Database Users

CyanogenMod Port - Lets do this!!

POLL ENDS ON MONDAY (APRIL 25TH) AT 12:00 GMT
FIRST THING WE NEED DONE WILL BE TO GET CM/GINGERBREAD BOOTING regardless of the number of functions working
Dear SG3ians,
The time has come for us to take our beloved phone to the next level! Let's port Cyanogenmod (or gingerbread). I believe that if we unite this is a realistic possibility!
It might start off slow, it might take time, and there will definitely be hurdles to cross, but I know we can do this!
Who's with me!!
How was my motivational speech?
Ok, now lets get to more concrete stuff.
I suggest reading this (will update with link when able to. Go to cyangoen forums porting and read the sticky thread) and trying to follow this in our endeavor.
This is how suggest to proceed:
Phase 1:
Deciding what to port, getting a general outline of who will be involved, and planning+suggestions.
Phase 2:
Getting CM (or gingerbread) to boot and seeing what functions and what doesn't function
Phase 3:
Dividing up the non functioning work between devs/dev teams.
Phase 4:
Enjoying our "new" phones
I know this is a simplistic outline, but the sooner we start the sooner we finish.
For this to work it will of course require high interest within the community, it will also require civilized cooperation between members of the team.
Some other stuff (PLEASE READ BEFORE POSTING):
Please do not start posting posts like "I want CM too!" "+1 great idea for making the thread" "I'm interested how can I help"
Show your support by voting in the poll, more votes means you support this.
If you are interested in helping, say what knowledge you have and what you think you can do. For the time being I will start out with two main groups. Devs and testers. Testers will divided into alpha (will/can also test beta) and beta testers. Everybody involved (especially devs and alpha testers) have to say that they are aware of the risks (and be aware of the risk, duh ) that are involved in participating in this, and that all responsibility for any damages is all theirs. Devs will probably be furthered divided, but not at the present time. I will include the group potential devs (people who have some potentially useful skills/knowledge) for the time being. If potential devs dont become devs they will automatically be thought of as alpha testers, if you dont agree with this note it in you application post (and state if you want to then be considered as a beta tester or not participating at all if you dont become a dev). So if you wanna help post a post with one of the 4 choices and include the risk part (-only if you agree to it of course)
I have added the advisor group for people who dont have the phone but want to help with their knowledge
Any suggestion or ideas will be helpful, but try to check if somebody already proposed it, and if possible apply and suggest in the same post
I have made a dropbox for this project, if anybody knows/has a better alternative please let me know
User credentials will eventually be shared to select people (most likely only devs).
P.S. After I finish reserving, haree please move this to the dev section (if/when you are online)
P.P.S. If anybody is curious, this is stubborn_d0nkey. Thanks to clarkkov for inspiration
P.P.P.S. Latest CM means latest stable CM, not a nightly
IT IS OKAY TO POST NOW

Developers:
bhuvi - c, linux and core java

Potential Developers:
stubborn_d0nkey - some C, basic linux
AndroKite -medium linux/C (I'm assuming potential dev, if I'm wrong edit your post, or post a new one (but dont double post))
schopen80 -medium knowledge of linux, shell scripting, C and others
s3th.g3ck9 - (java)
powerpravin - drivers testing and a blazing fast brain

Can i help in the project?

Reserved, thanks for being patient!
wrong account, haree please delete this and the above post
@ above post. read the OP, read the bolded!

Alpha Testers:
CJHolder -basic linux
Pauri
jazux - very early alpha tester

Beta testers:
anant.0097 - maybe alpha tester
sekhargreen
chandradithya - maybe alpha tester

Advisors :

Helpful info:
Thread on cyanogenmod forums about general porting

Reserved, thanks for being patient!!

Reserved, thanks for being patient!!!

Reserved: YOU CAN POST NOW!

I'd like to be a potential developer. I have some knowledge of C and basic linux knoweldge. I am fully aware of all the risks, and I accept that I am responsible for all damages to my phone.
P.S. This is how an application post should look like
P.P.S. Basic linux does not mean that you are able to use linux for surfing and stuff, it means basic knowledge of more advanced linux stuff (ex. terminal)

