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.
Well as you all know, Nougat just landed officially on Newer Nexuses & AOSP Source code. and unfortunately N5 wasn't "good enough" to get official google support, but we'll soon get Nougat test on our beloved N5 thanks to great Dev community supporting it.
but i was wondering the Question that title says !
though AOSP Source code is uploaded for 7.0 release , there are some binaries that i believe closed source https://developers.google.com/android/nexus/drivers#hammerhead , and i think they should be updated as well to properly work any new update on device , that's why we see binary files updated by google till now for every official update.
but as N5 is now drop-out of Official support,so google surly will not provide updated binary patches, so does hardware company (Broadcom, Qualcomm , LG ) provides these patches after official support OR our Dev do some digging even though they are closed source and finally by trial & error they fix/updates these binaries ? if it's done by Devs individually, wouldn't everyone's thought for dealing with problem might be different which ends up making some ROMs more stable on one area and others in some different area !
( PS: Well you might got it from Question it self that i'm not a proper technical person in Android and even in that matter in coding , i'm just a guy who wonder these thing & tried to find answer on google but didn't get any satisfactory so end up asking in new thread instead on QA thread so that some one like me also get to know about it also , my previous device (Samsung i9070 ), having closed source CPU (NovaThor U8500) & CPU maker drifted from business , gave insane trouble to XDA devs while porting unofficial updates, so they fed-up and drifted away to new device within months which makes me more curious about this Question, hopefully i'll get proper answer from a Dev/Experienced Member )
jineshpatel30 said:
Well as you all know, Nougat just landed officially on Newer Nexuses & AOSP Source code. and unfortunately N5 wasn't "good enough" to get official google support, but we'll soon get Nougat test on our beloved N5 thanks to great Dev community supporting it.
but i was wondering the Question that title says !
though AOSP Source code is uploaded for 7.0 release , there are some binaries that i believe closed source https://developers.google.com/android/nexus/drivers#hammerhead , and i think they should be updated as well to properly work any new update on device , that's why we see binary files updated by google till now for every official update.
but as N5 is now drop-out of Official support,so google surly will not provide updated binary patches, so does hardware company (Broadcom, Qualcomm , LG ) provides these patches after official support OR our Dev do some digging even though they are closed source and finally by trial & error they fix/updates these binaries ? if it's done by Devs individually, wouldn't everyone's thought for dealing with problem might be different which ends up making some ROMs more stable on one area and others in some different area !
( PS: Well you might got it from Question it self that i'm not a proper technical person in Android and even in that matter in coding , i'm just a guy who wonder these thing & tried to find answer on google but didn't get any satisfactory so end up asking in new thread instead on QA thread so that some one like me also get to know about it also , my previous device (Samsung i9070 ), having closed source CPU (NovaThor U8500) & CPU maker drifted from business , gave insane trouble to XDA devs while porting unofficial updates, so they fed-up and drifted away to new device within months which makes me more curious about this Question, hopefully i'll get proper answer from a Dev/Experienced Member )
Click to expand...
Click to collapse
Short answer: they don't. Either they use old binaries that still work, or they use binaries from similar devices that are updated. For example, the nougat build available here for the nexus 5 has been built on old marshmallow binaries. Only the kernel can be modified since it's open source. There is not much we can do with closed source blobs unfortunately...
Hi Folks,
I'm trying to port B2G to my moto g3. I was referring to this doc (https://developer.mozilla.org/en-US/docs/Archive/B2G_OS/Porting_B2G_OS/basics). However some of the things mentioned in this doc are not clear to me. Could you please help me with the below issue.
I'd like to build the AndroidKernel from source. So where should I include the below lines? Is it in this file?
https://github.com/LineageOS/android_device_motorola_osprey/blob/cm-14.1/rootdir/etc/init.target.rc
HTML:
on early-init
start ueventd
import /init.b2g.rc
Also if I understood correctly. building the kernel from source doesn't require to unpack , edit the init.rc file and repack the kernel from the device. Could you please confirm this?
Thanks,
Arun
Hi Arun,
I totally understand your frustration with this. You'd like to contribute to the Servonk project but first you need to port B2G to your phone or buy a new phone. Since the only other supported phones are the Z3 compact and Nexus 5, both of which are still relatively expensive secondhand, you want to use your Moto G3 which means first porting B2G to it.
So, I think there are two options you have:
1. Port direct from the AOSP code
2. Port from the CM12 code.
As Gerard said in telegram, porting from CM to B2G was never finalised so may actually require more work. However there may actually be more people here who can help you since people seem more familiar with CM than AOSP (in general, I know some people are very knowledgeable in both).
I see you've posted in the AOSP 7.1.1 kernel thread. Unfortunately, for the Servonk project you currently need a Lollipop based build, so 5.x AOSP kernel or CM12.x.
It might be worth asking a mod to move this thread into one of the development sub-forums.
As you know, this is the limit of my knowledge, but I really hope you find some success, if would be great if you could contribute to the Servonk project.
Your last option is to use the desktop build of Servonk, based on Glutin instead of Gonk, but I understand that you really want to get Servonk working on your phone.
Best of luck