Related
anyone know if it's feasible to build the cm10.1 kernel without syncing the entire source?
I've tried googling it numerous times but nothing came up pertaining to it. i did however find how to build the cm9 kernel without syncing the entire source, bit couldn't get it to build...
thanks if anyone can help me five my way
ztotherad said:
anyone know if it's feasible to build the cm10.1 kernel without syncing the entire source?
I've tried googling it numerous times but nothing came up pertaining to it. i did however find how to build the cm9 kernel without syncing the entire source, bit couldn't get it to build...
thanks if anyone can help me five my way
Click to expand...
Click to collapse
See the Aries kernel tree on my github. Its a slightly modified version of the cyanogenmod tree, and includes a build script and initramfs so syncing the entire source tree isn't necessary to build from it.
jt1134 said:
See the Aries kernel tree on my github. Its a slightly modified version of the cyanogenmod tree, and includes a build script and initramfs so syncing the entire source tree isn't necessary to build from it.
Click to expand...
Click to collapse
thanks. i was honestly waiting for you to come in here and tell me it won't work without syncing it all, lol. I'll check it out though. thanks again! you effin' rock!
ztotherad said:
thanks. i was honestly waiting for you to come in here and tell me it won't work without syncing it all, lol. I'll check it out though. thanks again! you effin' rock!
Click to expand...
Click to collapse
NP. Iirc, I originally added the scripts after you asked me about it a few months back
All you should have to do is clone the repo, and then run the build.sh script that's included. It will download the right toolchain for you, build the initramfs archives and then compile the kernel.
I also set it up to create a flashable zip with the new kernel and modules, so the build script should handle all the essential steps automatically.
jt1134 said:
NP. Iirc, I originally added the scripts after you asked me about it a few months back
All you should have to do is clone the repo, and then run the build.sh script that's included. It will download the right toolchain for you, build the initramfs archives and then compile the kernel.
I also set it up to create a flashable zip with the new kernel and modules, so the build script should handle all the essential steps automatically.
Click to expand...
Click to collapse
haha yeah, cause a few months back you said i had to sync the whole source.
it sounds like you've been working your ass off. lol
but that's definitely awesome. it makes it easier on us all.
i want to download the CyanogenMod 10.2 source code. I searched a lot for this. As far I have known I have to use the following to initialize the repository:
Code:
$ cd ~/android/system/
$ repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
But the above one is for CyanogenMod 10.1 as there is cm-10.1 at the end of the code. should I use cm-10.2 to initialize the repository for CM 10.2? or is there any other method. Please help me.
I've even asked the same question in other threads but did not got any replies or help....
Plz anyone help me for this..
Yes, you need to add the cm-10.2 at the end to get the 10.2 repo. take a look at their readme on the github page, here is the link https://github.com/CyanogenMod/android
netwokz said:
Yes, you need to add the cm-10.2 at the end to get the 10.2 repo. take a look at their readme on the github page, here is the link https://github.com/CyanogenMod/android
Click to expand...
Click to collapse
I was too thinking of doing that but didn't find it anywhere.. Thanks a lot for your help.
netwokz said:
Yes, you need to add the cm-10.2 at the end to get the 10.2 repo. take a look at their readme on the github page, here is the link https://github.com/CyanogenMod/android
Click to expand...
Click to collapse
Can u also tell me, what might be the size of the source code, is it 20-30 GB. Or greater than that?
I want to say mine was between 15-20GB, but I would expect 20-30 to be on the safe side.
netwokz said:
I want to say mine was between 15-20GB, but I would expect 20-30 to be on the safe side.
Click to expand...
Click to collapse
15-20 GB of Cyanogenmod 10.2? really?
looks like I was off, my CyanogeMod folder for 10.2 is about 10GB. but it all depends on where you get it from, extra devices and or files might be included in the manifest, that you won't need.
netwokz said:
looks like I was off, my CyanogeMod folder for 10.2 is about 10GB. but it all depends on where you get it from, extra devices and or files might be included in the manifest, that you won't need.
Click to expand...
Click to collapse
ya right, finally i've got ready to download the source code, after that will make few commits and after that will try to add HALO for my Samsung Galaxy S3. Thanks for all your help.. And also it would be very nice for me if you could share my website on android, just started, still need improvements: http://technoxist.com/ Could you please help me making it more better?? If you can plz send me PM..
This helped
suyash1629 said:
15-20 GB of Cyanogenmod 10.2? really?
Click to expand...
Click to collapse
My build folder is about 15GB - that sounds about right.
fadedout said:
My build folder is about 15GB - that sounds about right.
Click to expand...
Click to collapse
I have both CM 10.2 and CM 11. I think build folder doesn't matter that much but the .repo folder size matter for the size of source code. .repo folder contains the source code which is synced to working directory when downloading source code is complete ,so the source code size will be of around 6-11GB according to the amdroid version you are downloading. My CM 10.2 source code size is about 6.8GB (.repo folder) and CM 11 is about 11GB. in both cases the size is of .repo folder
Hello everyone!
I present to you a paranoid android 3.99 port for our Xperia SP
Changelog:
V2: Device no longer hard reboots on bootanimation
V1: initial release
BUGS:
V2: Device doesn't boot (stuck on bootanimation and ADB offline)
V1: Device doesn't boot (hard reboot after 10 seconds of showing splash screen)
Download: PA_HUASHAN_V2
Now as you can see this ROM port is not booting but at least it doesn't do a hard reboot anymore! Currently I have no ADB access as it is listed as offline when doing: ADB devices of course I can't figure out the problem myself so I'm asking you guys for help. Since there is no logcat I know that it might be nasty to determine the problem and where the phone stops booting. I hope you guys can help me get this ROM to boot so we will finally have a working PA rom
thanks to: @-NickHalden- for his nice guide on how to port ROM's
@FXP for the base rom (cm10.2)
and the paranoid android team for the ROM that was ported (pa 3.99 from nexus 4)
Why don't you simply build from source?
kamarush said:
Why don't you simply build from source?
Click to expand...
Click to collapse
I'm trying that as well but i'm having some issues getting these files working
<device>.adds
<device>.removes
pa_<device>.conf
pa_<device>.mk
If I could easily get/make these files a source build would already be here
Do you have a idea on how to create these files? or where I can get them?
for example for the .adds file I need something like this (this comes from nexus 4)
https://github.com/ParanoidAndroid/android_vendor_pa/blob/jb43/manifests/mako.adds
It's pretty simple
Adds and removes are the repos what you need and don't need. About the makefiles. You can simple use the mako files as base, only need to change the values to match for our device.
kamarush said:
It's pretty simple
Adds and removes are the repos what you need and don't need. About the makefiles. You can simple use the mako files as base, only need to change the values to match for our device.
Click to expand...
Click to collapse
OK this is the .adds file I just made can you take a look at it?
huashan.adds
kamarush said:
Why don't you simply build from source?
Click to expand...
Click to collapse
A long ago, i dont have see you on xda....
now you've back....great master
OK guys PA is currently building from source! now let's prepare to wait a long time xD
noahvt said:
OK this is the .adds file I just made can you take a look at it?
huashan.adds
Click to expand...
Click to collapse
This file will be almost the same as the cm dependencies. So this isn't good.
Levered said:
A long ago, i dont have see you on xda....
now you've back....great master
Click to expand...
Click to collapse
Yeah was long time ago i just bought this device a week ago. I just came back to Sony from Samsung
noahvt said:
OK guys PA is currently building from source! now let's prepare to wait a long time xD
Click to expand...
Click to collapse
@kamarush
damn I ran into some building issues already (hopefully nothing to serious)
Lunching device
build/core/product_config.mk:231: *** device/sample/products/pa_huashan.mk: PRODUCT_NAME must be defined.. Stop.
Device huashan not found. Attempting to retrieve device repository from ParanoidAndroid Github (http://github.com/ParanoidAndroid).
Repository for huashan not found in the ParanoidAndroid Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/product_config.mk:231: *** device/sample/products/pa_huashan.mk: PRODUCT_NAME must be defined.. Stop.
** Don't have a product spec for: 'pa_huashan'
** Do you have the right repo manifest?
i'll upload my "pa_huashan.mk" file: https://mega.co.nz/#!gZESjTKQ!ESlhCwWQROoh53SFYJ5vqyA177o5jqZdy9V688BWUNs
EDIT: I modified my huashan.adds file
EDIT2: I really needs some help with this! I'm familiar with the compiling process of cyanogenmod but this is a whole new story
I'm a huge fan of PA, I hope this one for our SP will progress nicely. Keep up the good work devs. Currently on CM coz stock is too laggy on my one.
Tapatalked from my Xperia P
noahvt said:
@kamarush
damn I ran into some building issues already (hopefully nothing to serious)
Lunching device
build/core/product_config.mk:231: *** device/sample/products/pa_huashan.mk: PRODUCT_NAME must be defined.. Stop.
Device huashan not found. Attempting to retrieve device repository from ParanoidAndroid Github (http://github.com/ParanoidAndroid).
Repository for huashan not found in the ParanoidAndroid Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/product_config.mk:231: *** device/sample/products/pa_huashan.mk: PRODUCT_NAME must be defined.. Stop.
** Don't have a product spec for: 'pa_huashan'
** Do you have the right repo manifest?
i'll upload my "pa_huashan.mk" file: https://mega.co.nz/#!gZESjTKQ!ESlhCwWQROoh53SFYJ5vqyA177o5jqZdy9V688BWUNs
EDIT: I modified my huashan.adds file
EDIT2: I really needs some help with this! I'm familiar with the compiling process of cyanogenmod but this is a whole new story
Click to expand...
Click to collapse
Just need to update/add pa_huashan to the pa vendor makefiles.
@kamarush
Remember you in developing the Xperia line 2011. Glad to see it with our Xperia SP. Some project in mind?
[QOUTE]Yeah was long time ago i just bought this device a week ago. I just came back to Sony from Samsung [/QUOTE]
Great, i really want rom by you. i hope you can make it soon..:good:
OK guys the build has started again! All my previous problems were caused by syncing the old repo (github.com/paranoidandroid) instead of the new one (github.com/AOSPA-legacy) if you get errors like I did try and use the new source (repo init -u git://github.com/AOSPA-legacy/manifest.git -b kitkat)
Just letting you guys know that this project isn't dead
noahvt said:
OK guys the build has started again! All my previous problems were caused by syncing the old repo (github.com/paranoidandroid) instead of the new one (github.com/AOSPA-legacy) if you get errors like I did try and use the new source (repo init -u git://github.com/AOSPA-legacy/manifest.git -b kitkat)
Just letting you guys know that this project isn't dead
Click to expand...
Click to collapse
When you port AOSPA to unlocked Bl's, could you make a version for locked BL's?
MrSteve555 said:
When you port AOSPA to unlocked Bl's, could you make a version for locked BL's?
Click to expand...
Click to collapse
I'm already using the locked bootloader vendor blobs
Sent from my C5303 using XDA Free mobile app
noahvt said:
I'm already using the locked bootloader vendor blobs
Sent from my C5303 using XDA Free mobile app
Click to expand...
Click to collapse
That's really good. :thumbsup: One last question, why aren't you porting the latest PA(4+)?
MrSteve555 said:
That's really good. :thumbsup: One last question, why aren't you porting the latest PA(4+)?
Click to expand...
Click to collapse
I am now! I forgot to tell you that the version updated this ROM will now be 4.4.2 kitkat!
@kamarush still getting product name not defined but build started! I'll finish it tomorrow
Sent from my C5303 using XDA Free mobile app
noahvt said:
I am now! I forgot to tell you that the version updated this ROM will now be 4.4.2 kitkat!
@kamarush still getting product name not defined but build started! I'll finish it tomorrow
Sent from my C5303 using XDA Free mobile app
Click to expand...
Click to collapse
It's really good! If you finish the build tomorrow, I'll flash it right away . I loved PA on my N7, and I think it's the one of the best ROM's on xda. Hopefully PA won't have that annoying freeze bug.
MrSteve555 said:
It's really good! If you finish the build tomorrow, I'll flash it right away . I loved PA on my N7, and I think it's the one of the best ROM's on xda. Hopefully PA won't have that annoying freeze bug.
Click to expand...
Click to collapse
Unfortunately it probably will have the freeze bug as it's based on the vendor blobs that bagyusz uses
Sent from my C5303 using XDA Free mobile app
Ok guys total git and gerrit noob here. im trying to learn to be able to upload to cyanogenmod gerrit so i can help out with some dev.
i have done:
signed up for cm gerrit
added my ssh key
setup git config to cm gerrit with my username and email that i used to signup with cm gerrit
all good so far. I synced up cm-13.0 sources. i repo cloned my device tree (which was from cyanogemod github).
i go
repo start cm-13.0 device/huawei/angler
it comes up with
error: project device/huawei/angler not found
if anyone can help me learn to be able to push commits for review i would very much appreciate it
Hello winxuser,
go into the directory you want to push to and make your changes. Commit them and push to CyanogenMod Gerrit:
git push ssh://[email protected]:29418/CyanogenMod/android_device_huawei_angler HEAD:refs/for/cm-13.0
(Replace your username with the one you choose while you registered.) I am pusing to AICP Gerrit every day. If I use repo start, it don't work for me too.
git push ssh://[email protected]:29418/CyanogenMod/device_huawei_angler HEAD:refs/for/cm-13.0
fatal: Project not found: CyanogenMod/device_huawei_angler
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Then:
git push ssh://[email protected]:29418/CyanogenMod/android_device_huawei_angler HEAD:refs/for/cm-13.0
Sorry, AICP is using another file structure.
Trafalgar Square said:
Then:
git push ssh://[email protected]:29418/CyanogenMod/android_device_huawei_angler HEAD:refs/for/cm-13.0
Sorry, AICP is using another file structure.
Click to expand...
Click to collapse
Ohh woops yes I forgot the android part hahaha,, well I was going to push the changes but I noticed none of the other nexus devices have it so I'm not sure
Sent from my Nexus 6P using XDA-Developers mobile app
I compiled angler cm using XXXHDPI dalvik heap and hwui, instead of xhdpi dalvik.. Just not sure what the advantage of that would be.. Just figured it would be better setting the dalvik up as xxxhdpi, it is a xxxhdpi device with 3gb ram
Sent from my Nexus 6P using XDA-Developers mobile app
ok change has been made and uploaded to gerrit,, what if i have missed something and i need to update it, how to i make patchsets?
Sorry, I don't know about patch sets.
But...
http://stackoverflow.com/questions/16118947/how-to-create-a-new-patchset-in-gerrit
Its all good I figured it out thanks for your help
Sent from my Nexus 6P using XDA-Developers mobile app
Sure man.
You helped a lot with your ROMs in Galaxy S3 LTE section and now I helped you
Trafalgar Square said:
Sure man.
You helped a lot with your ROMs in Galaxy S3 LTE section and now I helped you
Click to expand...
Click to collapse
Oh that's where I remember your name from.. I would of continued the work there but the phone that got donated to me the backlight ended up dying on it so I couldn't use it
Sent from my Nexus 6P using XDA-Developers mobile app
I have a kernel that I need to merge MM-mr2 in. So I have my kernel and MM-mr2 in my github. I just need to merge mr2 into my base. I have googled my a** of and havent had any luck. Someone who could help with the commands it would be greatly appreciated
Not sure I am tracking completely. I'll do what I can to answer your query.
From what you are describing, you have 2 branches, Master and MM-mr2 for your kernel. Refer to Basic Branching and Merging and more Visual explanation here.
The critical thing to know is that, both should be your branches. If one of them is owned by someone else, then you will be required to create a Pull Request.
Basically here are the steps you'd follow.
Checkout your master Branch where your other branch is going to be merged.
I assume MM-MR2 is another branch in the same repository Tree. If so, just issue ,
Code:
git merge MM-mr2
Now issue git status command to see the merge resulted in conflicts. It most likely will depending on what MR2 had that master did not.
Resolve the conflicts, then issue,
git add -A
this will add all the modified files to your commit. At which time you can do
git commit --amend
which will create a new commit on the master branch. This you can push to your git.
Oh and FYI, this thread is a good resource to me. [Guide] How to use Github
Perseus said:
Not sure I am tracking completely. I'll do what I can to answer your query.
From what you are describing, you have 2 branches, Master and MM-mr2 for your kernel. Refer to Basic Branching and Merging and more Visual explanation here.
The critical thing to know is that, both should be your branches. If one of them is owned by someone else, then you will be required to create a Pull Request.
Basically here are the steps you'd follow.
Checkout your master Branch where your other branch is going to be merged.
I assume MM-MR2 is another branch in the same repository Tree. If so, just issue ,
Code:
git merge MM-mr2
Now issue git status command to see the merge resulted in conflicts. It most likely will depending on what MR2 had that master did not.
Resolve the conflicts, then issue,
git add -A
this will add all the modified files to your commit. At which time you can do
git commit --amend
which will create a new commit on the master branch. This you can push to your git.
Oh and FYI, this thread is a good resource to me. [Guide] How to use Github
Click to expand...
Click to collapse
Heres my github https://github.com/APOPHIS9283
I need to merge shamu-mr2, into Project-Rachel
apophis9283 said:
Heres my github https://github.com/APOPHIS9283
I need to merge shamu-mr2, into Project-Rachel
Click to expand...
Click to collapse
Merging two repos is a immense undertaking. Not that it can not be done. But it means enormous amount of work. It is not the same as merging two branches, as I assumed earlier.
Would you care to explain why those two repos need to be merged? Is there a set of commits from one that you'd like in the other ?
Yeah my kernel is pretty much marshmallow. I need to bring in marshmallow mr2 to have it up to date with Google
*BUMP*
Anyone?
apophis9283 said:
Yeah my kernel is pretty much marshmallow. I need to bring in marshmallow mr2 to have it up to date with Google
Click to expand...
Click to collapse
In that case, do a Diff on github.com and choose those two to compare. That will create a Pull Request that you can merge. Please see this Tut.
Perseus said:
In that case, do a Diff on github.com and choose those two to compare. That will create a Pull Request that you can merge. Please see this Tut.
Click to expand...
Click to collapse
One last question. Sorry Github and such has always beena weak point.
https://android.googlesource.com/kernel/msm/+/android-msm-shamu-3.10-marshmallow-mr2/
I try to fork that but there doesnt seem to be a way
apophis9283 said:
Yeah my kernel is pretty much marshmallow. I need to bring in marshmallow mr2 to have it up to date with Google
Click to expand...
Click to collapse
apophis9283 said:
One last question. Sorry Github and such has always beena weak point.
https://android.googlesource.com/kernel/msm/+/android-msm-shamu-3.10-marshmallow-mr2/
I try to fork that but there doesnt seem to be a way
Click to expand...
Click to collapse
Trust me when I say, I HATE Git for the obnoxious, inane and downright silly errors it throws at me. You're not the first and most definitely not the last.
As to that link, unfortunately you will need to download a archive (See that .tgz link up top ? ). Expand the contents locally, then create a dummy repo in your own Git via web. Then Push the local unzipped folder to that Repo. The end result on Github should look exactly like what is at that link. Here's a Link that might help.
Perseus said:
Trust me when I say, I HATE Git for the obnoxious, inane and downright silly errors it throws at me. You're not the first and most definitely not the last.
As to that link, unfortunately you will need to download a archive (See that .tgz link up top ? ). Expand the contents locally, then create a dummy repo in your own Git via web. Then Push the local unzipped folder to that Repo. The end result on Github should look exactly like what is at that link.
Click to expand...
Click to collapse
I created a dummy github account and forked mr2. No matter what I do I cant even see mr2 as an option. This has been so frustrating I just dont have the patience to deal with it anymore. I truly appreciate your time
Thanks to xanax droid. I literally had to type in 4 commands and bam. I was fone that quick