Database Users

[DEV][ROM][Beta] AOKP Acer A500

Closed due to stupid forum rules

Anyone Flash yet???

Why should we donate to you? What's your part in this ROM? However protekk yet posted his ROM here, but as he did use Thor's kernel it was removed! I'll check the github link to see if everything is correct now.

smaury said:
Why should we donate to you? What's your part in this ROM? However protekk yet posted his ROM here, but as he did use Thor's kernel it was removed! I'll check the github link to see if everything is correct now,
Click to expand...
Click to collapse
its just my sig chill look at the top it says where i got this, however it took me 3 hour to get this post up and all the screenshots
BTW this does work cuz im running as i type
i put a footer on now, could you now remove your post, thank you

On github I can't find any source for A500 kernel, please give us a direct link.
Only found device related folder and vendor folder with related configurations and if i'm not wrong they are took from waydownsouth and his team's sources.

Edited
WHY DONT U LIKE IT???

jnktechstuff said:
its just my sig chill look at the top it says where i got this, however it took me 3 hour to get this post up and all the screenshots
BTW this does work cuz im running as i type
i put a footer on now, could you now remove your post, thank you
Click to expand...
Click to collapse
What Smaury was trying to explain to you, is that the AOKP type roms, use kernels that violate GPL. And roms that use kernels violating such license, are prohibited from being posted at XDA, or having direct links to such roms.
If you would read the rules about posting, you would have seen this.
Considering most A500 AOKP roms use Thor's kernel, and his kernel violates GPL, roms cntaining Thor's kernel, or links to it, cannot be posted. Period.
This is why these guys have their own place.
You should remove your post.
MD

haha dang i spent so much time on it, but i dont get it, how does this violate GPL, i used the rom from flexreaper not thor, also i credited people

It's not the rom, but the kernel.
In a short story, GPL basically states that changes to the android kernel must be made public. If a dev does not reveal the kernel source, then the kernel is in violation of GPL. Most decent sites will not host these types, as they do not want legal liability.
Thor is a great dev. Unfortunately he doesn't release kernel source, which is why he has his own site. It's a pity as he really does great stuff.
Kang roms, generally steal code and device trees from other devs, without giving credit to where they took it, and generally claim it as their own. As stated before, most of the kang roms use Thor's kernel therefore are not allowed to be posted. By nature of their practices, they generally are not welcome in a lot of places.
The rules are not stupid. They are in place to protect the devs and the users alike.
MD

Thanks haha I got u now
I will try not to do this again, just trying to learn a become a good developer

Former FSM (retired) Forum Mod Introduction

So everybody knows, I have taken over as one of the Moderators for this forum.
Feel free to PM for questions,
Hit the report button if it's something you think I should take a look at.
Pax
EDIT FROM Moscow Desire,
Pax is now retired from FSM Duties. :crying:
MD

paxChristos said:
So everybody knows, I have taken over as one of the Moderators for this forum.
Feel free to PM for questions,
Hit the report button if it's something you think I should take a look at.
Pax
Click to expand...
Click to collapse
Welcome great job thanks for being a mod;-)

Welcome~!

welcome
http://forum.xda-developers.com/showthread.php?t=1711137
can u look at this thread and see if the thors kernel was ever present if it was fine if not can we get the thread reopened AOKP would be another good option for roms for the tablet.

Timelord83 said:
welcome
http://forum.xda-developers.com/showthread.php?t=1711137
can u look at this thread and see if the thors kernel was ever present if it was fine if not can we get the thread reopened AOKP would be another good option for roms for the tablet.
Click to expand...
Click to collapse
Why not just go get it from rootzwiki if you want it so bad?

bfranklin1986 said:
Why not just go get it from rootzwiki if you want it so bad?
Click to expand...
Click to collapse
I'll stick to XDA. Not everyone on here has social skills to participate in forum discussions but i find that this site has much more information and the groups of people are more eager to help troubleshoot. by unlocking the thread if its not thors kernel it opens it up to ALL of xda to help.

Timelord83 said:
I'll stick to XDA. Not everyone on here has social skills to participate in forum discussions but i find that this site has much more information and the groups of people are more eager to help troubleshoot. by unlocking the thread if its not thors kernel it opens it up to ALL of xda to help.
Click to expand...
Click to collapse
I'm not sure how many actually remember the events relating to this earlier this year... But it was a mess.
Thor decided to start developing a ICS rom providing (presumably under apache2) the device/vender tree to the build. Just two little tidbits were, how to say, off with his approach.
a) The device tree included his kernel still without the source code (so now we have some apache2 code.. nice but not required, and its poisoned with a closed source kernel)
b) he provided links to the github repo (now deleted and/or hidden) on XDA via adfly.
After this was reported, XDA closed the thread, Thor took down the git repo and tried to pan this off to his greater followers (probably successfully) as XDA not even allowing him in when him to work here even when his code is "open".
--
While the source was open blazingwolf, ProTekk, randomblame (and some others?) managed to get the repo and clone it (or parts of it) into their own projects.. Mostly with little or no credit, and not always properly removing all traces of Thors kernel (either the main kernel was replaced with blazingwolfs open kernel, but a second copy of Thors kernel in the repo was left, or they just used thors kernel as it existed in the device tree).
In addition to this there was a recovery that used blazingwolf's kernel but otherwise was a nearly unmodified thor recovery binary (simply a hex edit to change the title, and thus hide the upstream source)
--
AOKP is now using the CM9 base for the device and vender trees, so everything including the CM9 T20 kernel is open source. However I its up to the AOKP team to re-post here at this point and not someone just wanting a mirror with their own unrelated donate link.
Some locked threads to remember in relationship to this:
http://forum.xda-developers.com/showthread.php?t=1353252 - ProTekk bit of ICS locked
http://forum.xda-developers.com/showthread.php?t=1426617 - randomblame recovery - locked
http://forum.xda-developers.com/showthread.php?t=1524919 - original A500 AOPK thread - locked

