Database Users

[Q] Building OmniRom from resources for i9100

OK, so I am not a dev.
And iam completely newbie
I saw some people saying that if you have aosp on your device it's much easier to port omnirom for your device
So can I use CyanogenMod 10.2 that is available for the i9100
To build omni
And is there any detailed instruction on how to build it !!
Sent from my GT-I9100 using Tapatalk 4

I9100 needs some work because of its unified kernel, building it right now is pretty much useless if you don't know where to put your hands to solve some issues; I want to try it too but this project is in a early stage so I'll wait
Sent from my GT-I9100 using xda app-developers app

filllob said:
I9100 needs some work because of its unified kernel, building it right now is pretty much useless if you don't know where to put your hands to solve some issues; I want to try it too but this project is in a early stage so I'll wait
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Yup. There are two MAJOR blockers right now:
1) We haven't merged and tested the implementation of BOARD_SUPPRESS_EMMC_WIPE yet. So if someone were to build for a Superbrick-vulnerable device, they would have a a build that risks triggering Superbrick. While I normally don't like having moderators take down builds for something, if I see builds for Superbrick-vulnerable devices show up, I'm going to work with the mods to have them taken down until EMMC wipe suppression can be verified.
2) The build system needs some changes to permit TWRP to be built on userdebug builds. Right now, the only way you'll have a chance of working recovery is with an eng build.

Entropy512 said:
Yup. There are two MAJOR blockers right now:
1) We haven't merged and tested the implementation of BOARD_SUPPRESS_EMMC_WIPE yet. So if someone were to build for a Superbrick-vulnerable device, they would have a a build that risks triggering Superbrick. While I normally don't like having moderators take down builds for something, if I see builds for Superbrick-vulnerable devices show up, I'm going to work with the mods to have them taken down until EMMC wipe suppression can be verified.
2) The build system needs some changes to permit TWRP to be built on userdebug builds. Right now, the only way you'll have a chance of working recovery is with an eng build.
Click to expand...
Click to collapse
Can we not use cm10.2 smdk4412 kernel, @Entropy512? EMMC_WIPE is disabled there?
Also, would there be any problems if one were to remove Omni bootable project and replace it with cm10.2's?

chasmodo said:
Can we not use cm10.2 smdk4412 kernel, @Entropy512? EMMC_WIPE is disabled there?
Also, would there be any problems if one were to remove Omni bootable project and replace it with cm10.2's?
Click to expand...
Click to collapse
No, because it could still cause damage if flashing from an old "unsafe" kernel (see the first few CM10 builds as an example...). These are far rarer now than they used to be, but there are, believe it or not, occasionally people who are flashing stuff starting from TW ICS.
And CWM has tentacles throughout the CM source tree to get it to build. It requires too many hacks in too many places. TWRP is more standalone, the limitation being that on devices with standalone recovery, Dees_Troy always built using the "eng" variant instead of "userdebug".
There's a patch that allows for TWRP to build properly on userdebug using "make recoveryimage" but it fails to allow building of TWRP into unified-recovery devices like Sony pollux_windy/yuga. (Samsung requires even more hacks...)
Even the Sonys which are "sort of" working aren't ready for builds yet - for them to work they're dependent on the FOTAKernel trick Dees_Troy developed to allow for alternate recoveries to be put on a device.

Does the above apply also to the i9100g? It has an OMAP4 processor instead of Exynos so it should be easier to build for.

aidfarh said:
Does the above apply also to the i9100g? It has an OMAP4 processor instead of Exynos so it should be easier to build for.
Click to expand...
Click to collapse
I'm fairly certain the G has unified kernel/recovery just like most of the rest of the galaxys2 family (exception being the Qualcomm-based ones).
So it might build, but recovery will not function at all until the build system is fixed to properly support TWRP on devices with unified kernel/recovery.
It has nothing to do with Qualcomm vs. OMAP vs. Exynos, except that for whatever reason, Samsung actually allowed the recovery partition to serve its normal purpose on the Skyrocket and Hercules. Actually, the Straight Talk variant of the SGH-I777 might work, as that oddball device actually DID use its recovery partition.