I'd like to be a potential alpha/beta tester. I have some basic linux knoweldge. I am fully aware of all the risks, and I accept that I am responsible for all damages to my phone.

By Basic linux I mean I can use terminal etc. :L I use linux as my OS, Odin works fine in Wine!

CJHolder said:
I'd like to be a potential alpha/beta tester. I have some basic linux knoweldge. I am fully aware of all the risks, and I accept that I am responsible for all damages to my phone.
Click to expand...
Click to collapse
CJHolder said:
By Basic linux I mean I can use terminal etc. :L I use linux as my OS, Odin works fine in Wine!
Click to expand...
Click to collapse
Thanks!
(mostly for others)Listing knowledge/skills isn't that important for testers, and you dont really have to say what you mean by basic linux, I (I'm stubborn_d0nkey) just wanted to differentiate between two possible understandings of "basic linux" so people dont say basic linux when they take that as meaning day-to-day usage of linux (surfing, etc) since its not really helpful to the project

I want to help in the project I have some mediun linux knoweldge and C. I am fully aware of all the risks, and I accept that I am responsible for all damages to my phone.

I'd like to be a potential developer. I have medium knowledge of linux, shell scripting, C and others. I am fully aware of all the risks, and I accept that I am responsible for all damages to my phone.

You guys are doing a great job
But I must give some tips that I have
First try to do a sdk port
It just requires to take the boot.img from it and flashing it in FAST BOOT mode which we don't have
So there needs to be done other way
Secondly there are some threads which describe how to port cm to any phone
Take a look at them
Thanks,
cdesai

Talk to motofoca (mad-team)...he has ported gingerbread to g5...he can surely help...
http://Techass.wordpress.com

[REF] ICS User Experience Graphs (sentiment analysis)

I've decided to pull this project as it doesn't seem useful, or accurate! Feel free to pm if you have any ideas for me.
Where did the other benchmarks go?
All ICS ROM Benchmarks: this thread
Battery Drain Benchmarks: this thread
Kernel Features and Benchmarks: this thread
CPU Governors and I/O Schedulers: this thread
Power Saving Governors: this thread
Does SuperCharging work?: this thread

Methodology
I wrote a program in C++ with several routines:
1) copy all the thread's html all into one file
2) throw away all the html code
3) throw away anything from a quote
4) throw away any one letter words
5) throw away all punctuation except apostrophes/exclamation marks/question marks/periods/full-stops (also add a full-stop if it was missing at the end of a post)
Then the entire thread is uploaded in chunks of 400 words to an API http://www.alchemyapi.com/api/sentiment/
This returns a sentiment score for each 400 word chunk. It can be either positive or negative. Since most users are polite when they have a criticism, the scores tend to range from slightly negative to very positive.
[Q] What is 'sentiment analysis'?
[A] Find out more here: http://en.wikipedia.org/wiki/Sentiment_analysis
- - - quote "Computers can perform automated sentiment analysis of digital texts, using elements from machine learning such as latent semantic analysis, support vector machines, "bag of words" and Semantic Orientation — Pointwise Mutual Information..." sourced from the above link.
Each 400 word block gets a score usually ranging somewhere between slightly negative and very positive. Each score forms the basis of my raw data.
I currently show this data as several graphs, but I may strip away some. The most useful graph (remember, my background is mathematics education...) is a combination of the entire thread's average score plus the average for the most recent 10%. This helps to highlight threads that have a history of good sentiment as well as continuing good sentiment.
Notes
Initial attempt (for posterity): http://forum.xda-developers.com/showpost.php?p=24451874&postcount=712

I couldn't have done this without the support of a few people in particular: tchaari (who first informed me of this marvellous field of sentiment analysis); harbb for joking around with me (which got me thinking about doing it for real); and glennkaonang for feedback and moral support. Special thanks to original21 who inspired me to provide the most recent data separately.
Thanks to the XDA community in general, the developers, and a special shout out to others who have been supportive in my previous works: CyberGR, simms22, morfic, krarvind, wildestpixel, kong, Oodie, steve.garon, brainmaster, mathkid95, DaXmax, AndroidUser00110001, hope I didn't I forget anyone
Thanks to anyone past, present and future who has any constructive criticism, or just hits my thanks button! It keeps me going! Thanks to the moderators for keeping me in check... and to google/samsung for the toys

