Jenkins, our butler who builds nightlies for you

Jenkins, our butler who builds nightlies for you - General PAC Discussion

Hello all,
Let's start with a little introduction.
Hi! I am Dymion, one of the Developers working on our beloved PAC ROM, and the owner of one of the JenSlaves, I named it DympyDesk.
I know there's quite a lot of information in that first sentence already, but please, bear with me for a moment while I explain each of these pieces of information.
Let's start with the PAC ROM, but you probably already know what that is.
It's that one awesome custom ROM which has it all! Chances are you are running a nightly build of it right now.
Which brings us to the second part of information, the JenSlaves.
You're probably wondering what the hell a JenSlave is. Well, quite simply put, a JenSlave is one of the nodes on our Jenkins Server.
Each node of the Jenkins Server compile a nightly for a device, one at a time, and the Jenkins Server decides what node will build what device.
An example of one of these nodes is my PC, DympyDesk. I try to help where I can with building Nightlies, but there's a downside to this..Oh yeah? What's the downside?
Why, thanks for asking, the downside of my PC also being a JenSlave, is time.
You see, as my machine is building Nightlies for you all to enjoy, I can not use it for Development, and thus slowing down the progress of making PAC even more awesome.I see.. But what can I do?
Oh great! You're already thinking of offering your help, you must be a really awesome person!
Well, if you have a PC which is capable of compiling android withing a reasonable time limit, and you don't mind lending us your machine to make Nightlies for this awesome ROM, you can join our Jenkins Army!
Well, it's not really an army, it's a bunch of developers and contributors lending their machines to our Jenkins Server so we can make Nightlies happen faster.
However, just wanting to let your PC become a JenSlave is not just quite enough..
There are some (hardware) requirements when it comes to building Nightlies, and these requirements are as follows:
A quad-core CPU or better
8GB of RAM, or higher
At least 380GB free space for builds
Running Linux
A somewhat decent internet connection
If your PC meets these requirements and you still want to join, well, you are more than welcome to!Okay, you have my attention, but what's in it for me?
Ah, we knew this would happen, and that's why we also have a little reward for everyone who helps us out.
You get added to a Google Hangout group consisting of some of the Core Developers of PAC, there to help you out with certain Android Building related questions.
Maybe you have an awesome idea or a fantastic contributions, well, then this is the way to bring that to the attention of the Developers, isn't that just plain awesome?Okay, that seems fair and pretty awesome, sign me up!
Awh yeah! If you would be so kind to either reply to this thread, send me a PM, or hit me ([email protected]) or Papa Smurf151 ([email protected]) up on Google Hangouts, we can help you out from there.Before I contact you guys, I'm going to want a bit more info..
Well, that's understandable if you're going to lend us your PC.
We have created an easy install script which you will run, during the installation, we ask for a few credentials which are use to distinguish your JenSlave from the others.
The installation itself creates a new user, the "Build" user, which is used by Jenkins to compile Nightlies and send them to our FTP servers so other users can download the Nightly.
It also installs a service which is used for communication between the JenSlave and Jenkins, this will run in the background and automatically starts when your machine boots.
Also, Jenkins can't access any of your files or change any settings, so no worries on that front.Well, I love the work you guys do, but I can't help by being a JenSlave..
Oh no worries, as long as you enjoy our ROM!
As always, we still have a way for you all to track the current progress on Jenkins:
http://jenkins.pac-rom.com/
If you are waiting eagerly for a device to complete (or fail, if that's your thing), you can also watch the Console Output in real-time!
If you ever change your mind, or maybe you know someone who is willing to provide his PC, please do come back and contact us.Dymion.
XDA:DevDB Information
PAC Jenkins, Tool/Utility for the PAC ROM
Contributors
dympy, MaDc0w
Source Code: https://github.com/PAC-man
Version Information
Status: Testing
Created 2015-04-03
Last Updated 2015-04-03

is it 4.4.2?
dympy said:
Hello all,
Let's start with a little introduction.
Hi! I am Dymion, one of the Developers working on our beloved PAC ROM, and the owner of one of the DIBS (Distributed Build System) machines, I named it dympydesk.
We use DIBS to create nightlies for you all to enjoy, the process behind it is quite simple.
We provide you with a script that you can only run if you are authorized by us.
This script will install all the needed packages and create a new build user for you, we will only use that user.
It will also install a service which will run at start up and will register your machine with DIBS, so we will know we can send build tasks to your machine.
Then the fun starts and your machine will start working and when it's done, it will upload the nightly onto our servers and receive a new task, if there are any.
However, as fun and awesome as this all is, we have a little problem..
You see, we are running low on machines in our system. We currently have about 4 or 5 active machines that have to build all the nightlies for the devices we support.
Because of this our Development Machines are compiling nightlies all day, leaving less usable time to actually develop new features and make PAC a better ROM.
And now we get to the real point of this post, we need your help making nightly builds.
We usually start building around 1 AM Eastern Time, and builds used to take about 4 to 5 hours max, but this can vary depending on the number of machines we have.
The hardware requirements are as follows:
A quad-core CPU or better
8GB of RAM, or higher
At least 380GB free space for builds
Running Linux
A somewhat decent internet connection
We don't take over your PC, it will still be yours, we'll just be borrowing some of it's power and space when you're at work or asleep.
If you want to help us out, please reply on this thread, I'll be watching it closely, send me a PM, or hit me([email protected]) or Papa Smurf151([email protected]) up on Hangouts.
From there on we can provide you with the needed instruction for joining our build system.
Now you're probably wondering, what's in it for me?
Well, we will add you to our DIBS Hangouts group, which will mean you'll be able to directly contact some of our Senior Devs.
Your name will also be added to our contributors list, located in every PAC ROM and our website.
The current status of DIBS can always be viewed on our website, using the following link:
http://www.pac-rom.com/#Dashboard
We really hope you can help us with this, and we thank you in advance.
Dymion.
Click to expand...
Click to collapse
is the roms for mako are over 4.4.2?
thx

ohad129 said:
is the roms for mako are over 4.4.2?
thx
Click to expand...
Click to collapse
Please refrain from posting things like this, as it is completely unrelated to the thread.
Having that said, I do not own a mako, but I do believe nexus devices will still be supported.
Dymion.

I would be interested in this as it sounds cool. I'm currently 16, and plan on building my own pc , (with a friends guidance of course!) And I only have a 3 MB/s down connection vie satellite right now. We thinking about WiMax right now though.
Sent from my Nexus 7 using Tapatalk

ClutchX.LA said:
I would be interested in this as it sounds cool. I'm currently 16, and plan on building my own pc , (with a friends guidance of course!) And I only have a 3 MB/s down connection vie satellite right now. We thinking about WiMax right now though.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Internet speed just needs to be fast enough to DL source and upload 100 mb files at a decent rate.
If building your own PC hit me up on hangouts [email protected] and I can give u some links as amazon is selling lots of hardware on sale right now
XDA Moderator

ohad129 said:
is the roms for mako are over 4.4.2?
thx
Click to expand...
Click to collapse
I would but can i choose device how does it work? I would need to be taught or helped along with git, gerrit whatever you guys use havent learned that yet.
My PC specs.
----------------------
Pimped out ASUS G75VW (which means portable building gaming)
Dual boot
Windows8.1 250GB ssd 4 gaming >.-
and
Xubuntu 13.10 1TB HDD
16 GB's DDR3 ram.
-------------------
TWC internet
=========
New ASUS latest A/C 802.11 someting wireless
------------------
My knowledge + skills
- Fast visual learner through Team viewer or walked through once.
- HTML5
- CSS3 basics
- Blogger
- Site management
-----------------
Roms compiled
(Just started learning Android dev)
Pure AOKP Evita 4.4.2 two versions so far :: Link

dympy said:
-SNIP-
Click to expand...
Click to collapse
I'd be willing to help, 3930K at 4.8Ghz, 16GB RAM at 2133Mhz, 840 Pro SSD, 150/75 internet, but I have no experience with *nix and gerrit or dual-booting. If you can help me with that, I'll gladly build for you guys. :good:
Sent from my Nexus 5 using Tapatalk

Argumentation said:
I'd be willing to help, 3930K at 4.8Ghz, 16GB RAM at 2133Mhz, 840 Pro SSD, 150/75 internet, but I have no experience with *nix and gerrit or dual-booting. If you can help me with that, I'll gladly build for you guys. :good:
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Please hit me up on hangouts [email protected]
XDA Moderator

dympy said:
Hello all,
Let's start with a little introduction.
Hi! I am Dymion, one of the Developers working on our beloved PAC ROM, and the owner of one of the DIBS (Distributed Build System) machines, I named it dympydesk.
We use DIBS to create nightlies for you all to enjoy, the process behind it is quite simple.
We provide you with a script that you can only run if you are authorized by us.
This script will install all the needed packages and create a new build user for you, we will only use that user.
It will also install a service which will run at start up and will register your machine with DIBS, so we will know we can send build tasks to your machine.
Then the fun starts and your machine will start working and when it's done, it will upload the nightly onto our servers and receive a new task, if there are any.
However, as fun and awesome as this all is, we have a little problem..
You see, we are running low on machines in our system. We currently have about 4 or 5 active machines that have to build all the nightlies for the devices we support.
Because of this our Development Machines are compiling nightlies all day, leaving less usable time to actually develop new features and make PAC a better ROM.
And now we get to the real point of this post, we need your help making nightly builds.
We usually start building around 1 AM Eastern Time, and builds used to take about 4 to 5 hours max, but this can vary depending on the number of machines we have.
The hardware requirements are as follows:
A quad-core CPU or better
8GB of RAM, or higher
At least 380GB free space for builds
Running Linux
A somewhat decent internet connection
We don't take over your PC, it will still be yours, we'll just be borrowing some of it's power and space when you're at work or asleep.
If you want to help us out, please reply on this thread, I'll be watching it closely, send me a PM, or hit me([email protected]) or Papa Smurf151([email protected]) up on Hangouts.
From there on we can provide you with the needed instruction for joining our build system.
Now you're probably wondering, what's in it for me?
Well, we will add you to our DIBS Hangouts group, which will mean you'll be able to directly contact some of our Senior Devs.
Your name will also be added to our contributors list, located in every PAC ROM and our website.
The current status of DIBS can always be viewed on our website, using the following link:
http://www.pac-rom.com/#Dashboard
We really hope you can help us with this, and we thank you in advance.
Dymion.
Click to expand...
Click to collapse
I'm game.

theoctagon said:
I'm game.
Click to expand...
Click to collapse
Awesome! I'll hit you up in PM when I get to work!
Dymion.
Sent from my Nexus 5 using XDA Premium 4 mobile app

I've got a 6 core machine with 16g of RAM and a big honking RAID that's got a couple TB of room left of it. I've used it to build ROMs and kernels before, and it's running Ubuntu 13.10, 64 bit. The internet connection is 12mbit down, 1 Mbit up.
I'd be willing to help if you think what I've got is sufficient.

ssewk2x said:
I've got a 6 core machine with 16g of RAM and a big honking RAID that's got a couple TB of room left of it. I've used it to build ROMs and kernels before, and it's running Ubuntu 13.10, 64 bit. The internet connection is 12mbit down, 1 Mbit up.
I'd be willing to help if you think what I've got is sufficient.
Click to expand...
Click to collapse
That would be awesome!
Do you have hangouts? If so, hit me, [email protected], or Papa Smurf151, [email protected], up on hangouts and we can sort stuff out.
If you don't have hangouts, please send me or Papa Smurf151 a PM (Or both, that's also a possibility).
Dymion.