Just to clear this up, roms are under Apache v2 license (which doesn't require source release) kernels are under GPL which does require source release.
Sent from my R800x using Tapatalk 2

ezterry said:
I'm not sure how many actually remember the events relating to this earlier this year... But it was a mess.
Thor decided to start developing a ICS rom providing (presumably under apache2) the device/vender tree to the build. Just two little tidbits were, how to say, off with his approach.
a) The device tree included his kernel still without the source code (so now we have some apache2 code.. nice but not required, and its poisoned with a closed source kernel)
b) he provided links to the github repo (now deleted and/or hidden) on XDA via adfly.
After this was reported, XDA closed the thread, Thor took down the git repo and tried to pan this off to his greater followers (probably successfully) as XDA not even allowing him in when him to work here even when his code is "open".
--
While the source was open blazingwolf, ProTekk, randomblame (and some others?) managed to get the repo and clone it (or parts of it) into their own projects.. Mostly with little or no credit, and not always properly removing all traces of Thors kernel (either the main kernel was replaced with blazingwolfs open kernel, but a second copy of Thors kernel in the repo was left, or they just used thors kernel as it existed in the device tree).
In addition to this there was a recovery that used blazingwolf's kernel but otherwise was a nearly unmodified thor recovery binary (simply a hex edit to change the title, and thus hide the upstream source)
--
AOKP is now using the CM9 base for the device and vender trees, so everything including the CM9 T20 kernel is open source. However I its up to the AOKP team to re-post here at this point and not someone just wanting a mirror with their own unrelated donate link.
Some locked threads to remember in relationship to this:
http://forum.xda-developers.com/showthread.php?t=1353252 - ProTekk bit of ICS locked
http://forum.xda-developers.com/showthread.php?t=1426617 - randomblame recovery - locked
http://forum.xda-developers.com/showthread.php?t=1524919 - original A500 AOPK thread - locked
Click to expand...
Click to collapse
sadly i do but the thread i linked is albeit messy with side stuff i made the assumption it was mod locked. after talking with the other people i have foudn out that the OP requested it be locked. i went and got the rom from AOKP website and as far as i can tell is Thor free and i run clockwork recovery and V8 ICS bootloader.
As for the motives for my request is i'd like to see more roms succeed for this tablet as it is "old" tech people are moving to the tegra 3 Tabs i am not ready to give up on my $567.87 less than year old purchase. I own the A501 ATT 4G LTE Variant i bought it from ATT without contract hence the price

Uhm... Hi paxChristos! Welcome to our slightly disfunctional family! I hope that you have a great time.:silly:

Timelord83 said:
As for the motives for my request is i'd like to see more roms succeed for this tablet as it is "old" tech people are moving to the tegra 3 Tabs i am not ready to give up on my $567.87 less than year old purchase. I own the A501 ATT 4G LTE Variant i bought it from ATT without contract hence the price
Click to expand...
Click to collapse
As do we all (want larger choices in roms).
But there-in lies the issue. We have an AOKP rom that has been through many hands, and at times, had some suspicious coding involved. Including getting closed on more than 1 occassion due to shady practices and non-GPL kernels. Might have been 3 seperate roms for all we know.
To post the rom now, would probably piss off quite a few people if enough credits were not given, even if the kernel proved to be legit. And even then, you would have several people claiming the rom was theirs and they were the original authors. That's the nature of these "KANG" roms and "MIUI" roms.
Well, we have polluted PaxChristo's welcome thread enough for now. I suggest we give it a rest, and probably open a new thread in the General Forum. I'll DL and install it, and see what's up with it. Post some results later.
MD

good job
paxChristos said:
So everybody knows, I have taken over as one of the Moderators for this forum.
Feel free to PM for questions,
Hit the report button if it's something you think I should take a look at.
Pax
Click to expand...
Click to collapse
t my a500wondering where to post question about how to root my tab. Sadly it is running 3.2 honey and I am very confused as what to do to get it rooted. I am in southern Louisiana, maybe there are folks close to me that could help.
Thanks everyone don
Hey thanks for being a mod' it is a lot of work I know. Listen I am knew as I just go

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?

We heard you! Sony kernel sources now available on GitHub

