Database Develop

build cyanogemod for p3100

Hi,
I have a samsung tab 2 p3100, which now has cynaogenmod 10 jellybean installed. I now need to make some tweaks in andorid OS<
How do I change the android source code and compile a build to flash on samsung p3100.
I downloaded the android source code from google and compiled it to generate a otapackage build with maguro configuration. But the zip file is not working for the device.
How can I create a ROM from the andorid source code which can be flashed on the samsung P3100. ?
Thanks and Regards,
Mahendra Naik

mahendra0203 said:
Hi,
I have a samsung tab 2 p3100, which now has cynaogenmod 10 jellybean installed. I now need to make some tweaks in andorid OS<
How do I change the android source code and compile a build to flash on samsung p3100.
I downloaded the android source code from google and compiled it to generate a otapackage build with maguro configuration. But the zip file is not working for the device.
How can I create a ROM from the andorid source code which can be flashed on the samsung P3100. ?
Thanks and Regards,
Mahendra Naik
Click to expand...
Click to collapse
You will need to do a lot more research. There are a lot of steps to setup a build environment for a device. No one can answer in a few words here Search XDA for tutorial on building CM10. There are a lot of pieces beyond the Google source that are required

adding application to the caynogenmod build
DigitalMD said:
You will need to do a lot more research. There are a lot of steps to setup a build environment for a device. No one can answer in a few words here Search XDA for tutorial on building CM10. There are a lot of pieces beyond the Google source that are required
Click to expand...
Click to collapse
Thanks for the reply,
I was able to compile cyanogenmod successfully and install it on the device.
Now I want to add my app as part of the build, so when the device is flashed with the rom, the app will already be there, instead of me having to install it again,
For this, I added the source of the app to /packages/apps and wrote an android.mk file and added the name of the app to PRODUCT_PACKAGES in the /build/target/product/core.mk file. But still the app is not included in the build,
How do I add my app as part of the cyanogenmod build?
Thanks and Regards,
Mahendra Naik

mahendra0203 said:
Thanks for the reply,
I was able to compile cyanogenmod successfully and install it on the device.
Now I want to add my app as part of the build, so when the device is flashed with the rom, the app will already be there, instead of me having to install it again,
For this, I added the source of the app to /packages/apps and wrote an android.mk file and added the name of the app to PRODUCT_PACKAGES in the /build/target/product/core.mk file. But still the app is not included in the build,
How do I add my app as part of the cyanogenmod build?
Thanks and Regards,
Mahendra Naik
Click to expand...
Click to collapse
A more simpler way is if You could just keep your app in system/app in your final zip!
Sent from my GT-P3100 using Tapatalk 2

Adding multi-window support to your Omni build

Since this has been asked a few times
Multi windows support is not in by default
You need to cherry-pick this to include it in your build
https://gerrit.omnirom.org/#/c/53/

thank you,
I added it into my p5110 build, i'll let you know if it works well.
edit:: working well

I won't lie, I plan to build Omni today as my first-ever Android build. It may go hilariously badly, it may go wonderfully. Is it in the command line that I cherry-pick that piece of code? The rest I think I can figure out myself. Thanks in advance.

dibblebill said:
Is it in the command line that I cherry-pick that piece of code?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=37053013&postcount=7

chasmodo said:
http://forum.xda-developers.com/showpost.php?p=37053013&postcount=7
Click to expand...
Click to collapse
You probably will want to do a "repo start" first, otherwise your commit will be clobbered on sync.
e.g. from the root of the source tree:
Code:
repo start work frameworks/base
for more on repo - http://source.android.com/source/using-repo.html

Thank you both. Very helpful. It's wonderful receiving help from the developers, especially since this will be my first build
Sent from my Nexus 10

dibblebill said:
Thank you both. Very helpful. It's wonderful receiving help from the developers, especially since this will be my first build
Sent from my Nexus 10
Click to expand...
Click to collapse
For everybody there was a "first time"