another bedalus special treat in store

I have been thinking, you should actually join the Recognized Contributor as you contributed alot...
Sent from my Nexus S using Tapatalk 2 Beta-5

DaXmax said:
I have been thinking, you should actually join the Recognized Contributor as you contributed alot...
Sent from my Nexus S using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
+1
Nice to see that bedalus benchmarks are back
Very interesting work bedalus. The results in the spreadsheet are not always significant but it's a very good start that deserves many encouragements. I am thinking about if taking two words before and two words after each term can improve the readability of the results...
I have also another UX idea: coding some program that can evaluate (approximately) if a post is a positive feedback, negative feedback, a simple question or a simple answer. Then, a final average score is computed.

DaXmax said:
I have been thinking, you should actually join the Recognized Contributor as you contributed alot...
Click to expand...
Click to collapse
Thanks! I think I'm the most pleased with this one because it made me learn C++. I'm just wrapping my head around custom structs.
I've applied for the RC status. Don't know what the criteria are particularly, but I think I've produced some useful stuff. If I get it, I might order an XDA t-shirt, then my wife will be really concerned...

tchaari said:
+1
Nice to see that bedalus benchmarks are back
Very interesting work bedalus. The results in the spreadsheet are not always significant but it's a very good start that deserves many encouragements. I am thinking about if taking two words before and two words after each term can improve the readability of the results...
Click to expand...
Click to collapse
I'm one step ahead of you this time tchaari, the code for two words before and after is halfway there...
tchaari said:
I have also another UX idea: coding some program that can evaluate (approximately) if a post is a positive feedback, negative feedback, a simple question or a simple answer. Then, a final average score is computed.
Click to expand...
Click to collapse
Isn't that what your brain is for?
EDIT: I'm just adding the link you PM'd me so I can find it more easily: http://stackoverflow.com/questions/...-how-positive-or-negative-a-statement-text-is

UPDATE: Found the bug in my program that caused it to crash if there was only one page (with 50 posts per page) i.e. any young thread with less than 51 posts would fit on one page, and my program will only download the total number of pages -1 (it saves the last page for a new start page for when I update a thread). Fixed... now trying to get all the other threads.

bedalus said:
I'm one step ahead of you this time tchaari, the code for two words before and after is halfway there...
Click to expand...
Click to collapse
Not really surprised. You are the top benchmark specialist here
bedalus said:
Isn't that what your brain is for
Click to expand...
Click to collapse
Lol, that's true but we will all feel better if the machine can handle a little more computing and analysis from what our brains are cooking every day
You should really take a look on what's going on in the "natural language processing (NLP)" domain. If your program can be connected to some existing tools like [1] and [2], the results can be so interesting
[1] http://khassanali-nlp-research.blogspot.com/2008/01/nltk.html
[2] http://kmandcomputing.blogspot.com/2008/06/opinion-mining-with-rapidminer-quick.html
These are other refs on sentiment analysis and opinion mining from the NLP domain if someone is interested:
- http://en.wikipedia.org/wiki/Sentiment_analysis
- http://eprints.qut.edu.au/29301/1/c29301.pdf
Bedalus, you made us addicted to your benchmarks. If you close one more of your thread, I'll go on a hunger strike with Oodie

Wow ! This looks Promising
Let's see wht this gives us & yeah ! It was boring in NS forums without you . lol .

Welcome back sir
Sent from my Nexus S using XDA

Good to be back? At least I'm happy you are back!
Greetzz, jojoost.
Sent from my Nexus S using Tapatalk 2

