Database Info

GPL Mods and Roms

Hi there,
coming from the kyrillos/apocalypse remix thread I have a question for the devs here. Since Android is GPL software and so the resulting roms, changes etc. have to be published under the same license, why are people not allowed to remix roms as long as they release the sources again under GPL? I thought this was the spirit of open source: share and remix? Someone please enlighten me.
Thanks
Ben

Benjamin_L said:
Hi there,
coming from the kyrillos/apocalypse remix thread I have a question for the devs here. Since Android is GPL software and so the resulting roms, changes etc. have to be published under the same license, why are people not allowed to remix roms as long as they release the sources again under GPL? I thought this was the spirit of open source: share and remix? Someone please enlighten me.
Thanks
Ben
Click to expand...
Click to collapse
hi
pls im handling the issue pls dont create any more problems ok
CLOSED
and to all no more talk on this subject the next person doing it will have to face some serious action from me
pls dont force me to do the same

Essential prerequisites for a Developer to release a ROM in the DEVELOPMENT section

Note to Mods..
Kindly dont move it to the General section. This thread is about Rom development, and discusses a serious issue about the future of development in the Desire section, and whether we devs should continue to work here..
Some of us are getting irritated at this absolute proliferation of "me-too" roms..Roms which are apparently exact copies of others out there, taking all the files from them, deleting a few files (cut-copy-paste), and releasing it as the new "dev"'s own work..
In this context, I'd like to propose a list of questions a wanna-be Rom dev should ask himself/herself before starting a Rom thread here.
Can you smali and baksmali files individually?
Are you familiar with Edify and Amend?
Do you know about Kernel ramdisk loading, bootclasses and MTD layouts?
Are you familiar with adb and fastboot commands and can you offer support to endusers who have problem with this?
Can you debug Edify code and built an updater-script from scratch without wholly relying on the dsixda kitchen?
Do you know how to modify frameworks, system apps and jars and debug their errors?
Are you familiar with how to port roms between devices? (applicable only if you intend to release a port)
Have you significantly modified a Rom to add new and useful content?
Have you contributed uniquely to the Rom, and not just made a cocktail of features already made by devs?
Can you write/at least understand bash scripts?
Can you compile your own kernel from source code?
The items in Bold are more important..
If the answer to most of these questions is Yes, go ahead, we'd love to have your Rom here, as you most certainly have what it takes to release a finished product.. If not, think thrice before posting a Rom. We cant prevent you from posting in the Dev section, but be forewarned that it might be an invitation for flaming! If your purpose in posting a Rom is to learn development yourself, and you've made a Rom which uses >=80 % of another Dev's work, it may be better to release it as a "ROM-Mod" and work on it further,.
Another suggestion is to use the prefix [ROM] for something which is built originally, and [Rom-MOD] for others with minimal changes from a source Rom, and the latter should give proper credits to the source...
Before posting a new Rom, ask yourself the following questions:
What is the difference between your Rom and the Base?
Have you done active development, other than delete a few files/mix a few files/themes?
Is there a significant difference between your Rom and other Roms out there/your source, in terms of new features added?
The following is a list of items which are not considered development:
Using another Dev's original ROM as your base, where you :
Only add mods from yet another developer/rom
Do not include any actual development done by you in the form of code in bash scripts/updater-script/compiled binaries which add some new functionality to the original Rom
Only mix the source Rom with themes/apps created by another developer
Only remove/add some apps from the source rom, in the process reducing its size
In case the difference between the base Rom and the new Rom is very marginal, but includes a significant development on the part of the new dev, the change from base rom should be clearly documented as part of a changelog attached in the thread OP.
If your purpose in starting a Rom thread is to study to develop, you can clear questions related to development by using the Developer Google plus Huddle maintained here
What do you guys think? Should we suggest to the mod team to append this to the list of rules for posting? Feel free to add your suggestions/criticism/opinion