dympy said:
That would be awesome!
Do you have hangouts? If so, hit me, [email protected], or Papa Smurf151, [email protected], up on hangouts and we can sort stuff out.
If you don't have hangouts, please send me or Papa Smurf151 a PM (Or both, that's also a possibility).
Dymion.
Click to expand...
Click to collapse
I just opened a hangout with both of you in it and sent a message. See you over there.

Thanks
First off, thank you guys for the awesome rom. Secondly, I would love to help with the DIBS problem but I was wondering if there is a specific version of Linux I need to run for this? It would be about a week to a week and a half before I can start.

kingsugar said:
First off, thank you guys for the awesome rom. Secondly, I would love to help with the DIBS problem but I was wondering if there is a specific version of Linux I need to run for this? It would be about a week to a week and a half before I can start.
Click to expand...
Click to collapse
Just about any version of Linux, as long as it is 64 bit should work. We have mostly Ubuntu machines, but we also have Mint, Debian and others I may not remember at present.

Langes said:
Just about any version of Linux, as long as it is 64 bit should work. We have mostly Ubuntu machines, but we also have Mint, Debian and others I may not remember at present.
Click to expand...
Click to collapse
Okay once I have it up and running I will get in touch with one of you guys to get the rest of the instructions.

kingsugar said:
Okay once I have it up and running I will get in touch with one of you guys to get the rest of the instructions.
Click to expand...
Click to collapse
got a Q6600 @ 3GHz with 8GB of ram running arch.
building PAC works fine.
I could could keep it running for a few hours (~5-10 compiles a day).
- Chris