Hi guys
We heard you! Sony kernel sources now available on GitHub
Read more here
http://developer.sonymobile.com/2014/06/27/we-heard-you-sony-kernel-sources-now-available-on-github/
If you have dev questions contact me
Enjoy!
J

sp sources are up

Hope sony hear us for some other things too.. with us sony can make the Android for us even better /o/

Very good thank you!!!

jerpelea said:
Hi guys
We heard you! Sony kernel sources now available on GitHub
Read more here
http://developer.sonymobile.com/2014/06/27/we-heard-you-sony-kernel-sources-now-available-on-github/
If you have dev questions contact me
Enjoy!
J
Click to expand...
Click to collapse
As I see the 201 kernel available for SP. Why not the 205?

air001 said:
As I see the 201 kernel available for SP. Why not the 205?
Click to expand...
Click to collapse
With the exception of the ram disk, they are identical.

https://github.com/sonyxperiadev/kernel-copyleft/tree/12.1.A.1.xxx
Btw thanks @jerpelea

Perhaps someone can finaly take a proper look to the annoying RAM issue

Opening the camera api to allow 3rd party apps to set ISO etc would be the cherry on the top...

Well, now that the kernel is up - how about a service that allows to create signed kernels so that locked BL can also benefit from custom kernels?

mick232 said:
Well, now that the kernel is up - how about a service that allows to create signed kernels so that locked BL can also benefit from custom kernels?
Click to expand...
Click to collapse
It's impossible to do without Sony private keys/signing tools leak. This is just a kernel source, it doesn't contain them. So even if you build the kernel from source, it will only work on UBL.
Also, to all: moving source to github won't solve anything, and doesn't change anything, it's now just easier to obtain the source for devs. Previously the source was released in the form of open-source tar packages on Sony site...

MrSteve555 said:
It's impossible to do without Sony private keys/signing tools leak. This is just a kernel source, it doesn't contain them. So even if you build the kernel from source, it will only work on UBL.
.
Click to expand...
Click to collapse
That is why I said "service" - Sony doesn't have to hand over the keys. They can provide a service, you upload your custom built kernel, Sony signs it, you download the signed kernel.

mick232 said:
That is why I said "service" - Sony doesn't have to hand over the keys. They can provide a service, you upload your custom built kernel, Sony signs it, you download the signed kernel.
Click to expand...
Click to collapse
Oh, so I misunderstood you. Your idea is really good, but I don't think Sony would ever think about it. So it's just a miracle...

Signing a custom kernel is endorsing it. How can they know if it's broken or something messed up.
Releasing the keys and signing package is better option with declaration or warning for no liability in case of damage

neXus PRIME said:
Signing a custom kernel is endorsing it. How can they know if it's broken or something messed up.
Releasing the keys and signing package is better option with declaration or warning for no liability in case of damage
Click to expand...
Click to collapse
They will never release the keys. However, they, themselves, can sign it if we give it to them. And we can provide them with sources so that they know everything is working fine.

shahrukhqasim said:
They will never release the keys. However, they, themselves, can sign it if we give it to them. And we can provide them with sources so that they know everything is working fine.
Click to expand...
Click to collapse
They dont have enough resources & time to release proper and quick updates. You really think with the NUMBER or devices with locked bootloaders and estimated number of submissions of custom kernels will be possible???
Think about it first. At least dozen models within 18 months time fframe, tens and hundreds of custom ROMs and kernels for each devices.
And its not like one kernel dev will only go once. Be reasonable bro.
Companies only provide services which can be automated. or require a suitable amount of debugging. Bootloader unlocking is IMEI based and database can be automated. So millions of users can use it without issues.
Much better would be they just release the keys in spirit of open source or maybe give some unlock mechanism for permanent locked BLs.

jerpelea said:
Hi guys
We heard you! Sony kernel sources now available on GitHub
Read more here
http://developer.sonymobile.com/2014/06/27/we-heard-you-sony-kernel-sources-now-available-on-github/
If you have dev questions contact me
Enjoy!
J
Click to expand...
Click to collapse
We need solution for locked blootloaders! Development is so hard on locked bootloaders. Give us signing keys or make a site to get kernels signed or anything. LBL are lagging behind UBL a great deal. We need signing facility.
---------- Post added at 02:54 PM ---------- Previous post was at 02:53 PM ----------
neXus PRIME said:
They dont have enough resources & time to release proper and quick updates. You really think with the NUMBER or devices with locked bootloaders and estimated number of submissions of custom kernels will be possible???
Think about it first. At least dozen models within 18 months time fframe, tens and hundreds of custom ROMs and kernels for each devices.
And its not like one kernel dev will only go once. Be reasonable bro.
Companies only provide services which can be automated. or require a suitable amount of debugging. Bootloader unlocking is IMEI based and database can be automated. So millions of users can use it without issues.
Much better would be they just release the keys in spirit of open source or maybe give some unlock mechanism for permanent locked BLs.
Click to expand...
Click to collapse
Then lets just contact Sony what solution do they propose? They should at least respond.

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.