Entropy512 said:
I'm fairly certain the G has unified kernel/recovery just like most of the rest of the galaxys2 family (exception being the Qualcomm-based ones).
So it might build, but recovery will not function at all until the build system is fixed to properly support TWRP on devices with unified kernel/recovery.
It has nothing to do with Qualcomm vs. OMAP vs. Exynos, except that for whatever reason, Samsung actually allowed the recovery partition to serve its normal purpose on the Skyrocket and Hercules. Actually, the Straight Talk variant of the SGH-I777 might work, as that oddball device actually DID use its recovery partition.
Click to expand...
Click to collapse
Is there anything I can do to help? Maybe if I can make it work on my device?

So the I9000 got a build of OmniRom, I thought it has also a unified kernel !!!

I was searching on Google today
and I suddenly found this
http://forum.xda-developers.com/showthread.php?t=2494127
that's an alpha build for I9100
it's using the CM10 kernel and it uses CWM not TWRP
Iam testing it right now

Jiangyi had some success getting i9100g working last night
I'm attempting to build for n7000 to see if it works at all... Who knows. Although I still need to merge in BOARD_SUPPRESS_EMMC_WIPE...

Entropy512 said:
Jiangyi had some success getting i9100g working last night
I'm attempting to build for n7000 to see if it works at all... Who knows. Although I still need to merge in BOARD_SUPPRESS_EMMC_WIPE...
Click to expand...
Click to collapse
I built it for Note already
http://forum.xda-developers.com/showthread.php?t=2495930
Sent from my GT-N7000 using Tapatalk

Yes @herna,you built it without a working recovery and without further testing. Nonetheless, it is running flawlessly, quicksand fluid with Raw kernel r3 and it's Cwm recovery.
Would you mind having a look at this commit.
http://review.cyanogenmod.org/#/c/50800/
Fixed the mobile data drop while calling. Thanks
GALAXY NOTE N7000 // OMNI ROM // JLS36I

AA1973 said:
Yes @herna,you built it without a working recovery and without further testing. Nonetheless, it is running flawlessly, quicksand fluid with Raw kernel r3 and it's Cwm recovery.
Would you mind having a look at this commit.
http://review.cyanogenmod.org/#/c/50800/
Fixed the mobile data drop while calling. Thanks
GALAXY NOTE N7000 // OMNI ROM // JLS36I
Click to expand...
Click to collapse
Yeah I know. Entropy and me are looking for the error, but is not beeing easy to fix. Okey, will add in a few hours and release new one. And I correct you, except the latest version, I tried all versions I released and some others I didn't release. I always do but that day I needed phone for important family things and couldn't test
Also I went to release with a prebuilt TWRP 3.0.101 kernel but XplodWilD say me that this will get Semi-Official maybe, and only compiled non-touched ROMs will be released.
Sent from my GT-N7000 using Tapatalk

@Entropy512 just wondering if your commit "i777 bringup" can be applied (obviously with some changes) to i9100
Sent from my GT-I9100 using xda app-developers app

filllob said:
@Entropy512 just wondering if your commit "i777 bringup" can be applied (obviously with some changes) to i9100
Click to expand...
Click to collapse
n7000 bringup would be easier, methinks.

filllob said:
@Entropy512 just wondering if your commit "i777 bringup" can be applied (obviously with some changes) to i9100
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Ask some DEV to try and see if works
Enviado desde mi GT-N7000 mediante Tapatalk
---------- Post added at 01:45 PM ---------- Previous post was at 01:44 PM ----------
chasmodo said:
n7000 bringup would be easier, methinks.
Click to expand...
Click to collapse
N7000 is gonna be up as soon as XplodWild get free and merge it and change something I said him. Idk why my Gerrit is not working. I am gonna install Ubunt 13.10 for clean and will set up all again for try if I can get Gerrit working again
Enviado desde mi GT-N7000 mediante Tapatalk

I'd like to try it myself, just want to know if it's legit or not
Sent from my GT-I9100 using xda app-developers app

filllob said:
I'd like to try it myself, just want to know if it's legit or not
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
If is legit what? I cannot understand you, sorry. You want to try, to compile...?

i am a noob to compiling etc, only followed cm instructions.
I want to know if the changes in the commit I mentioned can be applied to i9100 too, obviously with some adjustments, and if there is something more to do to compile omni for i9100
I hope I explained myself right( English is not my language)
Sent from my GT-I9100 using xda app-developers app

i9595G rom source?