aHcVolle said:
got a Q6600 @ 3GHz with 8GB of ram running arch.
building PAC works fine.
I could could keep it running for a few hours (~5-10 compiles a day).
- Chris
Click to expand...
Click to collapse
Hey please hit me up on hangouts [email protected]
Dibs works a little different than you just building a few ROMs a day or what not
XDA Moderator

Is there any one distro that would work better then another? I can't get Ubuntu to install on my machine.

kingsugar said:
Is there any one distro that would work better then another? I can't get Ubuntu to install on my machine.
Click to expand...
Click to collapse
There are some guys running arch Linux, so I'd you can get that up and running, I think they can help you further with setting up dibs.
Just out of curiosity, why won't it install?
Dymion.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Related

[KERNEL] -2.6.35- Eternity Project for HTC Vision --- DIRTY --- TEST

Welcome to the Eternity Project Kernel for HTC Vision Thread!
The Eternity Project Kernel for HTC Vision (T-Mobile G2 & HTC Desire Z) is developed for gaining the maximum possible speed mantaining the maximum safety on our devices.
Features:
- Updated kernel (2.6.32.17 -> 2.6.35)
Kernel GIT Repository: http://gitorious.org/eternity-prj/eternityvision_2-6-35
Still some errors to correct.... and need help :|
Stay TuneD!

