Develop Bugs

[Q] How to cook a ROM?

I've been looking into creating my own Galaxy Nexus ROM but I can't for the life of me find out where to start. This is mainly going to be just for entertainment purposes of course.
As far as I know (which is not very much at all) I must compile the AOSP source code. The problem is I don't even know what compiling is. I don't mind if I have to learn as I have a very high interest in this and I'm possitive that I could learn fast.
Could someone please point me in the right direction to making a ROM?
I've also heard of people doing RAM optimizations,fullu deo-dexed, init.d scripts and speed optimizations. How would one go about doing that?
Any help would be GREATLY appreciated.

You have a lot of reading ahead of you.
I know there are guides for some of the things you mention at freeyourandroid.com but honestly man start reading
Android - making grown men pee sitting down since 2.0

Read the stickied post in the general forum on how to compile from source.
Also, you should really know and understand how the android system works before making a rom.
Sent from my Galaxy Nexus using xda premium

Hypercore said:
As far as I know (which is not very much at all) I must compile the AOSP source code. The problem is I don't even know what compiling is.
Click to expand...
Click to collapse
Let's start here. Do you know much about operating systems? You say you don't know what compiling is... so I take it you've never done any programming, even, say, a quick intro class in university? That's not a huge deal--I'm no programmer but I work with OSes all the time (especially Linux) and have learned a lot of scripting here and there.
I'd say start with learning about how Android works internally. Might even want to read up some on Linux if you don't know much about it, since that's the foundation.
There are plenty of guides on various forums (at least, there used to be) here, but a good place to start is to take an update .zip file and pick it apart. Start with a basic AOSP ROM, maybe, and start digging through it on your computer to see what's there and what does what.

[Q] Help porting E4GT goodness to SCH-R760(USCC)?

Hi, all. I picked up a new GSII from USCC a few days ago and I wondered what exactly has to be done to port CWM and/or roms from the E4GT to our phone. I'm hoping that the process will be fairly simple since our GSII is identical to the E4GT, excluding the WiMax radio.
Bear in mind that I'm running Ubuntu 11.10 before you give me Windows answers. But any and all help is appreciated. Your positivity could be the help I need to become a real dev.