Droidzone said:
Note to Mods..
Kindly dont move it to the General section. This thread is about Rom development, and discusses a serious issue about the future of development in the Desire section, and whether we devs should continue to work here..
Some of us are getting irritated at this absolute proliferation of "me-too" roms..Roms which are apparently exact copies of others out there, taking all the files from them, deleting a few files (cut-copy-paste), and releasing it as the new "dev"'s own work..
In this context, I'd like to propose a list of questions a wanna-be Rom dev should ask before starting a Rom thread here.
Can you smali and baksmali files individually?
Are you familiar with Edify and Amend?
Do you know about Kernel ramdisk loading, bootclasses and MTD layouts?
Are you familiar with adb and fastboot commands and can you offer support to endusers who have problem with this?
Can you debug Edify code and built an updater-script from scratch without wholly relying on the dsixda kitchen?
Do you know how to modify fameworks, system apps and jars and debug their errors?
Are you familiar with how to port roms between devices?
Have you significantly modified a Rom to add new and useful content?
Have you contributed uniquely to the Rom, and not just made a cocktail of features already made by devs?
Can you write/at least understand bash scripts?
Can you compile your own kernel from source code?
If the answer to most of these questions is Yes, go ahead, we'd love to have your Rom here.. If not, think thrice before posting a Rom. We cant prevent you from posting in the Dev section, but be forewarned that it might be an invitation for flaming!
What do you guys think? Should we suggest to the mod team to append this to the list of rules for posting? Feel free to add your suggestions/criticism/opinion
Click to expand...
Click to collapse
Droidzone, your totally right, there are like 3-4 same roms ... This is jus madness... Get those copyers out now ;o
Greetz
Sent from my HTC Runnymede using XDA App

Totally agree with the statement. There are too many Roms that are 99% the same which makes it not easy to choose one, especially for people with not much experience relating to Roms. On the other side, don't make those "rules" too strict as this is a possible entry barrier for new Rom developers and would limit the varierity.

chrismast said:
Totally agree with the statement. There are too many Roms that are 99% the same which makes it not easy to choose one, especially for people with not much experience relating to Roms. On the other side, don't make those "rules" too strict as this is a possible entry barrier for new Rom developers and would limit the varierity.
Click to expand...
Click to collapse
Totally agree.

Agree 100% , if your just 'adjusting' or 'modding' a rom place the file in a post on original Rom thread , if its a good mod I'm sure users will apteciate it and the original dev may put on op or even enhance the official rom from it.
This way those would be devs will gain respect and learn the trade , without annoying everyone with 'copies' .
Otherwise we could set up a 'mods' section on the forumn to move all copied roms to, would clear the clutter.
Cheers all devs
Sent from my HTC Desire using xda premium

AGREED ...
I am leaning towards learning ROM development myself but there is so much to learn and because i have this interest i have downloaded Ubuntu 10.04 and i am starting to learn how that works and i'll take it from there.
I mod almost every ROM i use before i flash it and trust me 7zip and notepad++ dont make you a DEV, YES it is always nice to see new DEVs and work being released but like back in the froyo days there was 3 Sense 1.9 ROMs that i tested, namely AuraxTSense, LeeDroid and Startburst. Even though they seemed the same they are very different and unique...
Now if you look @ AcedOff, Aurora and CoolAces3D, they are all Cools work and are no different and suffer from the same bugs. All these ROMs are creating is congestion.

Or we could all just use our common sense.

Got to be careful of making a l knee jerk reaction to one or two roms. I found the new stock gingerbread very useful, and that cooker was not a Dev as described by the rules above.

chrismast said:
Totally agree with the statement. There are too many Roms that are 99% the same which makes it not easy to choose one, especially for people with not much experience relating to Roms. On the other side, don't make those "rules" too strict as this is a possible entry barrier for new Rom developers and would limit the varierity.
Click to expand...
Click to collapse
100% agree.
I started messing around with redux source code, intergrated android 2.3.5 source into it, modified jar files, added code, removed code and compiled a unique ROM. I can debug it and can answer yes to maybe half of those questions...
Can you smali and baksmali files individually? Never tried
Are you familiar with Edify and Amend? yes
Do you know about Kernel ramdisk loading, bootclasses and MTD layouts?Maybe, No, Yes
Are you familiar with adb and fastboot commands and can you offer support to endusers who have problem with this? Yes
Can you debug Edify code and built an updater-script from scratch without wholly relying on the dsixda kitchen? Probably
Do you know how to modify frameworks, system apps and jars and debug their errors? Yes
Are you familiar with how to port roms between devices? Sort of
Have you significantly modified a Rom to add new and useful content? Yes
Have you contributed uniquely to the Rom, and not just made a cocktail of features already made by devs? Not really, I haven't invented my own mods
Can you write/at least understand bash scripts? Partly
Can you compile your own kernel from source code? Probably, Never tried. Can compile ROMs and Recoveries.
Click to expand...
Click to collapse
I can completely support my ROM and it isn't a simple clone, but too strict would create a barrier for me at least.
But I am sick to death of seeing people with "recognised Developer" status for simply running someone else's ROM through dsixda kitchen and selecting all the options - Surely this belittles the whole recognition?!
Perhaps the question should be:
Did you install someone elses rom, flash a couple of mods then run the backup through dsixda kitchen?