Thanks! Will test.

good stuff. porting the board files/dependancies, etc. is quite a bit of work, so my hats off to you!
will check it out.
thx for your efforts.

wow another?

I'm not 100% sure that I've ported all correctly (excluding some compiler errors that prevents the building ... and that I'm correcting)... so, well, pershoot, knowing your work I'd be proud if you take a look at the code
Anyway, I've corrected some other things, now I'm dealing with some errors on mddi.c ... I hope it'll be ready to test in some hours
Returning at work!
P.S.: It's ----SO---- dirty! I've uploaded it while testing and error checking!

kholk said:
I'm not 100% sure that I've ported all correctly (excluding some compiler errors that prevents the building ... and that I'm correcting)... so, well, pershoot, knowing your work I'd be proud if you take a look at the code
Anyway, I've corrected some other things, now I'm dealing with some errors on mddi.c ... I hope it'll be ready to test in some hours
Returning at work!
P.S.: It's ----SO---- dirty! I've uploaded it while testing and error checking!
Click to expand...
Click to collapse
yup for sure. i've gotten as far as the new QSD SPI bits, and put it down to work on other things... haven't gone back to it yet.

The new QSD SPI bits in the files uploaded are broken (prevents compilation), but locally I've already corrected them.
I've uploaded the files because I've done almost all the work, it needs only another percent of finalization...and I'm not committing every change in the same moment 'cause it would be painful
EDIT: Other things checked and fixed. Changes committed.
EDIT2: I'm stuck at the end. Anyone can help? Thanks!

Has there been any headway on this? I for one think this has a lot of potential.
Sent from my G2

thanks for your work. Is this kernel designed for AOSP or Stock or both? I'd love to have it compatible with Stock Rooted Rom

It's designed to work on stock Android, but I haven't had time to continue the work on it.
Unfortunately now I'm not at home and the only thing that keeps me connected is my G2...and anyway I'm on vacation with my girlfriend so you can understand the situation
However.
I'll watch at this when I'll get back home...
Resuming on 10/01

kholk said:
It's designed to work on stock Android, but I haven't had time to continue the work on it.
Unfortunately now I'm not at home and the only thing that keeps me connected is my G2...and anyway I'm on vacation with my girlfriend so you can understand the situation
However.
I'll watch at this when I'll get back home...
Resuming on 10/01
Click to expand...
Click to collapse
Ooo, you do what you have to do buddy and take your time! Have a great time with your loved ones and Happy new year to all!

Can I test this kernel on gingerbread/cm7 builds
Sent from my HTC Vision using XDA App

kholk said:
It's designed to work on stock Android, but I haven't had time to continue the work on it.
Unfortunately now I'm not at home and the only thing that keeps me connected is my G2...and anyway I'm on vacation with my girlfriend so you can understand the situation
However.
I'll watch at this when I'll get back home...
Resuming on 10/01
Click to expand...
Click to collapse
That is completely understandable, make sure you enjoy yourself. We can wait a little while in the backseat, but an updated kernel would be awesome . Just know that your efforts are appreciated. Thanks, and have fun!
thatruth132 said:
Can I test this kernel on gingerbread/cm7 builds
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Nandroid, and go for it . At it's current state I would expect a few things to be broken. Actually, gingerbread was designed to work with a .35 kernel so results might be favorable. The absolute worst thing that could happen is a bootloop, and you can fix that by flashing the stock kernel with adb. Let us know how it works.

Sounds cool..... stay safe
Sent from my HTC Nightmare G3

Bump for justice!
Do I need to build this to test on MIUI?
And can I OC to 1GHz with it? Or will I need to build one?
Or get someone else to build it

Android 2.3 (Gingerbread) Being Pushed To AOSP

http://www.androidpolice.com/2010/1...3-gingerbread-being-pushed-to-aosp-right-now/
go, go, go! )

These are very good news
I already see my Hero running CM 7
:happy face:

Excellent News Lets see who get's their GingerBread ROM out first

Sweet, if the hero really will be supported!

Cooooooooooooooool man very nice go go go go gooooooooooooooogle

Tchuup-tchuup! Hotness train is leaving the stations

ummm...
yea. will be interesting to watch... if it works on hero it will be fun... I don't expect devs will take the time on the hero any more like they used to but if someone out there has the know how and time and dedication then it's probably possible.

dkelley said:
ummm...
yea. will be interesting to watch... if it works on hero it will be fun... I don't expect devs will take the time on the hero any more like they used to but if someone out there has the know how and time and dedication then it's probably possible.
Click to expand...
Click to collapse
Feeyo...

Good news
Sent from my HTC Hero

C0mpu13rFr34k said:
Feeyo...
Click to expand...
Click to collapse
should be interesting to watch his progress

I wish the technical know-how would be something well documented.
What I mean is, ive seen lox/benocharm (sp?) progress in the last year in terms of Android knowledge, almost from the start. Ive seen one of these two guys post about initial questions about how things work, then edit his own post to do a mini-FAQ on ROM cooking. Now today it would look like they would kick some major ass at doing it if they were still able to give time for this, because they know the Hero hardware by heart; they know the usual glitch when porting (ie: how to make camera/bluetooth work, etc), all the minor details that makes a ROM usable or not for a day-to-day ROM! However, this kind of knowledge seems not so well documented.
What i'm basically saying is if a developer bails out the documentation about how to rebuild a custom ROM does too. It looks like (from a non-cooker point of view) that there is no centralized Wiki or webpage about the usual generic steps or roadblocks when porting from another device or when starting from AOSP to build FOR an Htc Hero (or any device, too).
Personally i know enough about linux in general, ive build a few updates.zip for my own knowledge's sake (nothing fancy though, removed/added apks ), but I have my questions on how to properly make something not built specifically for an Hero work with all the hardware functioning. I'm sure many others are in the same boat (plenty of tech knowledge but lack of Android ROM resources). For example, the question I had in mind were in the form of:
Does specific hardware components (gps, wifi, bt) relies on linux kernel modules? Does it need some kind of special APKS or Jars to make it work along with the framework, or just kernel modules are enough once loaded?
Following up on the point above: would copying modules from another device specific ROM would be sufficient? (I guess not), what about Android release versions (Eclair, Froyo, Gingerbread, etc)? Can modules work regardless of the Android version being run on?
ETC...
Well its pretty much a long rant, but since i'm stuck with a 3 year contract on Telus with an HTC Hero, I wouldnt mind giving a bit of my free time to make a working ROM out of it. However I am/was under the impression that the Hero ROM development scene went to a stop once Cyanogen started supporting Hero (seems to me there are only two *major* roms out there, CM and VillainRom), and due to that ROM cookers stoped caring about the Hero since it was well enough supported as it is (with CM on board).
Thanks for listening, doctor

I'm actually in the process of setting up an Ubuntu virtual box to dive right in, when I saw the AOSP sources getting pushed I thought why wait? Why not try it myself?
Don't expect anything soon. First of all I am just going to build off the Cyanogen tree and see if I can make a working ROM, then I will look into the deep dark hell that is porting software to HTC's proprietory-drivered-up-the-ass Hero

l0st.prophet said:
I'm actually in the process of setting up an Ubuntu virtual box to dive right in, when I saw the AOSP sources getting pushed I thought why wait? Why not try it myself?
Don't expect anything soon. First of all I am just going to build off the Cyanogen tree and see if I can make a working ROM, then I will look into the deep dark hell that is porting software to HTC's proprietory-drivered-up-the-ass Hero
Click to expand...
Click to collapse
Any luck with it? I had the same idea, reading now a lot of information about building a rom.

Maybe we can post some useful links or tutorials about building ROMs in this thread so that we can kind of collaborate?

That would be a great idea, i really like the idea of building my own rom. or at least try to build one.
Here you can find how to setup your own machine to build android roms
http://source.android.com/source/download.html
if you have problems with installing sun-java5-jdk follow the instructions on this page:
http://blog.enea.com/Blog/bid/32050/Ubuntu-9-10-Java-5-and-the-Android-Open-Source-Project

Also checkout Cyanogen's wiki, they really did an excellent job there:
http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Hero

I'm progressing... slowly. Downloading Ubuntu 10.10 iso, 200MB of updates, the SDK, Eclipse, the ADT plugin, all the platform updates and GIT is taking a while on < 2Mb connection...

Especially the repo syncing... that just takes ages ;

krispijn_s said:
Especially the repo syncing... that just takes ages ;
Click to expand...
Click to collapse
Gives me time to read I spose! I totally understand how to build off Cyanogen's code, that sounds simple, but I get a little lost when it comes to syncing with AOSP or branching Cyanogen to make changes... but I got hours of dowloading yet so I can read up about it then!

Make sure you download the x64 version of Ubuntu. Since 2.2.1 you need a 64-bit system to compile the Android OS project.
Also don't expect to get it compiling right away, I reckon somekind of cpu-profile is missing (could be named different). Third I heard that the sound and camera (again) systems got changed, could be buggers to get those working.
Just my two cents

[PROJECT][KERNEL] Join your efforts for HOX kernel development

I already saw a lot of kernel developers here, each of them posting their own version.
I don't think that "download sources / fix them / apply patches" by every one of them is ok.
If all could focus on a single source-tree and fix / apply patches to that we would get to a stable/improved version a lot faster.
I can provide a linux machine for the developers interested by this project.
Hardware: 2 x Xeon X7550, 16GB RAM (can be extended to about 60GB), 300GB of storage (can be extended) - RAID6, FC dedicated storage.
Example:
$ time make ARCH=arm clean
[...]
real 0m2.479s
user 0m0.953s
sys 0m1.151s
$ time make -j32 ARCH=arm CROSS_COMPILE=arm-eabi-
[...]
real 1m4.720s
user 19m11.694s
sys 3m23.190s
Click to expand...
Click to collapse
Software:
Slackware 64bit 13.37, gcc 4.5.2, gcc-arm 4.6.1
OS can be changed if you have good enough arguments.
SSH access, no root.
If any developer is interested by an account, pm me with the desired username.
Have fun!

Ok, if no one is interested, I have to start this alone...
BETA
First release - ALiCE Kernel - with patches/tweaks from eternity/franco/bricked kernels and some of my own. Everything seems to work on my HOX.
- Sweep2wake included
- modules built in kernel, no need to flash anything else but boot.img
Attached:
zImage - for including into your own boot.img
boot.img - InsertCoin 5.3.0 boot.img with this kernel.
DELETED ATTACHMENTS - Kernel was virtually unusable.
You can use zImage injector ( http://forum.xda-developers.com/showthread.php?t=1647398 ) to update your own boot.img

I like the idea of this collaboration of kernels.
And I like how the modules are integrated into the kernel.
I'll be testing this out more tomorrow with a battery test for a work day
Keep up the good work
EDIT:
3G Does not work.
As in it shows 3G/H on the top, but no network connectivity.
WiFi does however work.

Great
I'm not a kernel dev, but this seems like a good idea.
Kernel devs working together to create a solid/stable base kernel.
If they want to add specifics they can always release one aside of this.
Also good to integrate modules into boot.img
Keep up the good work.

+1
Good idea, and go on
Good work.

Well I build kernel in 1 minute on i7 920 @4.2 ghz, no need for you machine ;-)
But common git would be nice.. I have zero time to maintain a kernel for HOX
Sent from my HTC One X

It will be nice if we can have a common github repository for the OneX sense kernel with all the patch applies by the devs.
AliceXES, do you have a git link of your repo ?
Because I currently compiling the franco's repo with some config tweek for my own need. And I would like to compiling yours just for testing.
Anyways, thanks for starting your project

Please send me your twitter account it's for helping you

The biggest problems ain't hosting or building times, just version-control. A common Git would be nice, although it seems most changes get picked by eachothers at github.

What about a GitHub organisation? You can have free ones where everyone is admin if you leave the source open. But then that requires a certain level of trust I suppose, heh.

The problem was with modules - for some strange reason, 3G doesn't work with them built-in the kernel.
Also my laptop crashed. The 2nd HP 4520s dead in my hands.
I will probably won't work on this anymore until it's repaired.
Still, if anyone needs access to the compile-server, the offer is still open.

AliceXES said:
The problem was with modules - for some strange reason, 3G doesn't work with them built-in the kernel.
Also my laptop crashed. The 2nd HP 4520s dead in my hands.
I will probably won't work on this anymore until it's repaired.
Still, if anyone needs access to the compile-server, the offer is still open.
Click to expand...
Click to collapse
Sad happenings. Hopefully it'll be fixed soon so you'll be back on track!

1: 3G problem indeed lies in the modules (linked to one of the binary baseband module)
2: getting collaborators won't be easy; many (apart from a select few) of today's "chefs" (dare not call them devs) prefer to act alone, get the credits, instead of working together, where the progress would've been much faster. This has been discussed too many a time on xda.
It is so much easier to rip someone's work & claim it as your own... Which is why many a dev resorted to "protecting" their roms (for example, from dumping).
Another reason why not many would like to join you, is that then it would come apparent that they don't have any real skills, since they won't be contributing any patches. ;]