Until you guys get a kernel source drop (Sammy's too busy violating the GPL... again...), it'll be difficult to know what is and is not actually different.
You may get lucky and it'll primarily be a kernel swap and maybe a RIL swap - but not guaranteed.

Source has dropped on Samsung site https://opensource.samsung.com/reception/receptionSub.do?method=list&menu_item=mobile&classification1=mobile_phone under SCH-R760U. Anyone give us some help on this, I'm also willing to give some porting a go, just need a little kick in the right direction.

Looking to study Kernel Development could use some pointing in the right direction.

Looks like im getting involved earlier than I planned. But other than compiling a stock kernel from source. The guides for our phone never really got finished. Looks like the international guides as well as android kernel guides in general will lend some guidance.
So if anyone can point me in the right direction. Maybe even help when i get stuck.
Guides I found for our phone:
http://forum.xda-developers.com/showthread.php?t=1291122
http://forum.xda-developers.com/showthread.php?t=1442870
http://forum.xda-developers.com/showthread.php?t=1494804
I realize the problem with leak kernels on our phone other than not having source is with recovery being part of the initramfs. After reading up on the initramfs scheme one would think we can extract modify the files and repack it into the kernel like steady has been doing.
A quick google turns up a guide for the international gs2 which i hope will help me. http://forum.xda-developers.com/showthread.php?t=1294436
Then there is things like adding init.d support which i might be able to bug sfhub about. Most importantly building cwm to be packed into the initramfs. Also learned root was a part of the kernel but had i known zimage was the kernel partition I probably would have figured. But i have yet to look at either of these since I only decided yesterday to do this.
Im going to have this phone another 1.5 years so if were losing people I mind as well shuffle my projects and do this one now. I am not looking to create and maintain a custom cwm or anything.
Ive been a pascal programmer for 14 years. I can read and translate C syntax languages. I studied C++ but never having practiced it I can not write fluently without a reference in hand. I am a bit of a linux noob i mean i have compiled kernels and drivers even a from scratch gentoo install but that was all from instructions. Its one thing to do something its different to understand it.
I wrote this from my cell phone so sorry for worse than usual spelling grammar and lack of punctuation.

Also figured in my searching looking at threads started by formerly active devs might turns up some stuff.
Chris41g had a thread in the OG Epic section perfectly titled "To the people wanting learn to code kernels and roms for the Epic" http://forum.xda-developers.com/showthread.php?t=1177076
Edit - Having some time to read before i pass out that third guide that sweetwater did for our phone is rather complete up to date and he is still hanging around.

good luck man, i hope you get up and running with this. thanks for taking the challenge. the community is lacking in the kernel area and any support is greatly appreciated, by me anyway. thanks again.

Rain can you pm me?

RainMotorsports said:
Also figured in my searching looking at threads started by formerly active devs might turns up some stuff.
Chris41g had a thread in the OG Epic section perfectly titled "To the people wanting learn to code kernels and roms for the Epic" http://forum.xda-developers.com/showthread.php?t=1177076
Edit - Having some time to read before i pass out that third guide that sweetwater did for our phone is rather complete up to date and he is still hanging around.
Click to expand...
Click to collapse
Both of the E4GT guides will work no problem and are actually pretty simple, anyone here can do it. I promise that. There are some issues though. Our EL29 source is a little funky so building with the first E4GT guide will get you a booting CWM kernel but wifi will break. After A LOT of testing we found the problem in the init.d file and the fix is in Sweetwaterburn's github source. There were several of us who built kernels(even EL29 with CWM, which is weird that everyone still uses EL26 to flash AOSP but anyways...) and a few like interloper and agat who were able to incorporate various governors. That was around the time all of the leaks started so then the kernels just kind of fell of the map because why waste the time?
Now onto the ICS stock repacks.....There is a ton of risk in testing those. Look how many bricks steady and the team rogue had not to mention team troll and random users. Why not just wait a little till source drops? Once source drops building kernels will be a ton easier. Also Calkulin and the new guy(can't think of his tag) have built unsecure stock kernels so that should satisfy all of the needs for leaks.
Here is one Agat built: http://forum.xda-developers.com/showpost.php?p=22463351&postcount=265
here is another EL29 I built: http://forum.xda-developers.com/showpost.php?p=22461146&postcount=264

Thanks DTM. I read on Steady's G+ he is definitively moving away from the E4GT as he has given it to his wife.
The amount of activity and the people involved in SweetWaterBurns thread surprised me and now that I know that I don't think people should be too worried. I mean we already know part of this is a bit of impatience.
I will still be learning for the long run. Hope to see some good things with the community thread when the ICS kernel source is out.

RainMotorsports said:
Thanks DTM. I read on Steady's G+ he is definitively moving away from the E4GT as he has given it to his wife.
The amount of activity and the people involved in SweetWaterBurns thread surprised me and now that I know that I don't think people should be too worried. I mean we already know part of this is a bit of impatience.
I will still be learning for the long run. Hope to see some good things with the community thread when the ICS kernel source is out.
Click to expand...
Click to collapse
I encourage everyone to attempt a kernel. I have no formal computer training and I just dual booted my laptop, next thing you know I was churning out kernels. We definitely need some variety in our kernel selection, I just don't advise it for the leaks unless you can afford some bricks. Because we have beast "big brother" in the international SGSII community it is pretty easy porting over some of their modifications to our source code via winmerge or copy and paste. It is also a lot less risky than messing with leaks.

T-Mobile GS3 CM9: How do we get started?

I badly want to help get CM9 working, or at least learn from trying, on the T-Mobile variant of the GS3. I'm a pretty decent hacker, but I know I don't have enough / any experience with the Android OS / Kernel development to work on the GSM/LTE portions of the ROM. However, I feel that if someone could help me and anyone else interested to get the toolchain setup and source properly downloaded, we could help with the easier portions of the ROM and learn a little about the complex portions of the ROM just by watching what the more experienced devs are doing.
Right now, it seems like ...maybe.. a few people are working on their own rather than a collaborative effort (except the Sprint variant that has Team Epic working on a ROM). I don't want to slow progress by taking up a bunch of valuable dev time, but if one person could just help get some of the less experienced people off the ground, we could probably accelerate this effort...
In the meantime, would you guys mind posting some links to the best resources you have found for getting started building CM or even building Android in general? It doesn't really matter if it's a guide for a different device. I have searched but there is so much information missing in sources I have found.
Thank You,
KevlarTheGreat

Count one more.
I would love to get involved. I have a good amount of Linux and C experience (7+ years), but need a good place to start with Android ROM development (specifically for the GS3).
Sent from my Glitchy CM9 Fascinate

mybook4 said:
Count one more.
I would love to get involved. I have a good amount of Linux and C experience (7+ years), but need a good place to start with Android ROM development (specifically for the GS3).
Sent from my Glitchy CM9 Fascinate
Click to expand...
Click to collapse
M'ladies and gents, couldeth you count a third member of this exquisite inquiry.

Team Epic is sorting it out, just be patient:good:
http://www.epiccm.org/2012/06/sprint-sgs3-cm9-development-plan.html

That is if it truly works on all carriers phones without trouble.

kscasper13 said:
Team Epic is sorting it out, just be patient:good:
http://www.epiccm.org/2012/06/sprint-sgs3-cm9-development-plan.html
Click to expand...
Click to collapse
From what I understand, they are sorting it out for Sprint but T-Mobile is much different because it's GSM. Here is their reply to me when I asked if there would be CWM install scripts that would support both T-Mobile and Sprint from the same ROM:
From this post: http://forum.xda-developers.com/showpost.php?p=28021070&postcount=23
CMTeamEpic said:
No, there will not be ROM's that work on all variants. CDMA and GSM are quite different.
The tools like CWM will work on all variants (if made properly) because they don't use the radios.
Click to expand...
Click to collapse
I'm a bit surprised at this answer because I'm coming from the HD2 where tytung has two different versions of the kernel in his amazing CM9 ROM. It chooses which one to install automatically based on which radio support you have PPP vs RMNET.

[molly] seeking collaborators to build Ubuntu ROM

I've begun looking into building an Ubuntu ROM for the ADT1 (molly) device. After some initial investigation, I anticipate one problem will be the kernel version. The device is on a v3 kernel, so that will limit us to an older version of Ubuntu unless we find a new kernel with the right modules and / or source. My initial goal will be to get a basic userspace with SSH running.
If you'd like to help, let me know! I've done a lot of Linux and Android dev, but it has mostly been on x86, so particularly it would be great if someone with ARM experience (especially Tegra) would help. I'll be digging into the Linux for Tegra project to see what I can get from it; it looks like the L4T version that most closely matches is E17.
(Also: long time lurker, only recent poster... so if you have suggestions on how to move forward or if I'm not following best practices, please correct me!)

doctorjei said:
I've begun looking into building an Ubuntu ROM for the ADT1 (molly) device. After some initial investigation, I anticipate one problem will be the kernel version. The device is on a v3 kernel, so that will limit us to an older version of Ubuntu unless we find a new kernel with the right modules and / or source. My initial goal will be to get a basic userspace with SSH running.
If you'd like to help, let me know! I've done a lot of Linux and Android dev, but it has mostly been on x86, so particularly it would be great if someone with ARM experience (especially Tegra) would help. I'll be digging into the Linux for Tegra project to see what I can get from it; it looks like the L4T version that most closely matches is E17.
(Also: long time lurker, only recent poster... so if you have suggestions on how to move forward or if I'm not following best practices, please correct me!)
Click to expand...
Click to collapse
Not sure on the other stuff but will be more than happy to test

ill be happy to test too

I teach CS and the new semester has kept me busy. But when things slow down I'm planning to dig into this. I anticipate the biggest issue will be with drivers for the latest versions of the Linux kernel. If I can resolve those (big if), this is probably doable.

I mean, we already have a 3.10 port mostly done https://github.com/oscardagrach/android_kernel_google_molly/commits/molly_testing - and oscardagrach also had mainline running on it a tone point (albeit we lose XUSB support, and therefore Ethernet on molly).
3.10 makes sense as a target kernel.
We had a relatively recent version of Debian booting like 2 years ago.
Project just fell off as we lost interest sadly - that kernel is a good place to pick back up though.

This is great to hear - thanks! I think we may have corresponded a bit by email before. Do you know if the version of Debian that was working was systemd based? At least on paper, systemd requires Linux 3.13, so I was shooting for what it would take to get that working. Perhaps the differences are small enough. For better or worse (not touching that debate) systemd is used by most of the recent distro releases. I was digging a bit into the Tegra Linux releases for NVIDIA too and thinking I might be able to get some insight from that.

I'm looking for this project. I Can't help develloping but I Can test. Thanks a lot

NOT asking for an ETA but just checking to see if this project is still going

Hey! I'm still working on it but I had to pause again (got busy at work). One challenge is finding a way to run an advanced enough Linux kernel to support systemd. I know some people hate it, but most modern distros are based on it. Hoping to have some time soon again!

doctorjei said:
Hey! I'm still working on it but I had to pause again (got busy at work). One challenge is finding a way to run an advanced enough Linux kernel to support systemd. I know some people hate it, but most modern distros are based on it. Hoping to have some time soon again!
Click to expand...
Click to collapse
Good deal, just wanted to make sure. I still have mine sitting by my desk

Still going to be i386 or x64? Thanks for the effort, very interested to see how this progresses. I had a lot of fun last year dabbling with the Debian build.