backfromthestorm said:
Got to be careful of making a l knee jerk reaction to one or two roms. I found the new stock gingerbread very useful, and that cooker was not a Dev as described by the rules above.
Click to expand...
Click to collapse
The new stock gingerbread could have been had from teppic's thread posted many weeks ago (with additional mods). In fact, any newbie could easily have made it by running the zip available from HTC's site through dsixda's kitchen, which is whom the kitchen is intended for..

@3f1f37
Before the start again: But AceSMod007-3D is from me and not from coolexe! Otherwise it would not have been unlocked again my thread!!

rootSU said:
100% agree.
I started messing around with redux source code, intergrated android 2.3.5 source into it, modified jar files, added code, removed code and compiled a unique ROM. I can debug it and can answer yes to maybe half of those questions...
I can completely support my ROM and it isn't a simple clone, but too strict would create a barrier for me at least.
But I am sick to death of seeing people with "recognised Developer" status for simply running someone else's ROM through dsixda kitchen and selecting all the options - Surely this belittles the whole recognition?!
Click to expand...
Click to collapse
@rootsu, yours isnt a clone of anything, and if anything deserves Rom status, it's a Rom built from Android source and modified periodically..
I dont mean the dev should satisfy all these criteria at the time of his first build..
At least he should have done original development of his own..which includes things other than cut-copy-paste and changing hboot/fitting a rom built by another dev on another partition layout..
In any case, these are just suggestions...Maybe it could be a guide for future devs to let them know that blatant copying of someone else's work is not acceptable to the community at large

michaelm_007 said:
@3f1f37
Before the start again: But AceSMod007-3D is from me and not from coolexe! Otherwise it would not have been unlocked again my thread!!
Click to expand...
Click to collapse
Yo Micheal
I was in no way taking a shot at your work buddy, i am refering to ACED OFF!!! and not your AcesMod007.
I know there is a differences between you work and coolexe's, actually i commend you for your time and effort. You and cool remind of Baadnwz and Robocik from 1st half of this year, when the Sense 2.1/3.0 hybrids were coming out. They had similar features but were unique, this applies to both your work and cools.
To further put a feather in your hat, i am im-patiently waiting for your SagasMod007-3D to come out of beta as i follow your work very closely

You could be in danger of alienating noobs who come on here for advise, who want to learn to develop a rom from source or from a ruu. Surely the way to start to learn is from the start!
Not everybody has the knowledge like u Droidzone, but u never had it once either. You learn by doing.
I said im not a dev, i did mine cus there wasn't one out there that fitted for me.Now if i think that then somebody else might, so it helps them to.Surely this is where u start to learn. Granted if there was a rom somebody posted exactly like mine id be like wtf, so i do understand.

Honestly, the dev section is not (imho) for newbies who want to learn to develop, but for developers who have their own contribution to add to the forum..In other words, something genuinely developed by them, and not using the kitchen to select 1,2,3 and make a zip..
For learning to develop, why not make a thread in the General/Q&A section and make a collaborative effort? Then once there is an actual developed product, anyone can release it here.. Agreed, there was a time when I knew nought.. But by the time I released my first rom, I did know enough..Look at people like rootsu who were helping people out for years and learning the tricks of the trade, so to speak, before releasing their first product?
I fail to understand how anyone can call using a bash script and selecting a couple of options as development.. dsixda's kitchen, in dsixda's own words, is intended for newbies to modify a rom for personal use, and in his own words: 'dont expect the kitchen to transform you into a developer overnight'..
Mods are mods, and original roms are that.. Maybe mods can be released in the General section..