Does google or samsung post the rom source for GPE devices, like google does for nexus?
I ask because I could not find any source @ google's repo for this device, yet - i see people posting that they build i9505g roms from source.
Thanks.

erid2thed said:
Does google or samsung post the rom source for GPE devices, like google does for nexus?
I ask because I could not find any source @ google's repo for this device, yet - i see people posting that they build i9505g roms from source.
Thanks.
Click to expand...
Click to collapse
No. The GPE devices are not supported in AOSP. The ROMs and kernels are built by the OEMs, with support from Google. Samsung makes the GPL sections of the kernel available, but no ROM code and no binaries/drivers. As far as factory images go, those would have to be provided by Samsung and they do not provide them. I am surprised, however, that SamMobile doesn't have anything available.
Sent from my Nexus 10 using Tapatalk 4

oldblue910 said:
No. The GPE devices are not supported in AOSP. The ROMs and kernels are built by the OEMs, with support from Google. Samsung makes the GPL sections of the kernel available, but no ROM code and no binaries/drivers. As far as factory images go, those would have to be provided by Samsung and they do not provide them. I am surprised, however, that SamMobile doesn't have anything available.
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
Thanks
BTW - i made a kernel for 4.4 roms on the m919/i9505g
dont have enough posts to post it here, but uploading source to github.
Been on it for a few days, and I like
MODS: can i post kernel in this section until I get enough posts? or do i need to wait before I post kernel?

Call for devs: Github organization

Hey guys,
I've set up an organization on github und uploaded my config there.
Could you please provide me your github usernames via PN so I can add you to the team?
Thanks,
Daniel

Doublepranks. But I just wanna join for learning if you would let me in....
Sent from my XT1033 using Tapatalk

swordrune10, don't have a moto g yet but most likely getting one for xmas
Sent from my Galaxy Nexus using Tapatalk

Josalaito, i'm working in cm 10.2 now, and i think we need a hard work because msm8x26 is not fully supported by cyanogen and we need to use 8960(The same happened in my old y300 cm doesnt support 8x25 and we use msm7x27a)

Hi, my username is debaj, I hope I can help anything as a geneal Android developer since I have no experience in ROM development except building Cyanogenmod for my old Nexus S

My Username on github is: denizkoekden
Regards,
Deniz

Still don't have a Moto G but wanna buy one for christmas...
My username on GitHub is: Lopicl

github username: immortalyash
i think we go go ahead with ms8226 as config as motorola giving sources it will things easier for us to add stuff for msm8226 and make it full compatible

immortal_yash said:
github username: immortalyash
i think we go go ahead with ms8226 as config as motorola giving sources it will things easier for us to add stuff for msm8226 and make it full compatible
Click to expand...
Click to collapse
I think it's best to begin with msm8226 from the outset rather than trying to kang a different board
I'm seapoint on Git by the way. https://github.com/seapoint

My Moto G arrives Tomorrow
too bad I won't have time to do anything
I am Scrizz on github

Count me in. as for creating a kernel, device, hardware and properity tree. Github : calibrex
Problem is now, i've seen that the MotoG stands under MSM8226 and MSM8926 @ Wikipedia. Which one is the Phone now really using ?
I see josalaito did a bit of work on Github *thumbsup*

7alvi reporting for call of booty..jk
Count me in. Will be getting mine by January (most likely) and for my work I have built Carbon, Mokee, Slim, AOKP, baked, anir, etc etc for HTC Pico..!

kaliberx said:
Count me in. as for creating a kernel, device, hardware and properity tree. Github : calibrex
Problem is now, i've seen that the MotoG stands under MSM8226 and MSM8626 @ Wikipedia. Which one is the Phone now really using ?
I see josalaito did a bit of work on Github *thumbsup*
Click to expand...
Click to collapse
its MSM8226 and we have already started with device tree...it would be better art with kernel as i m not a kernel man

immortal_yash said:
its MSM8226 and we have already started with device tree...it would be better art with kernel as i m not a kernel man
Click to expand...
Click to collapse
Hmm ok, was just confused because there different Specs out there : one says 8926 the other 8226 .
Will start my Stuff tonight, as soon i come Home.

kaliberx said:
Hmm ok, was just confused because there different Specs out there : one says 8926 the other 8226 .
Will start my Stuff tonight, as soon i come Home.
Click to expand...
Click to collapse
try using mine or alpha or any pre started device tree willl save you some time
BTW any knows which audio blob is being used in Motog?