chasmodo said:
http://forum.xda-developers.com/showpost.php?p=37053013&postcount=7
Click to expand...
Click to collapse
When I execute this using the linked cherry pick, all I get is "fatal: Not a git repository (or any of the parent directories): .git

dibblebill said:
When I execute this using the linked cherry pick, all I get is "fatal: Not a git repository (or any of the parent directories): .git
Click to expand...
Click to collapse
you tried this mate?
Code:
git fetch [url]https://gerrit.omnirom.org/android_frameworks_base[/url] refs/changes/53/53/19 && git cherry-pick FETCH_HEAD
before that u must be inside ~/android/omni/frameworks/base if i im rigth, u get there by
Code:
cd ~/android/omni/frameworks/base
someone correct me if im wrong pls.

makkeonmies said:
you tried this mate?
Code:
git fetch [url]https://gerrit.omnirom.org/android_frameworks_base[/url] refs/changes/53/53/19 && git cherry-pick FETCH_HEAD
before that u must be inside ~/android/omni/frameworks/base if i im rigth, u get there by
Code:
cd ~/android/omni/frameworks/base
someone correct me if im wrong pls.
Click to expand...
Click to collapse
[codegit fetch https://gerrit.omnirom.org/android_frameworks_base refs/changes/53/53/19 && git cherry-pick FETCH_HEAD[/code]
Exactly as copied and pated from the cherrypick itself, yep.
I was, however, in ~/android/omni/.repo/projects/frameworks/base, though. Now I got it fixed and inserted. thanks!
on my way to being a ROM hacker/compiler, then later developer
EDIT: Will the sources for this rescync automatically when I repo sync, or will I have to also re-cherry pickk this every few days?

dibblebill said:
[codegit fetch https://gerrit.omnirom.org/android_frameworks_base refs/changes/53/53/19 && git cherry-pick FETCH_HEAD[/code]
Exactly as copied and pated from the cherrypick itself, yep.
I was, however, in ~/android/omni/.repo/projects/frameworks/base, though. Now I got it fixed and inserted. thanks!
on my way to being a ROM hacker/compiler, then later developer
EDIT: Will the sources for this rescync automatically when I repo sync, or will I have to also re-cherry pickk this every few days?
Click to expand...
Click to collapse
If you do a "repo start" before cherry-picking, repo will try to automatically rebase when syncing. It will not sync newer patchsets though.

thanks, very useful.
just to know, why isn't it yet merged ?

BENETNATH said:
thanks, very useful.
just to know, why isn't it yet merged ?
Click to expand...
Click to collapse
Because it still has a lot of bugs that need to be worked out?
Unfortunately, since Omni went public, we've had a ton of device support stuff to work with people on, so the more difficult items have temporarily stalled.

Entropy512 said:
Because it still has a lot of bugs that need to be worked out?
Unfortunately, since Omni went public, we've had a ton of device support stuff to work with people on, so the more difficult items have temporarily stalled.
Click to expand...
Click to collapse
sadly i would say.
BBQ was a great timing but people went crazy on omni, which is a good and a bad thing ^^
i've built omni for my device, with the commit, and it's nice, but currently, it's nearly strictly an AOSP, which is a bit frustrating
keep the hard work, courage to all the omni dev !

BENETNATH said:
sadly i would say.
BBQ was a great timing but people went crazy on omni, which is a good and a bad thing ^^
i've built omni for my device, with the commit, and it's nice, but currently, it's nearly strictly an AOSP, which is a bit frustrating
keep the hard work, courage to all the omni dev !
Click to expand...
Click to collapse
Yeah, I would've liked to have polished things a bit more - but the BABBQ was an opportunity we didn't want to miss.

yep,
anyway, great work. what you guys need now is to keep that alive, and to limit the time spent on bringing devices, better enhance the rom.
Rom builders will join the effort for all the rom stuff, especially as it's really easy (i've bring my device in a dozen of minutes, from a CM branch. needs polishing but works)

Does anyone have the last patch set for multiwindow the 4.3 branch? It seems like the past two weeks worth of patches were lost after the Gerrit server hard drive failure, and I just got my first build done yesterday so I'm not sure what I can cherry pick to test out multiwindow. The last comment remaining seems to imply that the last patch set was broken.

https://gerrit.omnirom.org/#/c/1510/

chasmodo said:
https://gerrit.omnirom.org/#/c/1510/
Click to expand...
Click to collapse
That's the 4.4 branch. Time to cherry-pick!

sgt. meow said:
That's the 4.4 branch. Time to cherry-pick!
Click to expand...
Click to collapse
Are you cherry picking back to 4.3 or doing a 4.4 build? Let us know how it goes! I just set up a build this weekend for my N8013 but Gerrit was down so I couldn't get multiwindow, and when it came back the Gerrit ticket was missing two weeks worth of patches as I mentioned so I was feeling like it would be risky to try to apply it.

[KERNEL] [KEXEC] Kernel EXECution for locked devices [N900V] [WIP]

THIS THREAD IS WIP & FOR DEVELOPERS ONLY !
Technical information with sources & binaries is in post #2. It includes kernel building, kexec-module, kexec-tools, hijack script, required patches & current problems with logs.
Click to expand...
Click to collapse
What is kexec?​--------------------------------------------------------------------------------------------------------​
kexec or kernel execution is a module/mechanism of the kernel that allows live/hot booting of a new/custom kernel "over" the currently running kernel. For more info, read the useful threads/links bellow.
kexec could be used to load a custom kernel into memory & yes, we'll then be able to install AOSP ROMs or in general run a custom kernel compatible with our device.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Updates:​--------------------------------------------------------------------------------------------------------​
[09/01/2014]:​
kexec module has been successfully patched & loaded/inserted into both NC2 & NC4 stock kernels. Now, I'm working on compiling/loading a guest kernel & fixing possible problems/bugs.
Click to expand...
Click to collapse
[08/31/2014]:​
Two versions of HLTEVZW KK kernel have been compiled from source: one uses the default configurations & the 2nd adds custom capabilities & kexec boot options. Moreover, kexec-tools & module have been cross-compiled. Now, I'm working on patches for kexec module & guest kernel (the hardest part).
Click to expand...
Click to collapse
[08/01/2014]:​
I've successfully flashed a custom kernel on my device. This trips knox flag & isn't 100% related to kexec, but it has the same objective (loading custom kernel on the locked-bootloader devices). However, the bootloader makes security check & blocks the installed kernel with the "unauthorized software by VZW" warning. Then, I tried to patch the bootloader to remove this security check, but my device was HARD BRICKED. Now, I've created a General thread for how to recover from a HARD BRICK. This is promising info for testing bootloader exploits.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
​​
Status
--------------------------------------------------------------------------------------------------------​
Supported NC2 & NC4 kernels
Working kexec-tools
Loaded kexec module
WIP kexec/guest kernel​
Click to expand...
Click to collapse
Thanks to / Credits:
--------------------------------------------------------------------------------------------------------​
@sextape - for the leaked NC2 firmware
@Hashcode - for his great work on kernel/recovery
...
Please PM me if I forgot to add proper credits for your work!​
Click to expand...
Click to collapse
​
XDA:DevDB Information
KEXEC, Kernel for the Verizon Samsung Galaxy Note 3
Contributors
hsbadr, CalcProgrammer1, ryanbg
Kernel Special Features:
Version Information
Status: Testing
Created 2014-07-11
Last Updated 2015-02-15

Technical Information
This post is reserved for technical information with sources & binaries. This includes kernel building, kexec-module, kexec-tools, hijack script, required patches & current problems.
Kernel Building:
--------------------------------------------------------------------------------------------------------​
The first step for building working kexec-module & tools is to cross-compile the kernel from source with the correct configurations. I won't describe how to build a kernel from source, but you may find this thread very useful.
I've used two different sources for the NC4/NC2 HLTE_VZW KK kernels. The 1st one is a part of SM-N900V_NA_KK_Opensource.zip released by Samsung for N900V NC4 kernel while the 2nd is available on @Hashcode's Github profile with 3 branches: hltevzw-kk-nc2 branch is modified for N900V NC2 kernel + 15 commits for compiling kexec as a module & other kexec patches.
The instructions provided by Samsung to build the NC4 kernel are to update CROSS_COMPILE toolchain environment variable in the Makefile & build with the default configurations as follows:
Code:
export ARCH=arm
make VARIANT_DEFCONFIG=msm8974_sec_hlte_vzw_defconfig msm8974_sec_defconfig SELINUX_DEFCONFIG=selinux_defconfig
make
However, I've patched the sources & used menuconfig interface to customize kernel configurations as follows:
Code:
export ARCH=arm
make VARIANT_DEFCONFIG=msm8974_sec_hlte_vzw_defconfig msm8974_sec_defconfig SELINUX_DEFCONFIG=selinux_defconfig menuconfig
make
(menuconfig is added in the second line)
The default output is the kernel image (arch/arm/boot/zImage) & modules (drivers/*/*.ko). The kexec-module(s) will be built if you patched the sources & configured it as a module.
You may then use dtbTool to generate device tree dt.img & mkbootimg to pack the kernel in boot.img.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Kexec Module:
--------------------------------------------------------------------------------------------------------​
There're many different flavors of kexec-mod sources. @delewer in this thread uses a standalone kexec-mod source MOD'd for Sony Xperia Z1 to be cross-compiled against the precompiled kernel source while @Hashcode in his sources on Github patches the kernel source to cross-compile kexec-mod with the kernel. Some modules may or may not use/port the hardboot patches. The output for kexec module/drivers have different names (the standalone kexec-mod source generates kexec_load.ko & procfs_rw.ko while the kernel source patched by @Hashcode generates 3 modules: arm_kexec.ko, msm_kexec.ko & kexec.ko).
To test if the cross-compiled modules are loadable & have the correct kernel headers, use insmod in terminal emulator (or a safe point with terminal like Safestrap) to insert the module into the kernel (assuming you've kexec.ko in /system/lib/modules/):
Code:
insmod /system/lib/modules/kexec.ko
Then, use lsmod to list & show the status of loaded modules:
Code:
lsmod
Alternatively, you may check if system call of the kernel includes kexec functions using:
Code:
cat /proc/kallsyms | grep kexec
The kexec-modules I've compiled are loadable & have been successfully inserted into both NC4 & NC2 kernels.
I'm using my own sources for kexec-module based on others & I'll share the sources with binaries & modules after making some required tests.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Kexec Tools:
--------------------------------------------------------------------------------------------------------​
I'm using the latest version of kexec-tools from here (currently, kexec-tools-2.0.8.tar.gz) cross-compiled for arm with custom configurations. Three binaries are generated including kexec (directly boot into a new kernel) & kdump (display kernel trace data). For more info, check the manpage of each binary & kexec/kexec-tools manuals/guides.
To test your kexec-tools cross-compiled binaries for arm,
Code:
kexec --help
assuming that they're in your PATH (e.g., /system/xbin) with executable permissions (e.g., 755).
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Hijack Script:
--------------------------------------------------------------------------------------------------------
will be updated soon...​
Click to expand...
Click to collapse
Required Patches:
--------------------------------------------------------------------------------------------------------
will be updated soon...​
Click to expand...
Click to collapse
Current Problems/Logs:
--------------------------------------------------------------------------------------------------------
will be updated soon...​
Click to expand...
Click to collapse

Sent from my SM-G900V using Tapatalk

jr_718 said:
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
My eyes about popped out the side of my head when I saw this! It says your in testing have you had any luck at all? Thank you thank you thank you BTW!

amebiasis said:
My eyes about popped out the side of my head when I saw this! It says your in testing have you had any luck at all? Thank you thank you thank you BTW!
Click to expand...
Click to collapse
I've tested several binaries for the same kernel version, but none works for now. I'll compile from source & see. However, please keep this this thread for devs discussions only until we release working kexec & guest kernel.

Trying to keep the n3 alive before the n4 arrives? Lol seriously though congrats and thank you. Hope you and the devs here the best of luck. We, the re owners, appreciate all you have done already for us.

bmwh0r3 said:
Trying to keep the n3 alive before the n4 arrives? Lol seriously though congrats and thank you. Hope you and the devs here the best of luck. We, the re owners, appreciate all you have done already for us.
Click to expand...
Click to collapse
Note 4 is useless until it gets root & custom ROMs. For me, it'll be better ONLY IF we can break its security & unlock bootloader!

What about surge & ryanbg and e.v.a. I been following them and they both have a good idea on how things work well I think they are good for the job

Just a thought I had when unlocking my spare RAZR hd, but the kernels on the Razr and my note 3 are 3.4.97 and 3.4.0. Is the exploit part of the kernel or is there a reason I'm a user and not a Dev? If it is, motopacalypse.apk is what unlocked my RAZR. I'm just trying to learn so please don't think I'm a moron. I just don't know the coding aspect of android at all.

Have you got an irc or hangout open for discussion?
Thanks for your efforts! !

tpike said:
Have you got an irc or hangout open for discussion?
Thanks for your efforts! !
Click to expand...
Click to collapse
There is #Galaxy-Note-3 on Freenode but it's really quiet in there most of the time.

Many forum lurkers like me have been anxiously waiting for this breakthrough! Don't give up! I also believe in donating to hardworking devs like you guys! Good luck...

I was an owner of a Motorola Defy and the day that it got KEXEC I was so exited.. so good luck for you guys! Nothing is impossible. :victory:

Feche said:
I was an owner of a Motorola Defy and the day that it got KEXEC I was so exited.. so good luck for you guys! Nothing is impossible. :victory:
Click to expand...
Click to collapse
Who was devs on kexec on defy?

ironfisted said:
Who was devs on kexec on defy?
Click to expand...
Click to collapse
Not sure

I've been working on kexec for a little while now with limited success. My biggest problem is the getting the 4 byte CRCs for the kernel symbols used by the kexec module. Same with a few other projects I'm working on. They compiled the NC2 kernel with MOD VERSION and CRC. I've compiled it from source, but there's so much work to be done my head is spinning.

ryanbg said:
I've been working on kexec for a little while now with limited success. My biggest problem is the getting the 4 byte CRCs for the kernel symbols used by the kexec module. Same with a few other projects I'm working on. They compiled the NC2 kernel with MOD VERSION and CRC. I've compiled it from source, but there's so much work to be done my head is spinning.
Click to expand...
Click to collapse
Good luck! Lots of us are waiting for this!

ryanbg said:
I've been working on kexec for a little while now with limited success. My biggest problem is the getting the 4 byte CRCs for the kernel symbols used by the kexec module. Same with a few other projects I'm working on. They compiled the NC2 kernel with MOD VERSION and CRC. I've compiled it from source, but there's so much work to be done my head is spinning.
Click to expand...
Click to collapse
Keep it up man, I understand the hard work involved in doing something like this, but it will definitely pay of in the end!!! Thank you for your hard work and dedication, you got a lot of people counting on you
Sent from my BajaRom "L" Themed Note 3

ryanbg said:
I've been working on kexec for a little while now with limited success. My biggest problem is the getting the 4 byte CRCs for the kernel symbols used by the kexec module. Same with a few other projects I'm working on. They compiled the NC2 kernel with MOD VERSION and CRC. I've compiled it from source, but there's so much work to be done my head is spinning.
Click to expand...
Click to collapse
I see. Let me know if you'd like to contribute to this thread. I'll update it soon with more details about the required patches & the preliminary results of my tests ––after releasing a new version of JasmineROM.

ryanbg said:
I've been working on kexec for a little while now with limited success. My biggest problem is the getting the 4 byte CRCs for the kernel symbols used by the kexec module. Same with a few other projects I'm working on. They compiled the NC2 kernel with MOD VERSION and CRC. I've compiled it from source, but there's so much work to be done my head is spinning.
Click to expand...
Click to collapse
I was told by a defy dev that we would have better luck contacting hp touch pad kernel devs. I guess their kernel is more like ours I guess. Idk. I never tried contacting dev from their yet

[NEWS] Kernel Source of 5.1 Released !

Okay, so let me get this straight.
I just checked Google Git of Android One ( https://android.googlesource.com/kernel/mediatek/ ) then I found something.
Google & Mediatek has pushed lollipop-5.1 branch ! Which means, kernel for 5.1 are ready to build
Here's the full branch just in case anyone need it :
https://android.googlesource.com/kernel/mediatek/+/android-mediatek-sprout-3.10-lollipop-mr1
and if you want to clone it and build a kernel for it, just type :
git clone https://android.googlesource.com/kernel/mediatek/ -b android-mediatek-sprout-3.10-lollipop-mr1
Cheers !

Just one question please?
F4uzan said:
Okay, so let me get this straight.
I just checked Google Git of Android One ( https://android.googlesource.com/kernel/mediatek/ ) then I found something.
Google & Mediatek has pushed lollipop-5.1 branch ! Which means, kernel for 5.1 are ready to build
Here's the full branch just in case anyone need it :
https://android.googlesource.com/kernel/mediatek/+/android-mediatek-sprout-3.10-lollipop-mr1
and if you want to clone it and build a kernel for it, just type :
git clone https://android.googlesource.com/kernel/mediatek/ -b android-mediatek-sprout-3.10-lollipop-mr1
Cheers !
Click to expand...
Click to collapse
Hey thanks for the news ( btw this news already been realeased by XDA itself and varun already grabbed it)
but there are three branch
one is named as kitkat
one is named for lollipop
so what does that third brach (android-3.18 )is for and you seems to be a well learned person( reconized contributer ) so there one question
Will google release device tree of android one devices as it does for nexus device? is there any scope for it in future (it may seem noobie to you but i really don't know)
thanks

hjmodi said:
Hey thanks for the news ( btw this news already been realeased by XDA itself and varun already grabbed it)
but there are three branch
one is named as kitkat
one is named for lollipop
so what does that third brach (android-3.18 )is for and you seems to be a well learned person( reconized contributer ) so there one question
Will google release device tree of android one devices as it does for nexus device? is there any scope for it in future (it may seem noobie to you but i really don't know)
thanks
Click to expand...
Click to collapse
Oh, it's already posted ? I'm really sorry xD (I rarely check the XDA portal, please forgive me if I repost this)
About the first question, the third branch doesn't seem to contain any tag (or I maybe too foolish to see if there's any tag), so I can assume that it's either a beta or kernel 3.18 that'll soon arrive for our device.
And for the device tree, it depends for Google and/or Mediatek. I really have no idea in this, tho.
Again, sorry if I repost this !

[CM-13.0] CyanogenMod 13.0 Development/Disscussion Forum.

@RendyAK , @Nonta72 and @MSF Jarvis are requested to come here.
I have started to work on cm-13.0 device and vendor tree, any body please download latest cm-13.0 source.
we are going to discuss in comments.
Raised som cm-13.0 blobs, few blobs missing on stock 6.0? any file missing do a merge request. libMali.so was based on cm-12.1 so, if you have libmali based on stock 6.0 please handover or do a merge request.
Vendor: https://github.com/HostZero/android_vendor_d5110_infinix/tree/cm-13.0
Device: Work progress
- HostZero

HostZero said:
@RendyAK , @Nonta72 and @MSF Jarvis are requested to come here.
I have started to work on cm-13.0 device and vendor tree, any body please download latest cm-13.0 source.
we are going to discuss in comments.
- HostZero
Click to expand...
Click to collapse
Syncing sources up on my server now....
Sent from my Pixel V1 using XDA Labs

MSF Jarvis said:
Syncing sources up on my server now....
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
Roger That!

@HostZero, @Nonta72, @RendyAK Check out this : http://build-box.msfjarvis.me:8080/job/cm-13-seedmtk/lastBuild/console
Don't mind the job name, I had planned this for the other variant but now it's for infinix. My suggestion would be to create a GitHub organization and add in everybody to it rather than one person having it on his personal account. And also, gimme a local manifest for the d5110
Sent from my Pixel V1 using XDA Labs

MSF Jarvis said:
@HostZero, @Nonta72, @RendyAK Check out this : http://build-box.msfjarvis.me:8080/job/cm-13-seedmtk/lastBuild/console
Don't mind the job name, I had planned this for the other variant but now it's for infinix. My suggestion would be to create a GitHub organization and add in everybody to it rather than one person having it on his personal account. And also, gimme a local manifest for the d5110
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
Build Fail. ? Hmm I will submit device tree tommrow for infinix

HostZero said:
Build Fail. ? Hmm I will submit device tree tommrow for infinix
Click to expand...
Click to collapse
https://github.com/d5110-devs
Go there and accept the invitation, then go to your repository settings and select Transfer and transfer the vendor tree to this organization. @Nonta72, you have an invitation pending too. @RendyAK, I couldn't find you on GitHub so send any of us your GitHub username and we'll add you
About the fail, it doesn't matter, I have shell access to the server as well so I can debug it properly in case there's an issue.
Sent from my Pixel V1 using XDA Labs

MSF Jarvis said:
https://github.com/d5110-devs
Go there and accept the invitation, then go to your repository settings and select Transfer and transfer the vendor tree to this organization. @Nonta72, you have an invitation pending too. @RendyAK, I couldn't find you on GitHub so send any of us your GitHub username and we'll add you
About the fail, it doesn't matter, I have shell access to the server as well so I can debug it properly in case there's an issue.
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
Great!

MSF Jarvis said:
https://github.com/d5110-devs
Go there and accept the invitation, then go to your repository settings and select Transfer and transfer the vendor tree to this organization. @Nonta72, you have an invitation pending too. @RendyAK, I couldn't find you on GitHub so send any of us your GitHub username and we'll add you
About the fail, it doesn't matter, I have shell access to the server as well so I can debug it properly in case there's an issue.
Click to expand...
Click to collapse
I have an github account, here it is. https://github.com/Rendyindo/
Since i didnt have any ubuntu computer, so i only can help with some system files. Is it ok?

RendyAK said:
I have an github account, here it is. https://github.com/Rendyindo/
Since i didnt have any ubuntu computer, so i only can help with some system files. Is it ok?
Click to expand...
Click to collapse
It'd be nice if you can probably arrange to dual boot Ubuntu or something because all the files in vendor and device have file system permissions set and Windows tends to completely ruin those. Without Linux you can't even help with the system files
Sent from my Pixel V1 using XDA Labs

MSF Jarvis said:
https://github.com/d5110-devs
Go there and accept the invitation, then go to your repository settings and select Transfer and transfer the vendor tree to this organization. @Nonta72, you have an invitation pending too. @RendyAK, I couldn't find you on GitHub so send any of us your GitHub username and we'll add you
About the fail, it doesn't matter, I have shell access to the server as well so I can debug it properly in case there's an issue.
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
HostZero said:
@RendyAK , @Nonta72 and @MSF Jarvis are requested to come here.
I have started to work on cm-13.0 device and vendor tree, any body please download latest cm-13.0 source.
we are going to discuss in comments.
Raised som cm-13.0 blobs, few blobs missing on stock 6.0? any file missing do a merge request. libMali.so was based on cm-12.1 so, if you have libmali based on stock 6.0 please handover or do a merge request.
Vendor: https://github.com/HostZero/android_vendor_d5110_infinix/tree/cm-13.0
Device: Work progress
- HostZero
Click to expand...
Click to collapse
libMali.so is indeed missing. Unless the compiler compiles one; I'm not sure we can boot cm13 yet. cm12.1's one is probably not compatible (kind of).
And I'm really sorry. I've been very busy lately.
I pushed some updates on my github. Still have lot of work to do there.

Nonta72 said:
libMali.so is indeed missing. Unless the compiler compiles one; I'm not sure we can boot cm13 yet. cm12.1's one is probably not compatible (kind of).
And I'm really sorry. I've been very busy lately.
I pushed some updates on my github. Still have lot of work to do there.
Click to expand...
Click to collapse
Hmm anyways I have pushed the cm-13.0 device tree too I have upstremed as many files as possible.
https://github.com/d5110-devs

MSF Jarvis said:
It'd be nice if you can probably arrange to dual boot Ubuntu or something because all the files in vendor and device have file system permissions set and Windows tends to completely ruin those. Without Linux you can't even help with the system files
Click to expand...
Click to collapse
Hmm, okay.. Gonna dual boot it, or use virtualbox.
Or can i use bash in win10, and install git there, i know apt-get and everthing in ubuntu works there.

RendyAK said:
Hmm, okay.. Gonna dual boot it, or use virtualbox.
Or can i use bash in win10, and install git there, i know apt-get and everthing in ubuntu works there.
Click to expand...
Click to collapse
MSF Jarvis Seems to be compiling and i have ubuntu but.. my package is done! as tree and vendor are ready try to compile.
Here by OFFICIAL TWRP:
https://dl.twrp.me/d5110

RendyAK said:
Hmm, okay.. Gonna dual boot it, or use virtualbox.
Or can i use bash in win10, and install git there, i know apt-get and everthing in ubuntu works there.
Click to expand...
Click to collapse
git works, but filesystem permissions are an ext* FS thing, and Windows doesn't recognize ext3 and ext4 formatted partitions so permissions will still get borked. Only solution is a Linux distro.
Sent from my Pixel V1 using XDA Labs

MSF Jarvis said:
git works, but filesystem permissions are an ext* FS thing, and Windows doesn't recognize ext3 and ext4 formatted partitions so permissions will still get borked. Only solution is a Linux distro.
Click to expand...
Click to collapse
Okay then..
Edit:
We have 3.18 too, is it makes cm13 more stable?

RendyAK said:
Okay then..
Edit:
We have 3.18 too, is it makes cm13 more stable?
Click to expand...
Click to collapse
Kernel 3.18? Dunno what to do with it honestly, @HostZero has been handling the device tree till now. I'm just setting up builds at the moment.
Sent from my Pixel V1 using XDA Labs

MSF Jarvis said:
Kernel 3.18? Dunno what to do with it honestly, @HostZero has been handling the device tree till now. I'm just setting up builds at the moment.
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
OMG! You guys could provide 3.18, I have used the 3.10 which has come with STOCK 6.0 if you guys can provide MSF will update it!
- HostZero

I have not done any changes with tree I have upstreamed may files available to cm-13.0 from 12.1.

HostZero said:
I have not done any changes with tree I have upstreamed may files available to cm-13.0 from 12.1.
Click to expand...
Click to collapse
I've re-created the device repo with original files from @Nonta72's device tree. Please don't kill commit histories and steal credits. Nonta did the base work and deserves the respect for that. You can delete your local device repo, clone the device repo from d5110-devs and make your changes. And please, please, use meaningful commit messages. You don't have to make a commit for every file you change and you don't need to add a fake file every f***in' time. Please take out the time to learn how to use git before you continue work on the device tree since I can't be cleaning up the mess you make of the commit messages each time.
Sent from my Pixel V1 using XDA Labs

MSF Jarvis said:
I've re-created the device repo with original files from @Nonta72's device tree. Please don't kill commit histories and steal credits. Nonta did the base work and deserves the respect for that. You can delete your local device repo, clone the device repo from d5110-devs and make your changes. And please, please, use meaningful commit messages. You don't have to make a commit for every file you change and you don't need to add a fake file every f***in' time. Please take out the time to learn how to use git before you continue work on the device tree since I can't be cleaning up the mess you make of the commit messages each time.
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
WTF! I should do again. C'mon man... I ll do later mostly not now. I will send you tree.zip better you can push it. Because my push is failing.