Related
Hey everyone, well, ironically, I'm asking for help . I've wanted to create a AOSP ROM, but I can't find a guide on getting AOSP to the Sprint Hero. Is there a step by step guide for compiling it, with all the config files needed? Thanks, I really would appreciate it, and I'm sure you'll appreciate the future ROM's of mine too .
EXTREMELY tempted to post a lmgtfy
justinisyoung said:
EXTREMELY tempted to post a lmgtfy
Click to expand...
Click to collapse
Uhh... I will literally scream if it's on google. I went through, so many pages googling it. I have compiled android before, yes. But not for the hero.
This is what i have been trying to make work.
http://android.modaco.com/index.php?s=&showtopic=301857&view=findpost&p=1179830
Its only a peice of the puzzle. I havent been able to do much with it, I wasnt able to find where I needed to shove libcamera for our hw to get past an error.
PM Darch....
kkruse said:
This is what i have been trying to make work.
http://android.modaco.com/index.php?s=&showtopic=301857&view=findpost&p=1179830
Its only a peice of the puzzle. I havent been able to do much with it, I wasnt able to find where I needed to shove libcamera for our hw to get past an error.
Click to expand...
Click to collapse
what make errors have you been receiving. sometimes when you compile using that vendor tree some of the libs don't get pushed into the target.
I posted a "vendor overlay" ZIP for our CDMA hero elsewhere on this site (it's the LoX GSM hero overlay with edits for heroc plus some extra libs, etc, for 2.1), I was initially hoping for some feedback on it from some of the other devs. I was having the same issues darch mentions where some of the files don't copy over during the build so you just have to copy them into the target as the errors come up. Search my userID plus "vendor" and "voodoo" and it should come up.
5tr4t4 said:
I posted a "vendor overlay" ZIP for our CDMA hero elsewhere on this site (it's the LoX GSM hero overlay with edits for heroc plus some extra libs, etc, for 2.1), I was initially hoping for some feedback on it from some of the other devs. I was having the same issues darch mentions where some of the files don't copy over during the build so you just have to copy them into the target as the errors come up. Search my userID plus "vendor" and "voodoo" and it should come up.
Click to expand...
Click to collapse
you could do that to fix it... or we can fix the unzip scripts, because that is the root of all the problems in which the camera libs aren't making it to the target.
Btw, i'm gunna check out your vendor overlay. sounds like it'll help people compile cyanogenmod a bit more eaily.
darchstar said:
you could do that to fix it... or we can fix the unzip scripts, because that is the root of all the problems in which the camera libs aren't making it to the target.
Btw, i'm gunna check out your vendor overlay. sounds like it'll help people compile cyanogenmod a bit more eaily.
Click to expand...
Click to collapse
I never investigated it very deeply. If you know it's the unzip step, that would be great to have it fixed. BTW, there two extract-files.sh in my overlay, one that pulls needed files from the device, and another that pulls them from a ROM (came in handy at one point). I'm still not clear about how much variability there is with libs, etc, from version to version, you would know better.
Finally, the kernel zImage included is just Toast's .29 that I built from scratch the day I posted the overlay. There's probably a newer version now...and I assume you can just package with your own boot.img anyway.
darchstar said:
what make errors have you been receiving. sometimes when you compile using that vendor tree some of the libs don't get pushed into the target.
Click to expand...
Click to collapse
sorry to leave ya hanging but I just checked in... let me recompile it again and see.... Ill probably have the results back in the AM. Too tired now
This is a continuation of the "Compiling CM6 for Eris" thread - http://forum.xda-developers.com/showthread.php?t=856215. But since Team ADX has really come together on this, we are releasing it in it's new form.
Thanks to workshed for working to get the Eris on the Official CM list and merged into the main repo. And also, thanks to workshed for most of the v6 --> v7 changes to EasyDev!
This script will grab CM7 source and compile a CM7 ROM for you using the official vendor tree that is built-in to the CM source. You have the option of including Google Apps or not.
Uses:
CM source - https://github.com/CyanogenMod/android.git
Conap's CFS kernel that's built-in to CM source - https://github.com/Conap30/htc_kernel_desirec_cfs
Requirements
-------------
1) 64- bit Linux -tested on Debian, Ubuntu 10.04, Linux Mint (if you have a different flavor of linux and easydev worked for you, please let us know so we can update this list)
2) An existing Eris ROM that the script will pull the proprietary files from.
INSTRUCTIONS
1) Download the script
2) 'chmod a+x easydev-v9.sh'
3) copy it to the directory of your choice or leave it where it is
4) copy an existing ROM to the same directory (tested with GSB, but most should work)
5) run it ('sudo ./easydev-v9.sh')
Possilbe future features:
Done.
Changelog
v1 - initial release
v2 - added squisher, made 'make clean' optional, added installation of dependencies, cleaned up output
v3 - uses existing ROM to pull proprietary files, renamed to 'easydev' for case sensitive linux admins
v4 - fixed file missing from list in unzip-files.sh in vendor tree, fixed move/rename of existing ROM, change 'make clean' option to default to no instead of yes
v5 - added 'apt-get update' to refresh repo list (should install dependencies now), swapped order of extract-files and unzip-files to fix 'chmod akmd' issue, tried not to break anything else
v6 - moved questions to beginning of script, added check to only init repo the first time, added check for existing ROM, modded vendor tree to fix compile issues
v7 - removed CM6 stuff, removed kernel compilation code, removed vendor tree code, changed from CM6 to CM7, fixed path bug, added 32-bit libs to dep list
v8 - added ALL official CM devices (mostly untested), minor update to dependency installer code (4-21-11)
v9 - added an extra check for correct Java version, fixed .zip rename issue
Download links:
v7+ --> https://github.com/gnarlyc/EasyDev-Eris
NOTE: If you have issues with google setup or not being able to pass andy the android at the beginning of setup, please delete Provisions.apk for system/app you shouldn't have a problem, but just incase, this will remedy it. -workshed
I'm all over this sh*t
Oh damn, I'm excited for this. good thing I use ubuntu!
Sent from my ERIS using XDA App
this should be fun once i get my new laptop.
Nice! I will be trying this later.
This is awesome! Thanks alot. What does the 'make clean' option do?
Skrip037 said:
This is awesome! Thanks alot. What does the 'make clean' option do?
Click to expand...
Click to collapse
The make clean removes everything that has been compile so far leaving only the original source.
Skrip037 said:
This is awesome! Thanks alot. What does the 'make clean' option do?
Click to expand...
Click to collapse
It removes any previously built ROMs, etc. It's not needed every time, so I've made it optional in the next version. The problem was that sometimes the script would be broken in some way and wouldn't build a ROM. But, there's so much text displayed to the screen, it's not always easy to notice. So, I was actually flashing the same test ROM over and over instead of getting a new build...
Great work guys. Going to try it out on Arch Linux and if anyone's interested I'll give details about how to get it working there (or just modify the script to detect Arch as opposed to Ubuntu and work accordingly.
<gripe>One complaint: commands (including scripts) should *always* start with a lowercase letter </gripe>
good work gnarlyc & conap.
this sounds great and i will be trying this when i get home. I have just one question. Why would i want to run this instead of conap's rom? Both being pure CM. I see alot of the other cm6 roms have stuff themed, but conap's rom doesn't. I'm assuming this is complete pure cm without little tweaks done by devs of the respective roms. Thanks in advance.
ngc604 said:
this sounds great and i will be trying this when i get home. I have just one question. Why would i want to run this instead of conap's rom? Both being pure CM. I see alot of the other cm6 roms have stuff themed, but conap's rom doesn't. I'm assuming this is complete pure cm without little tweaks done by devs of the respective roms. Thanks in advance.
Click to expand...
Click to collapse
Some people just like to "roll their own", more or less. If you like having someone else make improvements and fix issues for you, then you'll probably want to stick with another ROM.
I would love to make my own fixes and tweaks but i dont have the knowledge nor the time to gain said knowledge. guess i will just stick with the devs roms. thanks
Very very exciting. I am installing Ubunto 10.4 now. So does EasyDev-v2 pull from the CM6 nightlies or the stable version and can we change where it pulls from for the CM6 source. This is great.
Will have to check this out later. Always wanted to understand the compile process, always to busy with other software projects. Thanks for building this resource for the rest of us.
morrisdan said:
Very very exciting. I am installing Ubunto 10.4 now. So does EasyDev-v2 pull from the CM6 nightlies or the stable version and can we change where it pulls from for the CM6 source. This is great.
Click to expand...
Click to collapse
Hmmm. Someone correct me if I'm wrong, but I'm pretty sure that this is currently grabbing 'stable'.
Code:
repo init -u git://github.com/CyanogenMod/android.git -b froyo
I'm thinking that to get the nightly, we'll have to change that to:
Code:
repo init -u git://github.com/CyanogenMod/android.git -b master
I'll try it as soon as I can. You got me to thinking that we could add that as an option, if I understand this correctly.
Nightly vs Stable
Yes, you answered my question regarding nightly and stable. I am having fun so far. I got all the necessary packages installed. That was pretty easy using the Ubunto package manager deal. So where do I find the proprietary.zip now? I am almost there to cook this sucker up.
morrisdan said:
Yes, you answered my question regarding nightly and stable. I am having fun so far. I got all the necessary packages installed. That was pretty easy using the Ubunto package manager deal. So where do I find the proprietary.zip now? I am almost there to cook this sucker up.
Click to expand...
Click to collapse
I was apparently wrong about the "-b master" switch, but I think I mostly got it right...
Right now, you'll have to grab the files listed in the OP and zip them up into a file called 'proprietary.zip'. Then place it in the same directory that you run the script from.
I'm working on a way that you can just place an existing ROM there, and it will extract the proprietary files for you. That should be in v3.
Proprietary.zip Files
Can I download CELB Froyo 3.8 and uncompress it and do searches for those files and pull them out and zip them up?
morrisdan said:
Can I download CELB Froyo 3.8 and uncompress it and do searches for those files and pull them out and zip them up?
Click to expand...
Click to collapse
Yes, that should work fine. Here's a list with the paths -
https://github.com/Conap30/android_device_htc_desirec/blob/master/extract-files.sh
Hey all, I guess if your here its because you want to build your own kernel from the HTC GB Kernel source for the HTC Droid Incredible. So that's what we're gonna do.
First things first. I have to send out a huge thanks to a few guys that helped me out along the way.
jdkoreclipse - Your the best man. Thanks for getting me compiling.
wdfowty - Always good on the code.
ohheyitslou - Standing by while a blabbered on with stupid questions.
conap - The original god of kernels.
Koush - Thanks for the anykernel updater.
Note: The method I descripe below is what worked for me to get this thing to build and boot. Additional packages may be required. Ie; JDK, Android SDK, Python, git and the 32bit libs (if your on a x64 machine). I do assume that you have them and have your computer set up for development. I also assume that you are fully aware that any damage caused to your devices from YOU following this guide is held at your own responsibility.
Click to expand...
Click to collapse
First things first, lets make sure you are on a linux distro. At the time of this writing, I was using Ubuntu 11.10 x64. Note: 64x is highly suggested. My computer is a dual core amd machine with 4GB of ram. I have a 250GB HHD.
Next lets download some things that we will need for your kernel.
The kernel source of course:
DROID Incredible by HTC (Verizon) – GB MR - 2.6.35 kernel source code
This is the correct size and MD5:
88.8 MB (93,175,808 bytes) 67c01623ff73415a99e5f8cd1d8ef11a
You will also want the CM Toolchain. This is what compiles your kernel.
Open a terminal window and type:
Code:
git clone git://github.com/CyanogenMod/android_prebuilt.git prebuilt
And finally, the anykernel_updater.zip for packaging and flashing your kernel: anykernel_updater.zip
Have these things downloaded? Great! Lets continue.
Next we need to create a new build directory to build your kernel in. For this tut, we will make this in your Home dir.
Open a terminal window and type:
Code:
cd ~
mkdir android
cd android
mkdir kernel
Easy huh?
Next grab your HTC Droid Incredible kernel source archive and just open it with archive manager. We don't need to do any untarring here.
You'll want to drag that 395.2MB folder inside called 'incrediblec-2.6.35-gb-mr' to that kernel directory you created.
Next, grab the CM toolchain archive and open it the same way. Yup just drag that folder thats inside there out and put right in your 'android' folder.
So lets review real quick before we continue:
Inside your Home directory you now have a folder called: android
Inside that android folder you have two folders. One called: kernel and the other called: android_prebuilt or prebuilt.
Inside the kernel folder you have your kernel source folder: incrediblec-2.6.35-gb-mr
Is this correct? Good.
Now, lets open a new terminal window and move to your kernel source folder:
Code:
cd '/home/yourusername/android/kernel/incrediblec-2.6.35-gb-mr'
Now we will compile the source. Note: This is a basic kernel source compiling guide. Our focus is to simply compile the source. Nothing more.
In the terminal window type:
Code:
make incrediblec_defconfig
make -j4 ARCH=arm CROSS_COMPILE=/home/yourusername/android_prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
Note I used j4. This is because I am using a dual core box to develop on. I think now days most boxes are usually dual core or quad core?
Your kernel should now be compiling. This process could run average between 5min-1hr. My laptop (which is beast) did it in about 2 minutes. But then again I'm running a full install of 'buntu x64 with everything updated and ready to rock.
Anyways after the compiler finishes building it will tell you where to locate your kernel and wifi driver. Yes the wifi driver is included!
The kernel should be at: /home/yourusername/android/kernel/incrediblec-2.6.35-gb-mr/arch/arm/boot/ for those that don't know it is called 'zimage'. Just drag that out to your Desktop.
Now go grab your wifi driver. Its located at: /home/yourusername/android/kernel/incrediblec-2.6.35-gb-mr/drivers/net/wireless/bcm4329_204/ It will be called bcm4329.ko. Again drag that out to your desktop.
Now you can close everything thats open. Grab that anykernel_flasher.zip you downloaded earlier and open it up with archive manager. Don't extract it, just open it.
Navigate to system/lib/module/ and drag your bcm4329.ko right into it.
Next back up all the way to the root of the anykernel_flasher.zip and then open the kernel folder. Yup just drag and drop your zimage right in there. Close the archive manager window.
CONGRATS!!! You just compiled your first kernel from source!
Now you can rename the zip to whatever is easiest for you to remember. Common practice says the date and time should be in the name. Like mine from today is called: 2.6.35.13-stang-kernel-1830-110111.zip.
Now go test your kernel. Just put it on your sd card and flash it through recovery. The anykernel_updater.zip will handle the wiping for you so you shouldn't have to worry about wiping boot, dalvik-cache or cache. You can still wipe those things if you would like.
Once the flash is complete, just hit reboot device and wait for your phone to boot up. It took mine about 5 minutes to fully boot up.
Well, I hope yall enjoyed this guide. I wanted to keep it simple. I am not a kernel god or anything but let me tell ya, I went through a lot to try to learn how to do this. So if you run into any trouble, I'll try to help you out if I can.
Have fun guys!
now what..........
Nice. Good job.
Sent from my ADR6300 using Tapatalk
Way to help us out with a good easy to follow guide stang thanks
sent from my sexy Slcd Droid Incredible. not dinc or D-inc that just sounds stupid.
tiny4579 said:
Nice. Good job.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
Thanks Tiny. Now we need to get some more customs going
evilstewie23 said:
Way to help us out with a good easy to follow guide stang thanks
sent from my sexy Slcd Droid Incredible. not dinc or D-inc that just sounds stupid.
Click to expand...
Click to collapse
Thanks stew, You know how much this means to me.
Beast Mode! Very nice guide sir, I'm sure some of the more serious members will get hella use out of this. I have been (sort of) following your progress on twitter, so glad to see that you finally got it figured out. Nice work.
00McD00 said:
Beast Mode! Very nice guide sir, I'm sure some of the more serious members will get hella use out of this. I have been (sort of) following your progress on twitter, so glad to see that you finally got it figured out. Nice work.
Click to expand...
Click to collapse
Thanks Mc. I'm just happy to have learned this much atleast. I'm even more happy to share what I've learned. That's the important part.
wildstang83 said:
Thanks Mc. I'm just happy to have learned this much atleast. I'm even more happy to share what I've learned. That's the important part.
Click to expand...
Click to collapse
Definitely, I have always felt the same way. Sharing is caring lol
That's the stuff, Wildstang. Glad you're back.
Sent from my Prime_XL Incredible via Tapatalk
very nice. Im going to give a this a go and see what i can some up with. does this require a sense rom or a aosp rom?
dirtsky said:
very nice. Im going to give a this a go and see what i can some up with. does this require a sense rom or a aosp rom?
Click to expand...
Click to collapse
This compiles a sense kernel.
tcberg2010 said:
This compiles a sense kernel.
Click to expand...
Click to collapse
Well Sh*t. Oh well ill still give it a go I guess.
tcberg2010 said:
This compiles a sense kernel.
Click to expand...
Click to collapse
these instructions will work fine for aosp. You just have to download that kernel source instead. The compile process is the same.
Sent from my ADR6300 using Tapatalk
Ill have to get the kernel source and see what I can do.
Sent from my Incredibly awesome Droid Incredible.
Thanks for adding this howto, wildstang -
I really appreciate it. I just for the first time in a year+ went from my old rooted inc to this home-brewed self-compiled (I added cifs & tun built into the kernel) and installed it. I'd just tried the insensitive ROM as well and this helped things quite a lot due to cifs & tun. I also set the clock to a not-very-aggressive 1075000 which works fine on my inc.
Much appreciated and good guide.
edit: I forgot to mention that in general and here as well, you can 'brand' your kernel so you're sure you've really installed it and it is running on your phone by checking the firmware revs in about-phone. To do that, just edit Makefile and I think it is called Extra (under Version) which is as it is set to .13, so I set that in my case to .13-cifs-tun-cust, and it shows on my phone. It is useful in case you forget to zip the file up or something.
Hashi
Hi guys i'm getting an atrix to help out and play with. I don't have att instead i have Verizon so this is just for fun. I have a Galaxy Nexus and the forums are full of info to building roms and kernels so i figured i would start my own cm10 rom for myself and if at some point down the road others. I found this link http://wiki.jeago.com/index.php?title=Build_for_olympus and desided i would give it a go and at least have a base. However i ran into a problem, When i get down to the "lunch" command i do not have "cm_olympus-userdebug" listed? can anyone steer me on the right path or is this an old Link that has since been pulled? Thanks guys
Doesn't matter if it's not listed. As long as you have synced the right repo, "lunch cm_olympus-userdebug" still works as expected.
I think it pulls the list from the official CM10 repo (which does not include olympus), but the command will work with the files you've synced (which does include olympus).
quetzalcoatl2435 said:
Doesn't matter if it's not listed. As long as you have synced the right repo, "lunch cm_olympus-userdebug" still works as expected.
I think it pulls the list from the official CM10 repo (which does not include olympus), but the command will work with the files you've synced (which does include olympus).
Click to expand...
Click to collapse
Hi. Correct me if I'm wrong, but I guess that the official CM repositories doesn't have branches later than CM7 for the olympus. You have to get them somewhere else for CM9 and later.
Yes, that's what I said. The official CM10 repo does not include olympus.
Get them here: https://github.com/epinter/android/tree/jb-olympus
kicker22004 said:
Hi guys i'm getting an atrix to help out and play with. I don't have att instead i have Verizon so this is just for fun. I have a Galaxy Nexus and the forums are full of info to building roms and kernels so i figured i would start my own cm10 rom for myself and if at some point down the road others. I found this link http://wiki.jeago.com/index.php?title=Build_for_olympus and desided i would give it a go and at least have a base. However i ran into a problem, When i get down to the "lunch" command i do not have "cm_olympus-userdebug" listed? can anyone steer me on the right path or is this an old Link that has since been pulled? Thanks guys
Click to expand...
Click to collapse
I used "generic_olympus-userdebug" for the lunch command and afterwards the "cm_olympus-userdebug" appears among the options.
---------- Post added at 08:38 PM ---------- Previous post was at 08:30 PM ----------
quetzalcoatl2435 said:
Yes, that's what I said. The official CM10 repo does not include olympus.
Get them here: https://github.com/epinter/android/tree/jb-olympus
Click to expand...
Click to collapse
Ooops, read too fast, my apologies...
I forked vendor, device and kernel repositories from CyanogenMod-Atrix github, but these are pre-alpha repos with known (and unknown) bugs. (BTW, though it compiles fine, the recovery won't install the resulting zip on my Atrix, still figuring out what's wrong)
ok now i'm getting way lost here. how do i go about adding this to my current files?
ok guys i just noticed that the link i was following had me pulling ICS not JB...wow i'm slow today.
Wiped everything and starting fresh. anyone have a guide to pull the needed build. Atrix4g18 sugested i needed https://github.com/epinter/android/branches and jb-olympus-new. I'm going to start over and this time pull repo init -u git://github.com/CyanogenMod/android.git -b jellybean instead of the ICS and then i should be at least closer to what i need.
kicker22004 said:
ok now i'm getting way lost here. how do i go about adding this to my current files?
ok guys i just noticed that the link i was following had me pulling ICS not JB...wow i'm slow today.
Wiped everything and starting fresh. anyone have a guide to pull the needed build. Atrix4g18 sugested i needed https://github.com/epinter/android/branches and jb-olympus-new. I'm going to start over and this time pull repo init -u git://github.com/CyanogenMod/android.git -b jellybean instead of the ICS and then i should be at least closer to what i need.
Click to expand...
Click to collapse
I'm not sure how to use the default.xml file in the link that quetzalcoatl2435 gave us, but in my case I created a local_manifest.xml file (from here) with the extra repos I needed and copied to .repo/local_manifest directory in the source tree root.
EDIT:
I think I got it, someone who really knows please confirm: instead of the deffault CM repo init, issue this: repo init -u git://github.com/epinter/android.git -b jb-olympus-new. Is that right?
OK for the time being i'm going to start rebuilding my repo again. i scratched everything so have to download the JB repo now. anyone with more info to using the Default.xml file or where it should be placed? Thanks guys
After looking at the Default.xml it seems he just added the Atrix to the list so i would assume i will copy paste and rerun repo sync? should i copy first then run repo sync or no?
All i have to say is thank you Verizon LTE with unlimited data and free tether LOL.
Don't use jb-olympus-new. That's for the new kernel and does not have the proprietary files included. You need to search for and add them manually.
Use this:
repo init -u git://github.com/epinter/android.git -b jb-olympus
repo sync
Assuming you've already installed all pre-requisites correctly, next do:
. build/envsetup.sh
lunch cm_olympus-userdebug
brunch olympus
Sent from my MB860 using xda app-developers app
kicker22004 said:
ok now i'm getting way lost here. how do i go about adding this to my current files?
ok guys i just noticed that the link i was following had me pulling ICS not JB...wow i'm slow today.
Wiped everything and starting fresh. anyone have a guide to pull the needed build. Atrix4g18 sugested i needed https://github.com/epinter/android/branches and jb-olympus-new. I'm going to start over and this time pull repo init -u git://github.com/CyanogenMod/android.git -b jellybean instead of the ICS and then i should be at least closer to what i need.
Click to expand...
Click to collapse
No need to pull CyanogenMod's github. It's included in epinter's github. No need to mess with the xml files either, just repo sync, lunch, and brunch.
kicker22004 said:
Hi guys i'm getting an atrix to help out and play with. I don't have att instead i have Verizon so this is just for fun. I have a Galaxy Nexus and the forums are full of info to building roms and kernels so i figured i would start my own cm10 rom for myself and if at some point down the road others. I found this link http://wiki.jeago.com/index.php?title=Build_for_olympus and desided i would give it a go and at least have a base. However i ran into a problem, When i get down to the "lunch" command i do not have "cm_olympus-userdebug" listed? can anyone steer me on the right path or is this an old Link that has since been pulled? Thanks guys
Click to expand...
Click to collapse
Just curious. Is this ROM going to be public?
quetzalcoatl2435 said:
No need to pull CyanogenMod's github. It's included in epinter's github. No need to mess with the xml files either, just repo sync, lunch, and brunch.
Click to expand...
Click to collapse
I think for the most compatible with the new kernel will need to add 2 more branches
github.com/CyanogenMod-Atrix/android_device_motorola_olympus.git
github.com/CyanogenMod-Atrix/android_vendor_motorola_olympus.git
Xerox98 said:
Just curious. Is this ROM going to be public?
Click to expand...
Click to collapse
How about you read the other threads before asking?
mapkel said:
I think for the most compatible with the new kernel will need to add 2 more branches
github.com/CyanogenMod-Atrix/android_device_motorola_olympus.git
github.com/CyanogenMod-Atrix/android_vendor_motorola_olympus.git
Click to expand...
Click to collapse
No need to add android_device_motorola_olympus.git to jb-olympus-new. It's already included by epinter. You only need to add the vendor files.
BTW, I was talking about the jb-olympus branch, not the jb-olympus-new branch.
The new branch is not for daily use (yet).
Thanks you guys. I had a github time out earlier so will be starting fresh here soon.
Sent from my Galaxy Nexus using xda app-developers app
And the countdown begins..... I have another 8gb of ram i removed thinking it was causing Build issues for my Gnex (turns out it was missing some blobs...oops) i'll be putting that back in before i start building. Going to start with a clone copy of this rom, Anyone know what happens with the new kernel and this? Yes i know it's alpha but i'm testing so that's what i need to focus on.
ok guys i went over this a few times and I found a few errors that i was able to fix by installing packages that were missing (13.04 64-bit btw). But i'm stuck on this one. anyone have any idea? this is after the Brunch olympus command. After more hunting on google seems i might need (sudo apt-get install libxml2-utils) so starting the Brunch again we'll see.
ravilov said:
How about you read the other threads before asking?
Click to expand...
Click to collapse
? I have pritty well read every post in the Atrix forum. I just wanted to know if this ROM would be made public when ready, so that there is another CM10 rom apart from Epinters.
this is from epinter's source. The first post says that i'm building this for fun and to help out if i can, and at some point down the road MAYBE be a public rom, my skills are limited and i don't feel at this stage that i'm rdy to release a ROM to the public, that's not saying i won't..just not soon. As for now i'm thinking i should be building this on 12.04 LTS because i keep running into Compiling errors... now i've got another one that's im trying to figure out.
Anyone have any idea's what i'm missing now lol.
Hi,
I synced the CM10.1 source last weekend. I mucked about with the kernel. I pointed it to Christopher83's custom toolchain. I built it. It works. I'm content.
However my plan was to revive 4.2.2 and actually ADD to it, otherwise you could just go and download the zip which the Andromadus team uploaded. Unfortunately I've discovered that I'm completely incompetent when it comes to firstly finding things to add, secondly finding the commit, and then thirdly trying to cherry pick and apply the commit so it works. I haven't really got to stage 3 yet.
So here's my suggestion: could someone please work with me or if syncing sources etc. is not possible, at least help me by being knowledgeable enough to know some good features, point me to the commits, and help me fix conflicts so that I can apply them successfully. Therefore I either want a team, the 4.2.2 revival team as it were, or someone or some people to help me if they can't directly interact with the sources. Don't worry if you can't build for whatever reason: if you can sync specific repos, e.g. settings, frameworks base, and modify them, and push them, so that I can build the ROM, that's fine. Anyone who helps at all will be deemed equally if not more important than myself, as I expect I'll ultimately just end up being the builder.
Thanks very much for your support.
I can help you with that. Tell me when you start your project and what errors did you get
Best Regards,
MarcoMarinho
RE: [DEV] CM10.1 builds | help needed adding features | "4.2.2 Revival Team"
_MarcoMarinho_ said:
I can help you with that. Tell me when you start your project and what errors did you get
Best Regards,
MarcoMarinho
Click to expand...
Click to collapse
Thanks firstly I thought a simple thing to do would be to add the recent app screen ram bar from SlimBean, but I can't find the commit anywhere in the SlimRoms github. Perhaps you know where it is or can find it for me, then I could cherrypick it and we could fix the conflicts together and we'd have our first unofficial CM10.1 ROM with additional features!
HTCDreamOn said:
Thanks firstly I thought a simple thing to do would be to add the recent app screen ram bar from SlimBean, but I can't find the commit anywhere in the SlimRoms github. Perhaps you know where it is or can find it for me, then I could cherrypick it and we could fix the conflicts together and we'd have our first unofficial CM10.1 ROM with additional features!
Click to expand...
Click to collapse
Sure
Here is the commit: https://github.com/SlimRoms/frameworks_base/commit/9c1c3c0955d51adc589ec6fbb667a0ae482de24e
You need this to: https://github.com/AOSB/android/commit/a512f16890af8c277c3d1a88c8bca36711b82328
RE: [DEV] CM10.1 builds | help needed adding features | "4.2.2 Revival Team"
_MarcoMarinho_ said:
Sure
Here is the commit: https://github.com/SlimRoms/frameworks_base/commit/9c1c3c0955d51adc589ec6fbb667a0ae482de24e
You need this to: https://github.com/AOSB/android/commit/a512f16890af8c277c3d1a88c8bca36711b82328
Click to expand...
Click to collapse
That looks interesting, but it's for KitKat... I'll try later once I'm confident. In the meantime, how can I get this to work: https://github.com/SlimRoms/packages_apps_Settings/commit/fb2ea42468bea20f09b99048c9e7535b6cde643f I'm OK apart from the very last bit in UserInterface.java, although I'm applying that code to SystemSettings.java anyway. Thanks
@demkantor @_MarcoMarinho_ I've synced the PA source, can you help me at all setting up the vision.adds file? Thanks
Sure thing, assume this is for 4.2 android right?
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Sure thing, assume this is for 4.2 android right?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep, as you know I synced the CM10.1 source a while ago so I used repo init --reference to sync the PA jellybean-legacy sources. Thanks for helping
paste this in a folder and title it
local_manifests
then add it to your .repo folder in ROM directory
I commented out a few things you may need to add, and there is possibly more but i dont have time to look into it all right now. just start with this, repo sync, and then build and check for errors
best of luck!
damn.... giving me uknown file, had to zip it first, so unzip the contents!
demkantor said:
paste this in a folder and title it
local_manifests
then add it to your .repo folder in ROM directory
I commented out a few things you may need to add, and there is possibly more but i dont have time to look into it all right now. just start with this, repo sync, and then build and check for errors
best of luck!
damn.... giving me uknown file, had to zip it first, so unzip the contents!
Click to expand...
Click to collapse
Thanks, do I only need to add these to the vision.adds file then, or do I not need a vision.adds file at all now?
HTCDreamOn said:
Thanks, do I only need to add these to the vision.adds file then, or do I not need a vision.adds file at all now?
Click to expand...
Click to collapse
cant say I've ever used a vision.adds file in a source build, I just find the files i need in github, download source, create a local_manifest, sync, check errors for somethings to add to manifest, build, check for errors, google how to fix, fix, fix, fix ,fix, then bam, got a rom that works.
but I can look into this vision.adds business, I don't think it will be necessary as this will place need files in the proper directories in your source code for you, I assume that's what the vision.adds would do?
demkantor said:
cant say I've ever used a vision.adds file in a source build, I just find the files i need in github, download source, create a local_manifest, sync, check errors for somethings to add to manifest, build, check for errors, google how to fix, fix, fix, fix ,fix, then bam, got a rom that works.
but I can look into this vision.adds business, I don't think it will be necessary as this will place need files in the proper directories in your source code for you, I assume that's what the vision.adds would do?
Click to expand...
Click to collapse
Here's the bit from their guide: http://forum.xda-developers.com/showpost.php?p=30958881&postcount=2 I'm not sure what it does though. I'm completely clueless about that whole post actually. I think it just syncs stuff after a sync.. or something. I don't know why though, isn't that what a local manifests file is for?
hmm... it looks like there will be a bit more to make than just the local_manifests
but i would attempt this first and if it doesnt work than follow the direction in that post as there me be a special way needed to build for pa, which i never have tried to build
most of what they are after will get pulled from local_manifests folder and placed appropriately. but at the same time... never used ./rom-build.sh before so this may be specific to pa, as in you need to follow their steps....
eh, just give it a try, if it doesnt work ill help you create those json files and build it the way laid out in their guide!
HTCDreamOn said:
Here's the bit from their guide: http://forum.xda-developers.com/showpost.php?p=30958881&postcount=2 I'm not sure what it does though. I'm completely clueless about that whole post actually. I think it just syncs stuff after a sync.. or something. I don't know why though, isn't that what a local manifests file is for?
Click to expand...
Click to collapse
Isn't easy, you need to add more repos to configure it for our phone.
This is very diferent:
http://forum.xda-developers.com/showpost.php?p=45827346&postcount=3467
As I said before, you need extra repos than CM needs. You can talk to the dev that made the SlimBean for our phone, as it's based on AOSP he needed to configure it as well.