Related
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
Hello everyone...I'm planning on trying to develop a gingerbread kernel for AOSP because we don't really have support anymore and everyone has moved onto developing for ICS (not that this is a bad thing). I figure in my spare time I might as well try to learn and develop for our phone. Let me start by saying I was never really into phones/smartphones/rooting, or software development, but I've always been fascinated by Linux in general. I've played around using a number of Linux distros, but I've never really done anything intensive with them (modified their kernels, etc.) but I am vaguely familiar with terminal usage.
Anyways that was just my introduction. I've been running an ICS kernel on my AOSP GB system (specs/stuff in my signature) and while most advised against it, I find it to run pretty well. I'm not sure why it seems to run so well on my phone, but it's basically solved most of my problems (or at least it appears to have done that), but I know the kernel isn't "optimized" for my phone. Some major things people have said are that the ramdisking operations/system is totally different when comparing ICS and GB. This kernel that I'm using is running pretty well, even knowing this fact. What I was wondering is if I could basically get the ICS kernel, then "merge it" with a GB kernel's parameters that pertain to the ramdisk/other major options of GB. That would probably make it better. Also, people stated that multitouch issues for the DINC2 occured on Aeroevan's 0.8 kernel, but not on the 0.7 kernel. This was the changelog stated by aeroevan:
v0.8: Upstream CyanogenMod changes + small touchscreen driver update from HTC. Only tested on my CM7.2 Kang build.
Click to expand...
Click to collapse
So maybe this "small touchscreen driver update" is the thing that caused it, but I'm assuming many other kernels applied this update too? Maybe there is a way to roll back to whatever was in 0.7 in this sense to get rid of the multitouch bug that plagues some people.
I have a pretty powerful laptop, so development shouldn't be too bad. I plan on running Ubuntu 11.10 (or whatever people find suitable these days) in a Virtual Machine and I plan on compiling stuff from there. I am not claiming I know everything or that these things are correct....I am simply just throwing out some brainstorming to get some ideas out there. I know GB is "old", but I (and some others as well) enjoy it's stability and that it generally functions perfectly. Maybe this thread will get a look from popular devs, or maybe it'll get a look from people who just know this stuff. Thanks for reading, and sorry for the length of the post.
Looking forward to your progress on this.
Sent from my ADR6350 using xda premium
It would be nice to have another kernal for AOSP other than aero.
Your help in developing AOSP kernels would be fantastic.
Thanks given. Because I am hard of hearing I cannot use any of the kernels (even Evan's) and have to stick to Sense
Cyanogenmod 9 is great, no doubt. But as far as I've seen, nobody has been able to get Ubuntu up and running on it. I'm assuming that the kernel associated doesn't have loop support.
If cm9 were to have this done in a pain free way, that would make it quite the ROM. So, if anyone has figured this out, I'd love to hear from you. I haven't been able to and I believe it's because of loop support. I've been learning to develop kernels and therefore am trying to create one that will work with both cm9 as well as allow the installation of Ubuntu or other Linux systems. Since I'm just getting into creating ROMs and kernels, I'm far from this. But if anyone has any ideas, let me know. And again, if you have done this on cm9 on an E4GT, I'd love to hear how.
Cheers.
Sent from my SPH-D710 using XDA
http://forum.xda-developers.com/showthread.php?t=1562138
Okay everybody, I want to start a WIP on this as it seems that we can get somewhere. The last dev seems to have dropped the project so I picked it up. :good:
***NOTE*** This is meant for development/testing purposes ONLY. It is in NO WAY for the faint of heart and you must follow ALL instructions or it will not boot! You have been warned!
As of 5/7/2013, the following things are working:
Camera (flash works, it takes pictures)
Sound (the only reason I know this works is because the shutter noise goes off in the camera app, there is no other way to test this right now)
The test apps (browser, notepad, gallery, camera, browser, phone, calculator, calendar, clock)
Power button (phone goes to sleep and wakes, hold the power button down to shut off the phone - the shutdown takes a second because it shuts down just like a linux kernel would - plug it in the charger to test this, it will vibrate once it is off)
Not working - just about everything else. Most items are still placeholders and there is a stability issue where the apps all close themselves after a few seconds which I am trying to figure out. There is no data or cellular connectivity of any kind. This may be fixable, however, since I was able to get the camera working by pulling the prebuilts from a different CM version. I'll keep experimenting with this. If you put the device to sleep, it does not wake up to the same brightness (it is dimmed) and you can not adjust the brightness right now (working on this as well, its a permissions issue in the kernel source but I haven't been able to narrow it down yet).
It is VERY finicky about how it is installed. I won't give any support for anything but TWRP 2.5.0.0
To install:
-Download the kernel zip and the latest daily from Ubuntu (I will post links later)
-Backup your current ROM in its entirety using TWRP - check every item on the list or you may have to go to a fresh install of your version you were running previously.
-In TWRP (once again, make sure its 2.5.0.0 because these are 2.5.0.0 specific instructions), factory reset but do an advanced reset, check dalvik, data, system, and cache. ***MAKE SURE THAT YOU DON'T FORMAT YOUR MICROSD***
-Install the kernel zip and do not wipe cache or dalvik
-Install the Ubuntu preinstalled image, once again make sure you do not wipe the cache or the dalvik.
-Do not do anything else, no fixing permissions or anything, just reboot
-Wait about 2 minutes for the lock screen to come up and then you can use it
I will keep working on the kernel - the other functions will not work until Ubuntu implements them.
This is my first time working with actual development - if anyone wants to give me a tutorial to get my project up on GitHub so everyone can work on it, I would be more than happy to do so.
Here are the links:
Kernel built 5/7/2013: http://d-h.st/185
Latest Ubuntu Touch base: http://cdimage.ubuntu.com/ubuntu-to...current/raring-preinstalled-phablet-armhf.zip
Since the source has been moved to Raring Ringtail, there should not be a need to update that link. Please note that the 5/7/2013 build is the one that I tested and be sure to let me know if it gets broken in the future.
Enjoy everyone and once again, if you want to contribute, I'm more than happy to set up a GitHub, I just need some basic help getting it started.
Thanks this looks very hopeful.
Sent from my SAMSUNG-SGH-I747 using xda premium
TheLastSidekick said:
Thanks this looks very hopeful.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I am hoping that development will take off. Ubuntu is set to start releasing alpha apps on the 16th so figuring out how to get a working kernel for it was top priority for me and nobody else seemed interested in doing it.
I've literally spent hours, lots of expletives, and other unpleasant things trying to get this built. I think I should have started working with CM BEFORE taking on UT but it paid off
Thank you sir,
Dling now
Sent from my Galaxy Nexus using xda premium
Flashed and everything went smoothly. Very pre-alpha, but alot of.stuff is working comsiderinf whaf it is. I wluld like to test this for any developer that wants to build it
Sent from my SGH-T999 using xda premium
ktetreault14 said:
Flashed and everything went smoothly. Very pre-alpha, but alot of.stuff is working comsiderinf whaf it is. I wluld like to test this for any developer that wants to build it
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I'm glad that you enjoyed what currently works.
I have done some work on the kernel but I need some help figuring out the WiFi. The drivers are proprietary Broadcom drivers so I need to see if anyone has gotten it to work on their Touch builds.
The rest of it is mainly just waiting on Ubuntu to stabilize - this isn't even considered an alpha at this point. Alpha starts May 16th.
Either way, I've managed to compile a kernel using cm-10.1-M3 (4.2.2) sources in preparation for UT's inevitable source upgrade from M1 (4.2.1) to M3. I'd post it but it doesn't have any different features from the M1 kernel up above.
I'll be updating it as Ubuntu releases new features or if I can get other things working on the build.
EtherealRemnant said:
I'm glad that you enjoyed what currently works.
I have done some work on the kernel but I need some help figuring out the WiFi. The drivers are proprietary Broadcom drivers so I need to see if anyone has gotten it to work on their Touch builds.
The rest of it is mainly just waiting on Ubuntu to stabilize - this isn't even considered an alpha at this point. Alpha starts May 16th.
Either way, I've managed to compile a kernel using cm-10.1-M3 (4.2.2) sources in preparation for UT's inevitable source upgrade from M1 (4.2.1) to M3. I'd post it but it doesn't have any different features from the M1 kernel up above.
I'll be updating it as Ubuntu releases new features or if I can get other things working on the build.
Click to expand...
Click to collapse
So, Ubuntu is using android stuff for these builds?
Sent from my SGH-T999 using xda premium
eggydrums said:
So, Ubuntu is using android stuff for these builds?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
The kernel is a CM base. Its a massive fork of CM that's kind of a royal pain in the ass to work with since its not been synced since they forked it and they've made major modifications to the code (all traces of Dalvik are gone, for example). You also have to make modifications to the kernel build so it functions more like a linux system, there are process patches that have to be applied to the kernel, etc.
Thanks for keeping this going. Not much is going on until Ubuntu pushes things out later this month. Everything will pretty much FC until we have the proper scripts.
Cannot wair for Ubuntu to be fully released, I would like to use this as a daily driver
Sent from my SGH-T999 using xda premium
charlieb620 said:
Thanks for keeping this going. Not much is going on until Ubuntu pushes things out later this month. Everything will pretty much FC until we have the proper scripts.
Click to expand...
Click to collapse
So you had the same issue with your build?
Admittedly, I never tried it because I was determined to build my own and yours was March dated. I had posted in the thread trying to get some assistance from you actually - but yeah, its certainly not usable right now.
Was your kernel a forced M1 or did you somehow find a way to get the nightly source to build? I've built M1 and M2 so far. Since I had the same results with both and UT is based off of M1, I haven't messed with M3.
I wish I could figure out the WiFi and the force close of apps - did you patch the kernel successfully? I added the proc patch as best I could (raw data paste but it didn't throw warnings so it must have worked - I'm not a programmer) and it didn't fix anything, apps still just close after a few seconds.
I was surprised that I got the camera and sound though just by switching CM versions. Maybe the same thing can happen with the WiFi? I noticed that it is being built as a module but I don't know enough about the Android kernel to reconfigure it as a built-in (I don't know if the Ubuntu kernel has the code for detecting all the hardware just yet, I'm guessing it doesn't). I've done lots of Linux kernel tweaking (I have toyed with it since Red Hat 1.0 and its my daily driver in the form of Ubuntu 13.04 right now - usually I use Mint but I wanted to eliminate as many variables as possible) but I don't know much about Android.
Admittedly, I started with UT before I had ever worked with CM even so I've learned a LOT. lol
Thanks for this.
So does this kernel work with the latest UT Developer Preview release? If not I would be willing to help you getting it back up to date even though I'm still a newbie! Thanks in advance for the response.
Sent from my SGH-T999 using xda app-developers app
biohazard said:
So does this kernel work with the latest UT Developer Preview release? If not I would be willing to help you getting it back up to date even though I'm still a newbie! Thanks in advance for the response.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
It should work fine with the latest DP. I haven't bothered to update it because the kernel source hasn't really been worked on. They're still focusing all of their work on Google devices.
There isn't a stable kernel for any S3 variant right now.
Sent from my SGH-T999 using Tapatalk 4 Beta
Mmmm, I can't seem to get it to boot at all.
Sent from my SGH-T999 using xda premium
biohazard said:
Mmmm, I can't seem to get it to boot at all.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Make sure you followed the directions exactly, any deviation will cause it not to boot. Also there is no boot screen. What you can do is plug it in to the charger before you boot it - if it fails to boot the phone will power off and take you to the charging screen. If it doesn't, give it a few minutes to load up especially the first boot.
If it fails again, let me know and I'll see about building a new kernel some time this week. As far as I am aware there is no newer kernel source on the Ubuntu side but I can try to build an RC5 based kernel (this is an M1 kernel).
Its worked for everyone else but I can't test it right now because I'm getting ready to go out and need my phone.
Sent from my SGH-T999 using Tapatalk 4 Beta
Alright I see, thanks for all the help. Could you possibly point me to the correct base download, I have tried multiple phablet bases, and I just can't get it to boot for some reason. Thanks in advance for all the help.
Sent from my SGH-T999 using Tapatalk 4 Beta
The international GS3 has working wi-fi.....i know the hardware is completely different but do you think you might be able to look at how they got it working over there?
http://forum.xda-developers.com/showthread.php?t=2315397
Here's the commit that shows how he got wi-fi working: https://github.com/Androguide/andro...mmit/feac1d9af58c2947e0f3f6b6719553be5811ce6d try applying that to init.qcom.rc i would but my computer won't build anything i'm trying to fix it...
Also for github you really just need to post your manifests file and whatever you've modified from the source code. i'm not really a pro with github but i've worked with it quite a lot. They have an awesome tutorial on their website i'd recommend checking out.
Okay Ubuntu made upstream code changes that broke the kernel. Give me a few days and I'll have an update.
Plays2 - that patch *should* work for us as well since we use Broadcom's WiFi just like the international version does (odd that they didn't use Qualcomm's since it came with the SoC but it works in our favor in this instance). Still takes a lot of configuration to get it running though.
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