Guys, please use git. Clone the team repo and start commiting changes
Sent from my XT1032 using xda app-developers app

a1Pha said:
Guys, please use git. Clone the team repo and start commiting changes
Sent from my XT1032 using xda app-developers app
Click to expand...
Click to collapse
don't worry, I got u
Sent from my Nexus 7 using Tapatalk

Me too i can do something for kernel... Also i have a sort of device tree on my github (yeah, a sort of)
Inviato dal mio Nexus 7 utilizzando Tapatalk

Lopicl.00 said:
Me too i can do something for kernel... Also i have a sort of device tree on my github (yeah, a sort of)
Inviato dal mio Nexus 7 utilizzando Tapatalk
Click to expand...
Click to collapse
we really do need a kernel tree and if someone could pull the prop files that would be great
Sent from my Nexus 7 using Tapatalk

If you want, you can fork my kernel project.

CyanogenMod

Do you guys think cyanogen will eventually add this phone to its official supported devices?
Coming from a Nexus 5 with endless rom development It'd be a shame if this phone didn't see as much. Especially since it has such potential

No I don't think that oneplus two will get official cyanogen support, as oneplus dropped cyanogen and started using there own OxygenOs. In fact, I think that even future devices from oneplus will also never get official cyanogen.
So, unfortunately we will need to stay at unofficial builds only.
Hit thanks If I helped!!!

kishan12345 said:
No I don't think that oneplus two will get official cyanogen support, as oneplus dropped cyanogen and started using there own OxygenOs. In fact, I think that even future devices from oneplus will also never get official cyanogen.
So, unfortunately we will need to stay at unofficial builds only.
Hit thanks If I helped!!!
Click to expand...
Click to collapse
yes cm13 will be officially available soon!And you are wrong ! one plus had a bad breakup with cyanogen but theirs a diiference between how people work on cynogenos and cyanogenmod !It depends on the devolepers of each community on how they work on devolepment on a particular device but one plus two devolepment is insane so cm13 is on the way and if u are still concerned look at the devs of HTC 826 they made thier device get official support and dont worry as far as i know the devolpement for this device will be booming shortly !And theirs already a thread on CM 13 !

Hope that your words come true. But still I don't think so that cm13 will be available OFFICIALLY.
Sent from my ONE A2003 using Tapatalk

kishan12345 said:
Hope that your words come true. But still I don't think so that cm13 will be available OFFICIALLY.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
lol bro if they get unofficial builds perhaps in a week ..then tell ME why wont they make it official after a month !what one plus one had is the cyanogen os and not cyanogenmod !To make a device official in cyanogenmod u have to have good devolpment for a particular device and the works for cm13 is already started for op2 !Check out cm12.1 thread garak is working on cm13 and threres another thread called cm13

As i understand, in order to get an official support from cyanogen to our device there must be unofficial CM build, witch can be sent to CM team for a review. If it passes, has most things working, then they add it to their device tree and officially supports it. In other words, anyone there can take CM vendor and framework codebase and then go and start adding the code necessary to make CM work properly on OPT device. When developer gets far enough along, he can then submit that code back to CM for inclusion into CM's github. If that code passes the checks that the CM team has, then the CM team will merge that code into its own device tree and add official support for that device.
Also there are chance of CM team taking this step by their selves .. but there is probably no hope for that. So the only hope is Grarak
This information is found in the official CM forum so i doubt it is false.

Potential Marshmallow for S3 GT-I9300 (Achieved)