Thanks for the kind words everyone! It's nice to be working on a thread again.
I got my program more stable. I found a more up to date version of wget for windows here by a guy called Oliver Krystal. It had the drivers built in.
I've removed the my program in the second post until I can locate the source of the instability. Last night I ran it and it managed to download most of the ROM threads, but crashed halfway through a long thread.
I'm going to tidy up the code and try and break it up into more manageable routines (most of the work is done in one long procedure at the moment, not very good practice... ) Then perhaps it'll be easier to debug.
When it's more stable I'll re-upload it.
@tchaari, maybe I do need to include some scoring algorithm, otherwise it's not really a benchmark is it! haha

Glad to see you back, bedalus.
This time you bring more headache to us having no experience at all in information technology with your testing methodology
Regarding improvements it needed, I think it's good enough already.
But the idea of that algorithm thing would make it more interesting, although it would bring more headache to me I guess
Sent from my Nexus S using xda premium

I changed a couple of things in the build, now it runs without crashing, so I re-uploaded the program to the second post (along with the spreadsheet).
The included 0threads.txt file currently includes all the 4.0.4 ROMs that were on my ROMs spreadsheet (didn't bother with 4.0.3s).
Any new ROMs I don't know about?
Does anyone want me to stick in any kernel threads? Theme threads? Threads from other phones?
STILL TO DO:
-Modify the program to update by starting to downloading threads at the point I last read
-See if I can implement a five word phrase
-See if I can find or create any language analysis program to score the phrases

bedalus said:
Thanks! I think I'm the most pleased with this one because it made me learn C++. I'm just wrapping my head around custom structs.
I've applied for the RC status. Don't know what the criteria are particularly, but I think I've produced some useful stuff. If I get it, I might order an XDA t-shirt, then my wife will be really concerned...
Click to expand...
Click to collapse
Lol. You contributed alot for the Nexus S development. Im sure the Senior Mod, will nominate you, if not, i will do it....

DaXmax said:
Lol. You contributed alot for the Nexus S development. Im sure the Senior Mod, will nominate you, if not, i will do it....
Click to expand...
Click to collapse
Cool! Thanks!

UPDATE: All 4.0.4 ROMs (that I currently know of) now in the spreadsheet. Just working on the index.

Another quality thread in the making I think!
Good to see you back I was getting worried when all your threads were closing.

Atrix Re-Birth Project

This page is dedicated to make a stable ICS-JB for the Motorola Atrix
Brief history about the project:
- Un unstable ICS for Motorola Atrix was leaked
- Developers worked on integrating kernel and drivers into existing build
- Kernel was found to be very unstable and new kernel is being ported to Atrix
- While we wait for the kernel, an ICS CM9 build is ready for anyone willing to join the challenge
Next step:
- Developers should get involved in fixing/enhancing the current build
- Code submission is done by forwarding the changes to the head development team for inclusion
Build source code is all available to anyone willing to participate. The build process follows CyanogenMOD builds.
Source Code location: https://github.com/MROM/android/tree/ics
Curent Team:
Project Managers: marcovrv and R3PL1C/\NT.
Head Developers: Epinter, MMontuori, and TPoint75.
Kernel developers: mvniekerk
Developers: Hayander, scanuto, ravilov, geleiahp, alberto88a, tachospeedo, Isaygarcia, digidrops, fanfantasy, hainguyen273, and caster62003.
Testers/Advanced Users: Carcara, EkzoMan, EMG92, Hayander, BusWah, Girafik, clockworkninja, rspaulo, Bravo9000, vigremrajesh, jlm-familiar, The-Milkybar-Kid, r3xx3r, ovitz, lightlord, ticiano_arraes, reix2x, Nargyle, diegofdg, shabeepk, pixut, Kaworu33, jhonnyx, Haxornator, fanhtc2, julian_fern, iximedaixi, heibailife, shadowed87, Matada02, Zeljko1234, tatperson, dibi91, NemeZZiZZ, Moonshield, bimasakti85, Cocolopes, Pont91, jeanpiere, pre4speed, jeffreygtab, nachobkcc, BravoMotorola and littleemp.
Without help, this project cannot continue.

Count me in for Rebirth
mmontuori said:
Dear fellow Atrix owners,
We all know by now that Motorola has cancelled the plans for upgrading to ICS, I was hoping myself to get the new drivers to update my own rom to ICS or JB. Well, this is not going to happen...
What do we do now?
We can either assume this is the death of this revolutionary device, or work on the Re-Birth. You probably know, but there are a group of developers working on upgrading the current Gingerbread version to ICS or JB. I am personally one of them...
We all need your help... we are donating our precious time and resources to make the Atrix 4G a better device that could last for another year or two, however, alone, we cannot continue with this...
WE NEED YOUR HELP...
If you are still reading this message, good, now it's time to decide if the Atrix is going to die in the couple of months or live for some time. We are looking for:
- People that can write code and troubleshoot (Android Java and C/C++)
- Testers
- Project managers (believe it ICS or JB is a full SDLC project)
- Android Advanced users not too scared of trying something new on their phones
- Donate Atrix Devices that you no longer need
- Of course, donations to at least justify the amount if time we spend on this
- If I forgot something, please reply to this thread with suggections
Again, you decide DEATH or RE-BIRTH
Take Care
Click to expand...
Click to collapse
It is certainly great to see commitment of this kind. I'm no DEV nor do i possess programming skills which could assist you. But please feel free to count me in as a tester and advanced user, more than willing to get his feet wet .

I will glady donate, as should others who wish to revive this device that surely isnt really outdated

I would love to be a tester and advanced user. I have 2 atrixes, so I can test to any extent on one of them. I would donate one but I need to have my main atrix as a backup to the s2 I am in the process of buying. So my backup backup is there for testing anything and everything needed.

I would have no problem in donating except I don't see anyone claiming that it is at all realistically possible to get the full ICS experience in our phones (meaning hardware acceleration and working camcorder). If that changes, I'd be happy to donate to keep my phone alive, but if it's just going to be another dissapointing waiting game with no outcome...
PS: Don't get me wrong, I'm not trying to rain on your parade or be an ungrateful bastard as I do really appreciate the work all of you devs put on this. I'd be happy to give money for a bounty.

i'd personally donate 50 dollars to the cause of keeping our phones alive. probably more as time went on as well, just to keep the project alive.
i would also be willing to test ANYTHING on my Atrix, as i have plans of replacing it soon anyways. the fingerprint scanner doesn't work anymore, and the touchscreen is dying.

I'm JUST NOW getting an Atrix and a Lapdock, a little late I know But count me as an advanced user willing to test anything. I hope to get webtop (In non-blur roms) working above all else, unfortunately since moto isn't willing to comply, that is also the most difficult task.

- Android Advanced users not too scared of trying something new on their phones
Click to expand...
Click to collapse
Count on me!

Love the intiative :fingers-crossed: I don't have any technical skills to share, but I'm willing to test and assist in any other way that I can.
Maybe we should get this posted on the Photon forums as well to consolidate the project?

Would you be able to develop a 3.x kernel?
Sent from my MB860 using xda premium

Tester and advance user!...
from the (m)ATRIX...

mmontuori said:
Dear fellow Atrix owners,
- People that can write code and troubleshoot (Android Java and C/C++)
Click to expand...
Click to collapse
One more developer ready here !

So you want to build a real ICS/JB ROM for Atrix?
Including a 3.x kernel, hardware acceleration and maybe working webtop?
If at least the first two things apply I would gladly donate for this one.:good:

nachobkcc said:
Count on me!
Click to expand...
Click to collapse
+1 :good:

You guys can count on me as a tester and advanced user!
Sent from my beloved Atrix

Android/Java developer over here. (Also some knowledge in C/C++)
Contact me via : [email protected]
---------- Post added at 01:07 AM ---------- Previous post was at 01:07 AM ----------
Android/Java developer over here. (Also some knowledge in C/C++)
Contact me via : [email protected]
If there is something i can do that doesn't take me a very lot of time (because of the for-a-life work)

This is possible but requires more than a couple of devs working close together to make it come true. And ofcourse, it will spend us certain time for fix the problem of Nvidia named Tegra2 by re-developing a brandnew driver for our device.
Once this mission completed, we can completely go further ahead to open up other attractive projects on this worth device

Definitely advanced user and tester. Have strong experience on tech related project management, just not on software development projects. Novice on java, almost intermediate on C, advanced in Pascal (dead language I know), but I think I'm a quick learner.
Have a "real" job, so time is limited but can arrange something. Just tell me where I can help.
m.rodriguez<at>computer.org
Sent from my MB860 using xda app-developers app

I am honored to be a member of this community!
Not a dev or a programmer here, but will do anything I can to give support.
Thank you all!
Sent from my MB860 using xda premium

I have some experience in Java, C/C++, the Android Framework and I am willing to learn more. But I also think, a project management is necessary to order issues, make possibilities clear, have a big picture, sharing knowledge. So, when you start, drop a message.

Kernel teacher...

Hey everyone, I'm looking for a developer who will be willing to help and teach me how to make a kernel! I would like to be able to add anything I want; meaning I'm looking for someone to teacher how to edit and add things to make it my own, not just teach me how to compile. I've never made anything deal with a source code, meaning I've never made an AOSP ROM nor kernel; I have made some touchwiz based ROMs, but that's a bit different. I would like to start by making something for the nexus 7 (WiFi only) then moving my way to the GsIII (d2spr). I'm currently using opensuse 12.3 KDE 64-bit, on its own HDD. Please, if anyone could help me and teach me, it would be greatly greatly appreciated!!!

What hourly rate are you willing to pay? LOL
What I would recommend you do is to start simply by:
a) installing the current NDK
b) downloading a complete stock kernel build tree as a tarball (.tgz)
c) setting up a build environment and successfully build the kernel
d) unpack an existing boot image, stuff your kernel in there, & re-pack it
e) boot it on your device. Does it run? Congrats! You are a kernel-builder!
The reason that I suggest this outline plan above is that it initially avoids learning git & associated tools until after seeing something you've built running on the device; that's a confidence-booster. That's the good news.
The bad news is that becoming a *good* kernel dev from scratch means that you simultaneously are learning kernel coding conventions, build tree structuring, and kernel APIs *plus* achieving an excellent understanding of how git & gerrit work.
In addition to some amount of original source code mods authored by a kernel dev, they spend a fair amount of time integrating patch sets (commits) coming from unrelated kernel projects (e.g. Linux kernel mainline or kernel mods from unrelated devices). Learning simple operations (commits) in git is easy enough, but understanding branch creation & multi-way merge strategies in the face of cherry-picks coming from arbitrary places is a bit of a mind bender the first time through it.
And there is the issue of compliance with the GPL. As soon as you decide to make public your work, you have an obligation to publish your sources.
There is at least one way to do this simply: don't worry about git/gerrit/github at all - use whatever source code control system you want, including none at all. When you are ready to publish, you publish a patch kit that transforms a specific commit on some other developer's (or google!) tree to your tree. That should satisfy the GPL.
Another thing to consider is to build these skills in an incremental fashion: if you have in mind a very specific kernel modification of original authorship as a first project, why not consider submitting your kernel patches as pull requests to an existing developer's kernel tree? If your patch/mod rocks, other devs will incorporate it - and probably be much more willing to answer twisty questions from you. You scratch their back, they scratch yours.
The point of the above two strategies is that they allow you to build skills incrementally rather than needing to know everything before you can begin doing anything. Don't try to learn it all simultaneously.
cheers