dan281082 said:
You could be in danger of alienating noobs who come on here for advise, who want to learn to develop a rom from source or from a ruu. Surely the way to start to learn is from the start!
Not everybody has the knowledge like u Droidzone, but u never had it once either. You learn by doing.
I said im not a dev, i did mine cus there wasn't one out there that fitted for me.Now if i think that then somebody else might, so it helps them to.Surely this is where u start to learn. Granted if there was a rom somebody posted exactly like mine id be like wtf, so i do understand.
Click to expand...
Click to collapse
For me, using dsixda to make stock roms is ok, so long as there arent loads of them available or they offer something different.
My personal issue (without naming names) is someone taking an AOSP ROM or even a Sense Port that is already released by a dev, runnig it through dsixda to add nanotext editor, a2sd+, zipalign or someone else's kernel, then release it as their own ROM and call themselves "Dev".
I personally do not see myself as a Dev. I couldn't take a ROM from another device, and make it work on the desire, or build a ROM for another device without the vendor and device directories from a working repository. I think I am a compiler at best. I can take source code from here and there, put it all together and compile a working ROM.
If I can't call myself a dev but people who take other people's roms and run through the kitchen then call themselves a dev, theres something wrong there. And then XDA supports them with "recognised developer" status
EDIT> @ Droidzone - I would definitely support a Development Q&A Subforum here. I can't believe we haven't got one. I'm sure devs would visit that to help, rather than n00b central (i.e Q&A)

i do agree there droidzone, a dedicated place for people to learn is what this needs.
if it had the support from people like rootsu(who has helped me no end) then it can benefit everybody.
But the support needs to be there not just from the odd one or two.

Droidzone said:
The new stock gingerbread could have been had from teppic's thread posted many weeks ago (with additional mods). In fact, any newbie could easily have made it by running the zip available from HTC's site through dsixda's kitchen, which is whom the kitchen is intended for..
Click to expand...
Click to collapse
I don't have a PC. So its been very useful. and not something I could of easily done. Or have the time. Its a nice upgrade. We shouldn't limit what's available to the rules of the first post.

Can a mod move this thread, its in the wrong section lol only messing, i can see your point of view, you bust your balls to make a rom and fix it and then someone adds a few tweaks and mas it their own, and they think cause they thank you, it makes everything ok, and its not being selfish on your part, you take another rom from a phone that isnt ours, transform that rom so that it works on our phone, to me that is amazing, you put all that effort in and then you must be so proud when you hav finished and majority of people are happy, i can ee how it hurts when someone changes a few things, problem is, youll never win, how many times do things get posted cause someone cant search, anyway to all the devs, keep up the hard work because 99% of the world appreciate your work, dont let the 1% spoil it for the rest !
Sent from my Transformer TF101 using Tapatalk

ZeGuitarist said:
Or we could all just use our common sense.
Click to expand...
Click to collapse
This completely.

[4.2]For mediatek 6577 Post it here !!!!

Android 4.2 is available for mediatek 6577.Yes i am telling the truth but the problem is no one has posted it here.
For example these mobile runs on android 4.2 and the chipset is mediatek 6577
FIRST
SECOND
THIRD
Click to expand...
Click to collapse
So if anyone of you had purchased one of these devices kindly upload system folder of it + boot.img.It will be a huge help for all mediatek based devices.
Thank you.

sURE , I HAVE MICROMAX A89

lol
JB 4.2 on MT6577?
Even with the rom and kernel, you will need ALOT more to work with.
And did you forget Mediatek is Closed Source?
Wish you good luck, you will need it !

superdragonpt said:
lol
JB 4.2 on MT6577?
Even with the rom and kernel, you will need ALOT more to work with.
And did you forget Mediatek is Closed Source?
Wish you good luck, you will need it !
Click to expand...
Click to collapse
First read things clearly then post.
I have not started this tread for porting JB 4.2.xx i have started this tread to collect necessary files.

icoolguy1995 said:
First read things clearly then post.
I have not started this tread for porting JB 4.2.xx i have started this tread to collect necessary files.
Click to expand...
Click to collapse
I actually read it
My reply was based in, what use can u actually have for JUST **hint**hint** the base system and Kernel source code?
Being the rest Closed Source, there isn't much you can do with JUST that.
Don't take it personal, i just hate these Comp. that dont comply with the Android GPL License.