Our device is still running because of XDA and the developers. And this 3 year + device is still in race to taste the Marshmallow .​
Let us use this thread for discussion related to it.​
And all of this has become possible because of the recognized developers @JustArchi @dhiru1602 @mcgi5sr2 @Moster2 @arter97, Christian Balster (OMNI team), @forkbomb444 Haxynox team, Nameless team (Sorry, in case I missed someone)​
There are 3 projects going on for getting a build of Marshmallow.(Achieved)
The Haxynox Team --- [ AOSP M is out --- Check it out ]
The Official CM --- [ The First to come --- CM 13 Thread Link ] && { It's happening, nightlies are here - Official CM-13 Download Link }
The Nameless Team --- [ It will happen ]
For the list of Marshmallow ROM's available for S3 GT-I9300, Click below:
Official CM13 : Thread Link
Official RESSURRECTION REMIX : Thread Link
Temasek's UNOFFICIAL CyanogenMod 13 : Thread Link
Official Mokee Open Source Project : Thread Link
The CyanPop 6.x.x Project : Thread Link
Minimal OS : Thread Link
Android Ice Cold Project : Thread Link
The Haxynox Team​
They are the first to initialize the process of building Marshmallow for our device tree.
Developers: @mcgi5sr2 @Ivan_Meler @dexter93
You can get the latest 'M' AOSP from here : Haxynox AOSP 'M' Link
Github: Link
Official CM 13​
The development process of CM 13 has just started few days back.
Developers: Simon Shields , CM team.
Gerrit Link: I9300-M-BringUp || smdk4412
Here comes the first building project of Marshmallow CM 13 :
CM 13 Thread Link
PS: No one knows who XYZ is on XDA. I searched for him on Github and came through this account of a developer ,which has the same commits as published on Official CM Gerrit.
The link of the Github is keepcalm444 and may be it is XYZ's user name.
An XDA account matched it forkbomb444 ( The email used for commit in Official CM Gerrit Review matches it .
(I am not sure about it)
The unknown developer is none other than @forkbomb444
Official Nameless Team​
They have asserted that they will definitely release Marshmallow for our device.
Source : Google+ Post
Developers: @dhiru1602 , Nameless Team.
You can follow their work on the thread here : Nameless ROM Link
Google+ Community (They are active here): Nameless ROM Official Community
Gerrit: Nameless ROM Gerrit
Note: I will update any information if something new happens. I welcome you to suggest new thoughts or new information.

You're forgetting Bliss team and their maintainers and developers who are also working to bring marshmallow to our phone. They've done a wonderful job on blisspop (I can tell you myself since I've been using their ROM as a daily driver for past weeks and I have no complaints about it)

Yes forkbomb(xda) this guy is maintaining cm13 official i ask on irc(he use this nickname)

That CM "Maintainer" is just using old commits from evryone else at the list and most of the time violating authorship by just squashing commits and putting his name on it

Romflasher69 said:
You're forgetting Bliss team and their maintainers and developers who are also working to bring marshmallow to our phone. They've done a wonderful job on blisspop (I can tell you myself since I've been using their ROM as a daily driver for past weeks and I have no complaints about it)
Click to expand...
Click to collapse
I love Blisspop too! I have tried lots of ROMS. At the end, blisspop! Thanks.

Ivan_Meler said:
That CM "Maintainer" is just using old commits from evryone else at the list and most of the time violating authorship by just squashing commits and putting his name on it
Click to expand...
Click to collapse
Maybe not because he has pushed some commits of his own also.
---------- Post added at 02:44 PM ---------- Previous post was at 02:38 PM ----------
And BTW are you guys sure that we will be getting the official CM13.0? No changes in github from last 2 days.

sunny1234590 said:
Maybe not because he has pushed some commits of his own also.
---------- Post added at 02:44 PM ---------- Previous post was at 02:38 PM ----------
And BTW are you guys sure that we will be getting the official CM13.0? No changes in github from last 2 days.
Click to expand...
Click to collapse
I didnt see his own changes at all they are just changes from other devs with his name on top..

sunny1234590 said:
Maybe not because he has pushed some commits of his own also.
---------- Post added at 02:44 PM ---------- Previous post was at 02:38 PM ----------
And BTW are you guys sure that we will be getting the official CM13.0? No changes in github from last 2 days.
Click to expand...
Click to collapse
Dear Brother, building a ROM is not like a game.
Things are always not pushed directly into gerrit everyday, it is a long process than we think.
And coming to another thing, we (normal users) have very less idea about development. It is better to keep calm than raising unnecessary issues. This issue can only be solved by a proper answer from the CM developer.

Romflasher69 said:
You're forgetting Bliss team and their maintainers and developers who are also working to bring marshmallow to our phone. They've done a wonderful job on blisspop (I can tell you myself since I've been using their ROM as a daily driver for past weeks and I have no complaints about it)
Click to expand...
Click to collapse
bingkeye said:
I love Blisspop too! I have tried lots of ROMS. At the end, blisspop! Thanks.
Click to expand...
Click to collapse
I didn't forget them. I respect their work.
Blisspop along with many other projects like Resurrection Remix, Euphoria OS, crDroid and many other are dependent on Archi device tree or Nameless device tree or Haxynox tree or some other (ROM source would be from respective projects).
Correct me, if I am wrong. I would definitely add them if someone from their team are working on bringing our device tree for 'M'.

Ivan_Meler said:
I didnt see his own changes at all they are just changes from other devs with his name on top..
Click to expand...
Click to collapse
Look onto github you'll see. However, I might be wrong too.

sunny1234590 said:
Look onto github you'll see. However, I might be wrong too.
Click to expand...
Click to collapse
Once check the below post carefully.
Ivan_Meler said:
I didnt see his own changes at all they are just changes from other devs with his name on top..
Click to expand...
Click to collapse
You would get the answer you want if you understand the bold/underlined/italicized part.

RajashekarReddy.A said:
Once check the below post carefully.
You would get the answer you want if you understand the bold/underlined/italicized part.
Click to expand...
Click to collapse
Selinux M bringup commit was of which developer? Wasn't it Simon himself? :/

Romflasher69 said:
You're forgetting Bliss team and their maintainers and developers who are also working to bring marshmallow to our phone. They've done a wonderful job on blisspop (I can tell you myself since I've been using their ROM as a daily driver for past weeks and I have no complaints about it)
Click to expand...
Click to collapse
Blisspop isn't exactly the most trustable ROM source I know. They've been caught kanging (stealing others work) many times and I'm sorry to say, but Blisspop isn't going anywhere until CM, Nameless or Haxynox do something.
Yes, it's getting a slight bit political if you're wondering.

I'm just tasting the flavor of the Marshmallow in my xt1069, but I prefer the i9300 because it's better than him (in my opinion, obviously). But, a little question about the future: can i9300 smell or taste Nutella? (I'm talking about a future Android N)
Talking about the ROM's, I feel very proud because we have so many people that don't let a device of this caliber die. Since I don't have money to donate, let me give my special thanks to all of you who don't let it go down. I'm very grateful.

moisespereira01 said:
I'm just tasting the flavor of the Marshmallow in my xt1069, but I prefer the i9300 because it's better than him (in my opinion, obviously). But, a little question about the future: can i9300 smell or taste Nutella? (I'm talking about a future Android N)
Talking about the ROM's, I feel very proud because we have so many people that don't let a device of this caliber die. Since I don't have money to donate, let me give my special thanks to all of you who don't let it go down. I'm very grateful.
Click to expand...
Click to collapse
It's a broad question.
First, let us hope if we could get a usable 'M' build first.

RajashekarReddy.A said:
It's a broad question.
First, let us hope if we could get a usable 'M' build first.
Click to expand...
Click to collapse
Too early, right? But I think we have a nice hardware to get M. Will it have a better Ram management?

Ivan_Meler said:
That CM "Maintainer" is just using old commits from evryone else at the list and most of the time violating authorship by just squashing commits and putting his name on it
Click to expand...
Click to collapse
Look, while I did do that, I think you'll find that it's been fixed. I'm sorry I did that, and it won't happen again.
Now, re: using old commits: did you *really* expect me to spend hours on end doing work that's already been done? It makes a lot more sense to focus on work that hasn't been done yet, rather than trying to redo everyone's work.
Now, if you have any issues with what I'm doing, feel free to PM me

Exactly! This is what my point is. And apart from that he himself is pushing some commits of his own. Make sure you guys checks at least. Yesterday there was two new commits which are not yet merged though.
Thanks a lot Simon @forkbomb444

forkbomb444 said:
Look, while I did do that, I think you'll find that it's been fixed. I'm sorry I did that, and it won't happen again.
Now, re: using old commits: did you *really* expect me to spend hours on end doing work that's already been done? It makes a lot more sense to focus on work that hasn't been done yet, rather than trying to redo everyone's work.
Now, if you have any issues with what I'm doing, feel free to PM me
Click to expand...
Click to collapse
I'm pretty sure proper authorship is the only issue here

Gokulbalram said:
I'm pretty sure proper authorship is the only issue here
Click to expand...
Click to collapse
He did give proper authorship to developers. Check github. Anyways, just a request to all the developers please help him to get the official CM13.0 for S3 running.