bftb0 said:
What hourly rate are you willing to pay? LOL
What I would recommend you do is to start simply by:
a) installing the current NDK
b) downloading a complete stock kernel build tree as a tarball (.tgz)
c) setting up a build environment and successfully build the kernel
d) unpack an existing boot image, stuff your kernel in there, & re-pack it
e) boot it on your device. Does it run? Congrats! You are a kernel-builder!
The reason that I suggest this outline plan above is that it initially avoids learning git & associated tools until after seeing something you've built running on the device; that's a confidence-booster. That's the good news.
The bad news is that becoming a *good* kernel dev from scratch means that you simultaneously are learning kernel coding conventions, build tree structuring, and kernel APIs *plus* achieving an excellent understanding of how git & gerrit work.
In addition to some amount of original source code mods authored by a kernel dev, they spend a fair amount of time integrating patch sets (commits) coming from unrelated kernel projects (e.g. Linux kernel mainline or kernel mods from unrelated devices). Learning simple operations (commits) in git is easy enough, but understanding branch creation & multi-way merge strategies in the face of cherry-picks coming from arbitrary places is a bit of a mind bender the first time through it.
And there is the issue of compliance with the GPL. As soon as you decide to make public your work, you have an obligation to publish your sources.
There is at least one way to do this simply: don't worry about git/gerrit/github at all - use whatever source code control system you want, including none at all. When you are ready to publish, you publish a patch kit that transforms a specific commit on some other developer's (or google!) tree to your tree. That should satisfy the GPL.
Another thing to consider is to build these skills in an incremental fashion: if you have in mind a very specific kernel modification of original authorship as a first project, why not consider submitting your kernel patches as pull requests to an existing developer's kernel tree? If your patch/mod rocks, other devs will incorporate it - and probably be much more willing to answer twisty questions from you. You scratch their back, they scratch yours.
The point of the above two strategies is that they allow you to build skills incrementally rather than needing to know everything before you can begin doing anything. Don't try to learn it all simultaneously.
cheers
Click to expand...
Click to collapse
Wow, okay, thank you! I'll start with that. Honestly I like having someone just point me in the directions then me teach myself the rest! That is probably the best thing to do all around. I just have somethings:
1.) If I get lost somewhere and am not able to find answer for something anywhere; do you mind if I PM you?
2.) Almost everywhere I read---including from source.android.com---it say, use Ubuntu; why? Do I have to? Ubuntu doesn't support my graphics card---and isn't easy to set up, even when using things from other OSes or just other stuff someone made---which is kinda needed because of my monitors.