Why compare ROMs with Kernels though? Maybe I'm unique at this, I don't know but, I never really cared about moving files around at ROM level or building AOSP ROMs. I prefer the kernel-space just a bit more
If people are afraid that their commits get stolen (which unintently happened just a few days ago, it seems) they should sign-off it properly.
Ányway I'm always interested in collaborating. Atm I'm just foring Franco's kernel and fixing a few compiling warnings.. I think what we really need is one main-maintainer which holds the master-branch, then the rest of our bunch just can push commits to him for reviewing. Who this lad is going to be, is also a tricky one.

I don't think I will have any success with this project
I started my own kernel thread (here: http://forum.xda-developers.com/showthread.php?t=1662781 ), sorry.
Anyway, the invitation is still open.

[ROM][AOSP][Nightly/Release] CarbonRom KitKat [Hercules]

About Carbon
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub. and on our Gerrit CarbonDev Gerrit.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Features
All of our features can be found on our site here:
Carbon Features
Here are some screenshots:
Carbon Screenshots
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users.
Download Carbon
All Carbon downloads and further information such as features, changelog, and FAQ can be found on our website.
Carbon Downloads
Changelog
For a detailed changelog, check out the changes made each night here:
Carbon Changelog
Support
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Who is Team Carbon?
Find out here:
Carbon Team
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!

XDA:DevDB Information
Kitkat CarbonRom for T-Mobile Galaxy S2, ROM for the T-Mobile Samsung Galaxy S II
Contributors
Somcom3X, somcom3x, CarbonDev
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Flash cm-11.0 first.
Based On: AOSP
Version Information
Status: Stable
Current Beta Version: Nightlies
Created 2014-01-30
Last Updated 2014-08-24

Reserved

Reserved

I'm your maintainer
on a side note: delta has been added, it downloads only the changes in the ROM and you one click flash them from the app. It's basically ota

First Will download and flash in a bit. Thanks

Official Carbon KK! Very nice, sir.

You were hinting at this the other day in the other Carbon thread, looks like things are about to get very interesting around here. In more ways than one too.

Can't wait to flash!!
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app

Sounds good

Under Carbon Fibres -> Device Tuneables, The page is blank. Is this expected or did I mess up? I assume this is where you would toggle Halo, Ribbons, DPI, etc. No worries if it just isn't there yet! Looking great!
Thanks

Grichecth said:
Under Carbon Fibres -> Device Tuneables, The page is blank. Is this expected or did I mess up? I assume this is where you would toggle Halo, Ribbons, DPI, etc. No worries if it just isn't there yet! Looking great!
Thanks
Click to expand...
Click to collapse
Ah. That section is meant for devices that need/have special functionality. Kind of like vibration settings etc... It's device specific.

ArtfulDodger said:
You were hinting at this the other day in the other Carbon thread, looks like things are about to get very interesting around here. In more ways than one too.
Click to expand...
Click to collapse
I was hoping someone would notice.
Sent from my SAMSUNG-SGH-T769 using Tapatalk

Somcom3X said:
I was hoping someone would notice.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Yeah I'm testing this now, Carbon is an awesome ROM no matter what version I've tried previously. The community here will embrace this undoubtedly. Can't wait to see the progression to stable but looks like the ROM has some pretty neat features already including active display.
I plan on using this with no scripts or tweaks for the time being either, see how it does.

ArtfulDodger said:
Yeah I'm testing this now, Carbon is an awesome ROM no matter what version I've tried previously. The community here will embrace this undoubtedly. Can't wait to see the progression to stable but looks like the ROM has some pretty neat features already including active display.
I plan on using this with no scripts or tweaks for the time being either, see how it does.
Click to expand...
Click to collapse
Only ROM with both active display and lock screen notifications atm.
Some dude is probably reading this right now and kanging it.
Sent from my SAMSUNG-SGH-T769 using Tapatalk

Somcom3X said:
Only ROM with both active display and lock screen notifications atm.
Some dude is probably reading this right now and kanging it.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Well we read it here first! Also the new boot animation is great, and boot time is phenomenal. Boot only takes seconds and I have not had that with ONE single ROM yet. Boots have normally been about a minute or so with other ROMs.
I'm going to try some things I haven't tried in a bit like ART although previously my experience with it hasn't been good. But again, a lot of time has passed since the last time I tried it.
Edit: Well never mind, ART couldn't get past the first 10 apps. That is pretty much what I thought would happen so no big deal. It's almost at the point ART might as well be removed altogether from KK ROMs but that is only my take, so in other words that isn't happening.

ArtfulDodger said:
Well we read it here first! Also the new boot animation is great, and boot time is phenomenal. Boot only takes seconds and I have not had that with ONE single ROM yet. Boots have normally been about a minute or so with other ROMs.
I'm going to try some things I haven't tried in a bit like ART although previously my experience with it hasn't been good. But again, a lot of time has passed since the last time I tried it.
Edit: Well never mind, ART couldn't get past the first 10 apps. That is pretty much what I thought would happen so no big deal. It's almost at the point ART might as well be removed altogether from KK ROMs but that is only my take, so in other words that isn't happening.
Click to expand...
Click to collapse
Art works. Try doing it without gaaps. Some gaaps don't have art support and that's why it gets stuck.
Sent from my SAMSUNG-SGH-T769 using Tapatalk

Somcom3X said:
Art works. Try doing it without gaaps. Some gaaps don't have art support and that's why it gets stuck.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Well I am using PA mini Gapps from 1/23, aren't those releases all ART compatible by now? Or is it better to run ART and then install them?

ArtfulDodger said:
Well I am using PA mini Gapps from 1/23, aren't those releases all ART compatible by now? Or is it better to run ART and then install them?
Click to expand...
Click to collapse
Dunno about pa, those gaaps are super buggy.
Use banks gapps
Sent from my SAMSUNG-SGH-T769 using Tapatalk

Somcom3X said:
Dunno about pa, those gaaps are super buggy.
Use banks gapps
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
OK I have those too, will do.
Edit: Your suggestion was spot on, ART worked this time. Thank you.

running it but haven't started really messing with it

[ROM][AOSP][Nightly/Release] CarbonRom KitKat [toroplus]

XDA:DevDB Information
[ROM][AOSP][Nightly/Release] CarbonRom KitKat [toroplus], ROM for the Samsung Galaxy Nexus
Contributors
CarbonDev, winner00
ROM OS Version: 4.4.x KitKat
Based On: AOSP
Version Information
Status: Beta
Created 2014-02-04
Last Updated 2014-06-07

Reserved

Reserved

Already loving Kit Kat! Thanks Carbon!

Man, this ROM is SOLID! It's great to be back home. I hope Carbon gets to relive its glory days, as it did in 4.3. Great job team!
Sent from my Galaxy Nexus using Tapatalk

Nice!
Sent from my Galaxy Nexus using Tapatalk

Can someone provide a direct link to rom download. Left sidebar device tree doesn't show up in phone or laptop browsers and even when I Google found my way to toroplus download page there's nothing linked after select a release type. Thanks

winnici said:
Can someone provide a direct link to rom download. Left sidebar device tree doesn't show up in phone or laptop browsers and even when I Google found my way to toroplus download page there's nothing linked after select a release type. Thanks
Click to expand...
Click to collapse
Use Google Chrome.
Sent from my Galaxy Nexus using Tapatalk

cmoG530 said:
Use Google Chrome.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I did. Mobile and desktop view and then on a Mac
If it works for you, please copy paste the dl link here or pm so I can try it out. Thanks
Update: download page working now

Please ignore

Can anyone let me know how data is please. A lot of devs have perfected the icons showing but data is sketchy. I like the features that are listed here and I would love to make this my everyday driver. I have been a CM fan for ever but I don't like the change in policy. Build and send out then hope for the best. This ROM seems like the one to replace CM. Thank you.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

Please ignore

tommy1121 said:
Can anyone let me know how data is please. A lot of devs have perfected the icons showing but data is sketchy. I like the features that are listed here and I would love to make this my everyday driver. I have been a CM fan for ever but I don't like the change in policy. Build and send out then hope for the best. This ROM seems like the one to replace CM. Thank you.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
data for me has been nothing short of a miracle! It has been switching seamlessly between 3G and LTE with no issues what-so-ever. I used to hate having to always reboot the phone just to get LTE in an area I know has LTE. I am also on the newest radio the GJ04 and have been for quite some time.
---------- Post added at 04:18 PM ---------- Previous post was at 04:16 PM ----------
The only issue I have so far (and its not a deal breaker by any means) is screen rotation...when the screen rotates, it sort of gets fuzzy, like a bad picture, but then quickly fixes itself. Running Carbon KitKat on my SGS4 as well and it does not do that, so I'm thinking its something with the Toroplus??

dirty flashed the most recent nightly and running well. digging the pie controls. any way that the Carbon Updates in about phone could work to update to the latest nightly as there are no KK milestones?

Very impressed with this Rom !
downloaded and flashed yesterday, very nice and stable. I like that the dialer has the Google local business search function built-in, I remember earlier cm builds didn't have it...
Haven't noticed any hiccups yet!:good:

Anyone flash a custom kernel with this Rom? any kernel suggestions?

Alternative Kernel
flashed the tinykernel-5.5-ASRAM.zip yesterday and everything seems to be running smooth after a day of use. This kernel is giving me 733mb of RAM to work with, so you gain around 30mb over the included rom kernel. I've tested WIFI, GPS, camera, etc., everything seems to function as it should. I've also underclocked to 230MHz and kept the max set at 1200, although you can go over 1500MHz if your phone can handle it...mine usually freezes instantly around 1500. Currently I'm still on build from 2-13, but will be updating soon.
This Rom seems to be very stable and one of the best KitKat Roms I've tried ! I've also reduced animations setting, along w/ other available related settings down to .25 within developer options. Under this set up my phone is pretty snappy!
Data switching (3g/4g, Wifi) has been flawless so far!

Although the tiny kernel I mention above works on this Rom, I was experiencing pretty often freeze ups requiring battery pulls, so running the included kernel since updating the rom and haven't had to battery pull yet... so for now will stick w/ the included cyanogenmod kernel.
Overall Great Rom !

Do any of the KK builds have LTE working?

jcruz767 said:
Do any of the KK builds have LTE working?
Click to expand...
Click to collapse
Yes mine is working.

Develop Bugs

welcome