superdragonpt said:
I actually read it
My reply was based in, what use can u actually have for JUST **hint**hint** the base system and Kernel source code?
Being the rest Closed Source, there isn't much you can do with JUST that.
Don't take it personal, i just hate these Comp. that dont comply with the Android GPL License.
Click to expand...
Click to collapse
Well if we get our hands on ROMs that have the same chipset we might find a solution for the camera don't you think?

Let me help u with the source code for mtk 6577
code.openhub.net/project?pid=&ipid=402434&fp=402434&mp&projSelected=true&filterChecked
Sent from my Micromax_A101 using XDA Free mobile app

All ROMs Ever thread

Do not post "Thank you" type responses.​[SIZE=+3]ALL ROMS EVER (Intro to be added)[/SIZE]
[SIZE=+2][INDEX][/SIZE]
[SIZE=+2]Helpful Information[/SIZE]​[SIZE=+1]Welcome, this thread has been created to encompass everything you may need for your android device. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread, or create your own thread in the Q&A forum. Do not use this as a general help thread.
Since most ROMs are MM now I will split ROMs in this thread into 2 sections, MM and EOL.
This thread probably isn't going to help anyone. If it does help you, however, please tell me the usage in a post!
Please tell me if I made any mistakes in the categorization, and add on new ROMs as they come out/those which I forgotten to add.
Lastly, Stock-Based ROMs will not be added unless it is being ported to other devices eg. Xperia ROM ported to XOSP to other devices[/SIZE]​Click on a Link below for More Info
MM ROMs
Toolchains
EOL ROMs
Kernels
Useful links any general index should have
http://forum.xda-developers.com/showpost.php?p=65849943&postcount=34
*​Forum Rules | New Users Guide | XDA Tour | Report Posts​Please look for a similar INDEX thread when visiting another device forum.
If you would like to create an [INDEX] please Click Here.
A special thanks to everyone who contributed to the production of this INDEX
Please note: This is and will be, an ongoing WIP​