jamcar said:
2.) Almost everywhere I read---including from source.android.com---it say, use Ubuntu; why? Do I have to? Ubuntu doesn't support my graphics card---and isn't easy to set up, even when using things from other OSes or just other stuff someone made---which is kinda needed because of my monitors.
Click to expand...
Click to collapse
I've used Unix/Linux for quite a long time, and if there is one thing that seems to never change is package dependency differences from distro to distro. Getting them resolved is mandatory (when you are stopped out by them), but typically quite a distraction from whatever it is you are trying to accomplish.
By using Ubuntu you will be following the footsteps of many others in front of you (including Google developers), and that means that when you encounter a problem, it will be very likely that exact problem has already been encountered and resolved, and you can find the solutions on the internet. That may not be the case for some other arbitrary distro. So, why make your life more difficult?
As far as kernel development goes, you can do anything you want inside a VM, assuming your machine has enough ram (say 4+ GB) and disk space (say 100G free). So get VirtualBox and create an Ubuntu VM.
There are small downsides to using a VM, but for code-building they are just fine - their performance in doing kernel builds is probably 95% of native metal.
jamcar said:
1.) If I get lost somewhere and am not able to find answer for something anywhere; do you mind if I PM you?
Click to expand...
Click to collapse
I would never commit to something open-ended like that - esp. since you said you have never coded anything before. You are free to PM me though, so long as you understand that I am free to choose not to reply. Given those ground rules, it might be better for you to just post your questions in public (say stackoverflow.com) so more eyeballs will see what you are asking.
cheers and good luck - you've chosen a pretty steep mountain to climb.