MM ROMs
*Mainly* CM-Based:
CyanogenMod
Temasek's CM
PAC ROM (And their cute but old website copyrighted 2014)
AICP
BeanStalk ROM
BlissPop ROM
AOKP
Resurrection Remix
XOSP
crDroid
CyanPop
OctOS
Marsh
MoKee
LiquidSmooth (+Slim base)
FlexOS (This is relatively obsolete as compared to Team Flex's AOSP-based Flayr OS)
OwnRom
TeslaOS (Not to be confused with Tesla by GZR)
*Mainly* AOSP/CAF-Based:
Dirty Unicorns (And CAF)
Pure Nexus
Cyanide L MM (Apparently it isn't Cyanide M) (Un-merged with Fusion from VrToxin)
OmniROM
Tesla by GZR
Slim
YAOSP
SlimYAOSP (Repo Init THIS first)
Nameless ROM
Broken ROM
Chroma ROM
MoKee
UberMallow (Previously OptiPop)
CandySix
FlayrOS
Exodus ROM (Quite confused as to which manifest to link to)
Validus by GZR
TipsyOS
OrionOS
Screw'D AOSP
AOSiP
ZephyrOS
BenzoRom
Beltz Rom (AOSP with DUI)
Cardinal AOSP
Citrus CAF
Evervolv
CopperHead OS
Toxic OS
All Purenexus and Slim mods from the guys at http://forum.xda-developers.com/slimroms/general/rom-builders-collective-t2861778

Toolchains
Guide for using below TC
UberTC (And Github) (For Pre-Built TC refer to BitBucket)
Linaro
SaberMod (Pre-Built TC at their website)
Hyper Toolchains
DragonTC
Christopher83's custom TC builds
Archi's Toolchains (Change the branches to change TC)

EOL stuff
VrToxin (Apparently some internal strife)
Fusion (Merged with Cyanide to VrToxin, then VrToxin died)
Archidroid/Archikernel (Should be getting a revive soon since Archi got an OP2)
Perseus Kernel (IDK why it died, too long ago)
Minimal OS (IDK why it died. Wanted to build this in particular because LP Minimal is awesome but suddenly github activity stopped)
Paranoid Android (RIP will miss you guys. They got "bought over" by OnePlus to dev OxygenOS)
F-AOSP (IDK why it died.)
Yank Kernel (I think he just gave up or something)
[*]80% of Dirty Unicorn (Went over to some Russian company) (Hi Mazda/Alex Cruz)
Euphoria OS
RadonX
Nexus Experience

Custom Kernels
AK Kernel
Lightning Kernel
Agni kernel
Arter97's Kernels
Boeffla Kernel
Franco Kernel
ElementalX
Phasma Kernel
Kylo Kernel (Same as above...???)
Some random modded kernels mostly in Nexus forums I didn't bother to add

RIP people.
A filler and awareness post.
See you in heaven. I know you are in a better place now.
TonyStark
FlashVetrin
Please add on. So far I only know of those two ^^

Garbage Link Collector
Another Link Collector (But not structured so Garbagely)
A ROM Building Guide for you to build ANY ROM on this list
XDA New User Guide
How to shake off "n00b" status
How to get Moderator's attention (Don't waste their time unnecessarily though )
Requests to Mods (All users welcome)
Logcat (MEOW)
Commonly used acronyms on XDA
How to become RC/RT
Signature Code Sharing
Archi's Optimisations (And for MM)
Index Project
Ask Away Project
Anti-Piracy/ContentGuard
NEED-TO-READ 1
NEED-TO-READ 2

Special thanks to:
@Trafalgar Square
@sd_shadow
@kuzibri
@zelendel
And everyone else at the Index Thread!!
Temporary to-do:
CarbonROM
others?

limjh16 said:
Last one
Click to expand...
Click to collapse
I would add descriptions and differences between rom types
https://en.wikipedia.org/wiki/List_of_custom_Android_firmware
http://android.wikia.com/wiki/Category:Custom_ROMs
http://lifehacker.com/5915093/five-best-android-roms
Sent from my KFFOWI using XDA Labs

limjh16;65315332
said:
CM
AOSP
Others
Kernels
Dead ROM/Kernels
Useful links any general index should have
[/INDENT][/INDENT]
*​Forum Rules | New Users Guide | XDA Tour | Report Posts​Please look for a similar INDEX thread when visiting another device forum.
If you would like to create an [INDEX] please Click Here.
A special thanks to everyone who contributed to the production of this INDEX
Please note: This is and will be, an ongoing WIP​
Click to expand...
Click to collapse
Hi,
sofar, so good. Would it be an idea to also add an item which devices are supported and which not? I would remove the item "Dead ROM/Kernels", they are of no use for your thread and may cause confusion.
kindest regards,kuzibri

Here is a big list of porting and compiling rom guides
[Guides][Updated] All Guides @ One Place By Hpsgill by Hpsgill

kuzibri said:
Hi,
sofar, so good. Would it be an idea to also add an item which devices are supported and which not? I would remove the item "Dead ROM/Kernels", they are of no use for your thread and may cause confusion.
kindest regards,kuzibri
Click to expand...
Click to collapse
That item is meant for stuff like AOKP where its dead, but for those who want kitkat then they can refer.
sd_shadow said:
Here is a big list of porting and compiling rom guides
[Guides][Updated] All Guides @ One Place By Hpsgill by Hpsgill
Click to expand...
Click to collapse
Will have a look and add to useful links section.

This thread is gonna take really long to get updated I am very busy with school haha...

limjh16 said:
This thread is gonna take really long to get updated I am very busy with school haha...
Click to expand...
Click to collapse
Why did you choose to start such a thread, which is very time consuming, when you are so busy with school? If I were you, I would restrict your available time to make an index thread of your own devices (i9305 or SGS3-LTE). I can understand your wish of creating the thread that's in your mind, but you do need/have the time to create and maintain it, which is IMHO almost impossible when you are also at school. If you still want to create this ALL ROM EVER thread, ask help from other members to help you, cause you cannot do it on your own. Nevertheless, if you still want to continue with this ALL ROM Ever thread, I'm willing to help you where ever I can. :good:
kindest regards, kuzibri

kuzibri said:
Why did you choose to start such a thread, which is very time consuming, when you are so busy with school? If I were you, I would restrict your available time to make an index thread of your own devices (i9305 or SGS3-LTE). I can understand your wish of creating the thread that's in your mind, but you do need/have the time to create and maintain it, which is IMHO almost impossible when you are also at school. If you still want to create this ALL ROM EVER thread, ask help from other members to help you, cause you cannot do it on your own. Nevertheless, if you still want to continue with this ALL ROM Ever thread, I'm willing to help you where ever I can. :good:
kindest regards, kuzibri
Click to expand...
Click to collapse
I didn't expect my first term of school to be so hectic, I created this before my term started. It's alright, I'll just leave this here. Not like anyone except you and sd_shadow comes here... but I'll try to update once a week.

To be honest most won't bother as not all roms are available for all devices.
Also don't put any fair in what someone else thinks of a rom. Their opinion almost never really matters.

zelendel said:
To be honest most won't bother as not all roms are available for all devices.
Also don't put any fair in what someone else thinks of a rom. Their opinion almost never really matters.
Click to expand...
Click to collapse
Hmm true... But I created mostly for me cuz I was just going around xda finding a ROM to build so I thought this thread would help.

limjh16 said:
Hmm true... But I created mostly for me cuz I was just going around xda finding a ROM to build so I thought this thread would help.
Click to expand...
Click to collapse
No sure where it would help but ok. Going around building roms from other groups will not last long. More and more teams are closing their source and not letting others use it.
So if your worried about building then I would start my own project and start from scratch with it. Aosp not CM

zelendel said:
No sure where it would help but ok. Going around building roms from other groups will not last long. More and more teams are closing their source and not letting others use it.
So if your worried about building then I would start my own project and start from scratch with it. Aosp not CM
Click to expand...
Click to collapse
Well I just started learning how to build so idk how to start off my own ROM project... But I am interested...... Teach me please...?

limjh16 said:
I didn't expect my first term of school to be so hectic, I created this before my term started. It's alright, I'll just leave this here. Not like anyone except you and sd_shadow comes here... but I'll try to update once a week.
Click to expand...
Click to collapse
Hi,
it's no problem that it will take longer that you thought initially. I agree with @zelendel regarding this: "So if your worried about building then I would start my own project and start from scratch with it. Aosp not CM" Cyogen Mod is a world on it's own and accepted as a fully functional OS. Regarding the fact that only sd_shadow and I, besides zelendel now, only visit your thread, is logical because it's a WIP.
kindest regards, kuzibri

Arter's paid kernels

We all know the Linux kernel is licensed under a specific license (GNU GPL). Arter is currently selling his kernel builds for a minimum of $2 per month to his patrons only. This is ridiculous. So we decided to mirror the build for those who can't compile it or bother paying for a kernel based on the Linux kernel itself.
MOD EDIT: DOWNLOAD LINK REMOVED
You can join our official telegram group for the latest stuff, discussion and assistance.
MOD EDIT: LINK REMOVED
Note: This isn't supposed to work on pie ROMs or Q ROMs using Pie blobs.
Enjoy

The fak is wrong with him lol

EugenStanis said:
The fak is wrong with him lol
Click to expand...
Click to collapse
Ask Arter

hbuilder said:
We all know the Linux kernel is licensed under a specific license (GNU GPL). Arter is currently selling his kernel builds for a minimum of $2 per month to his patrons only. This is ridiculous. So we decided to mirror the build for those who can't compile it or bother paying for a kernel based on the Linux kernel itself.
MOD EDIT: DOWNLOAD LINK REMOVED
Note: This isn't supposed to work on pie ROMs or Q ROMs using Pie blobs.
Enjoy
Click to expand...
Click to collapse
Link to original post patreon please

exodius48 said:
Link to original post patreon please
Click to expand...
Click to collapse
MOD EDIT: LINK REMOVED

hbuilder said:
MOD EDIT: LINK REMOVED
Click to expand...
Click to collapse
I'm not going to use a kernel from a great developer who tweets this:
3. The Poco community *really* sucks.
I've never had this amount of people constantly:
Click to expand...
Click to collapse
There is no such thing as good community. There are always poking members and members who appreciates the work the developers do. If you simply believe that the community sucks, you should simply move on and stop developing for them.
I hate to see a talented guy got on nerve just cause of few members eta posts. This should not be posted here neither we should make fun of the work he did.
With respect to the dev and his work, I'm really sad to see where the community lost a good developer for those who simply can't afford the paid versions and the dev who even thought of doing that. :crying:
Ps: there are many more awesome kernels by awesome developers. That's the beauty of open source and choice. Please close this and move on to a different kernel.

Thread closed, posting others work without permission
strongst
Forum Moderator