[Q] Some essential documentation badly needed

I read @Entropy512 write somewhere "we are more in need of developers than of testers at the moment"
To that effect I want to make an appeal to @maxwen @XpLoDWilD @Entropy512 @pulser_g2 and all other people who started the initiative to properly document out a few things
1. If a device maintainer wants to get his device added to omni ROM what should the steps be ?
2. To set up a omni ROM - compliant device tree what are the prerequisites. As in omniROM trees have been seen to be using a format of aosp.mk+custom.mk device makefiles where aosp.mk makes it AOSP-compliant and custom.mk is the omni additions. How custom.mk is to be made (a template maybe ?) should be be documented. In fact I would go out to say a device/custom/sample tree should be made as an example
3. Are there any guidelines as to how much the hardware side codes can be hacked with to make the devices supported ? (Many groups of developers have forks of hardware/qcom/* repos that are pretty liberally spread with #ifdef's and makes them break CTS/CDD in a huge way). How much will these hacks be supported ?
4. Obvious point, what are the fields in which you need help most badly as of now. That is to say ril/telephony experts are highly needed right now or are features the topmost priority or is the highest concern to make the hardware repos tip-top so that devices are completely stable
Also publishing some guides on how to get sources and build the ROM would be good too, but since you are looking for "Developers" right now, it can be assumed that they will figure that much out on their own at least

This documentation will be done.
Actually one of the key goals of omni is to properly document things.
Bear in mind exactly how early this is in the process - it was only yesterday we even made the links available for github...
Documentation will be a large part of going forward and it has been ongoing for a while. Currently that's the biggest task actually, much moreso than the actual development.
Developers don't only write code, they also write docs
To that effect, http://docs.omnirom.org is going to be the home

Among other things I want to do is a "patches for a given feature" document so it's easier to find out how a given feature (such as status bar brightness) was implemented.
I really want to do it before I have too many patches to put in there, but I also have tons of stuff to fix!

Entropy512 said:
Among other things I want to do is a "patches for a given feature" document so it's easier to find out how a given feature (such as status bar brightness) was implemented.
I really want to do it before I have too many patches to put in there, but I also have tons of stuff to fix!
Click to expand...
Click to collapse
What do you think about this idea? These common kernel patches could also fit into that document.

pulser_g2 said:
This documentation will be done.
Actually one of the key goals of omni is to properly document things.
Bear in mind exactly how early this is in the process - it was only yesterday we even made the links available for github...
Documentation will be a large part of going forward and it has been ongoing for a while. Currently that's the biggest task actually, much moreso than the actual development.
Developers don't only write code, they also write docs
To that effect, http://docs.omnirom.org is going to be the home
Click to expand...
Click to collapse
if I can be of any help let me know,
I would love to see this project start off right from the beginning with proper documentation about EVERYTHING
also +100 to @Entropy512 's idea. documenting each feature and how it has been added is really important
I strongly urge that submissions via gerrit should be enforced to have a well written description in the commit message too. (it is so much easier now with gerrit 2.7+ we can do it right inside our browser after the patch has been uploaded too)

championswimmer said:
if I can be of any help let me know,
I would love to see this project start off right from the beginning with proper documentation about EVERYTHING
also +100 to @Entropy512 's idea. documenting each feature and how it has been added is really important
I strongly urge that submissions via gerrit should be enforced to have a well written description in the commit message too. (it is so much easier now with gerrit 2.7+ we can do it right inside our browser after the patch has been uploaded too)
Click to expand...
Click to collapse
Yup. I've always tried to have a detailed commit message in anything I create, but I think we may need to start enforcing it so everyone does it.

Is there any kind of current features / bugs / patches list on the official build? Or even just a changelog?

orangekid said:
Is there any kind of current features / bugs / patches list on the official build? Or even just a changelog?
Click to expand...
Click to collapse
There are no official builds yet. Too early for that.
so much work to do.

Entropy512 said:
There are no official builds yet. Too early for that.
so much work to do.
Click to expand...
Click to collapse
Oh, I was under the impression there was a compiled "official" version for the N4, N7, etc...
No worries, in due time I'm sure. Be looking forward to the Nexus 5 build..

orangekid said:
No worries, in due time I'm sure. Be looking forward to the Nexus 5 build..
Click to expand...
Click to collapse
give us the device first

I follow Omni for the Nexus 5. Nightlies have started since Monday so I'd like to know if there's a general Omni changelog now or a specific one for each device.

I'm a developer without much ROM/Android development. I'd love to give a hand wherever possible, but like @championswimmer said, it's kind of overwhelming to jump in and help. I'm totally cool to be relegated to documenting things if that helps, but I also understand the interruption that it would cause for you guys to slow down long enough to explain what I need to know.
What I do have experience with:
Java
Jenkins
Minimal app development
Other crap that might or might not be helpful