Related
I want to start developing a custom rom(or at least to try).But firstly I don't know how to setup git and python on ubuntu.I read on google that I need that files.And when I set them up,how can I get the source code?If you know,please help.
Thanks in advance.
Edit: We downloaded the cyanogenmod source code successfully with repo.
Another question: Do I need python when I have eclipse?
If you know how, please tell us!
I know you can download source codes at github.com.
That's all I know....
Joost
Get linux and learn to use then get git then use git to get repo then use repo to download sources.
Mark
Pm me where u are at and i will help more in depth with u.
Mark
pashinator said:
Get linux and learn to use then get git then use git to get repo then use repo to download sources.
Mark
Click to expand...
Click to collapse
I know how to use ubuntu.I think I downloaded the kernel yesterday but don't know where it is.
Currently there are no proper manifest for compiling Android 2.2 or 2.3 for LG Swift, those that exist are outdated or deleted by the developers. We need a correct manifest for,lg shift device, vendor, kernel..etc to start building.
fdespotovski said:
I want to start developing a custom rom(or at least to try).But firstly I don't know how to setup git and python on ubuntu.I read on google that I need that files.And when I set them up,how can I get the source code?If you know,please help.
Thanks in advance.
Edit: We downloaded the cyanogenmod source code successfully with repo.
Another question: Do I need python when I have eclipse?
Click to expand...
Click to collapse
Can somebody tell us how to compile the system and kernel for unsupported devices like the lg gt540?
this is from the readme with Quarx rom if that helps
Компиляция:
make -j3 ARCH=arm CROSS_COMPILE=/путь до ndk/build/prebuilt/linux-x86/arm-eabi-4.4.0/bin/arm-eabi-
eoghan2t7 said:
this is from the readme with Quarx rom if that helps
Компиляция:
make -j3 ARCH=arm CROSS_COMPILE=/путь до ndk/build/prebuilt/linux-x86/arm-eabi-4.4.0/bin/arm-eabi-
Click to expand...
Click to collapse
Thanks for your reply!
Thanks to the amazing work of mapkel you can now use this script to compile and pack the kernel!
UPDATE: read mapkel's post here: http://forum.xda-developers.com/showpost.php?p=43419784&postcount=45
Thank him here.
This is an informative guide and I decline responsibility for any damage to your device.
Do not attempt to build this kernel if you are going to complain to devs about issues.
That being said, mapkel has made this so that even those with little knowledge can build the kernel without any issues. If you do have any issues, post here and I will try to assist you.
The following is a complete tutorial to building the kernel.
Credits:
Kernel Devs: krystianp, lehjr, Epinter, and mmontuori for making this kernel; without them there is no kernel.
Big thanks to mapkel for this amazing script.
Another big thanks to benouch for the original idea.
A final big thanks to zen25205 for help with building the kernel and getting the Linaro Toolchain.
Kernel Kitchen
I suggest building this with the latest CM9 MROM until the public beta is released.
You need to install Ubuntu 12.04 64bit (Google for instructions)
Prerequisites:
Open a terminal and run the following commands the first time:
Code:
sudo apt-get install -y build-essential kernel-package libncurses5-dev bzip2
Code:
sudo apt-get install git
If there are any issues with this guide, or if you have any issues building the kernel, post here and I will assist you as best I can.
Stage 1 (start at stage 2 if you have already built the kernel using this script:
Code:
cd ~
Code:
wget https://www.cubby.com/pl/kernel_script.zip/_25f010125b924ec7a42fe1d66245f36a
Code:
unzip ${HOME}/kernel_script.zip -d ${HOME}
Stage 2:
Code:
cd kernel
Code:
./script
There will be 4 choices to make throughout the script:
Clean install y/n (choose "n" on first run of script)
What defconfig? (Usually it is MROM but in the last update it is temporarily MROM2)
Compile CM9 or CM10 kernel? (self explanatory)
Name of config (Any name works. I chose "olympus".)
enjoy)
Built but cam not working
paladin881 said:
Built but cam not working
Click to expand...
Click to collapse
cameras disabled due to battery drain
Click to expand...
Click to collapse
https://github.com/CyanogenMod-Atrix/android_kernel_motorola_olympus/commits/master
Post here if it worked well for you. Give some feedback for mapkel.
No Wifi
Cheers, the script works great on Ubuntu 11.10, without a hic.
However, upon flashing the kernel, I get no wifi. I'm going to try your step by step tutorial...
Edit: I built the kernel using MROM2 defconfig and for CM10, and flashed "someone's" CM10
Newbleeto said:
Cheers, the script works great on Ubuntu 11.10, without a hic.
However, upon flashing the kernel, I get no wifi. I'm going to try your step by step tutorial...
Edit: I built the kernel using MROM2 defconfig and for CM10, and flashed "someone's" CM10
Click to expand...
Click to collapse
Strange..
The modules should copy with this.
Try CM9
atrix4g18 said:
Strange..
The modules should copy with this.
Try CM9
Click to expand...
Click to collapse
I'm updating Ubuntu, maybe the problem is on my end. Will try CM9 in the meanwhile and let you know!
Newbleeto said:
I'm updating Ubuntu, maybe the problem is on my end. Will try CM9 in the meanwhile and let you know!
Click to expand...
Click to collapse
You won't be able to do both.
If you compiled the kernel for CM10 you will only be able to use it on CM10.
Unless you are able to update Ubuntu as you compile the kernel for CM9.
atrix4g18 said:
You won't be able to do both.
If you compiled the kernel for CM10 you will only be able to use it on CM10.
Unless you are able to update Ubuntu as you compile the kernel for CM9.
Click to expand...
Click to collapse
It's impossible to compile while updating, didn't remember that, silly me :silly:
Anyhoot, wifi still doesn't work in Ubuntu 12.04. Fresh install on a different PC, way faster than updating
I'll try CM9 tomorrow, should've been asleep for a while
Can anyone or everyone list sites that work with a direct link.
That means I go to www.sitename/filename.zip and it starts downloading.
All I can think of right now is a cloud storage like Dropbox or Google Drive. I know Dropbox has a traffic limit for public files. Don't know about Google drive
Sent from my MB860 using xda app-developers app
upndwn4par has unlimited bandwidth, iirc. Maybe you can contact him and ask if you can host that one tiny script file there?
Or you could sign up with a free webhost and upload it there. There are several free webhosts with unlimited bandwidth (with a very limited space as trade-off, but I think it's more than enough for the script file).
If it's just a single script, maybe something like pastebin.com or similar might be an option? A little inconvenient since you have to copy and paste content instead of just download, but AFAIK it does have unlimited bandwidth.
atrix4g18 said:
Can anyone or everyone list sites that work with a direct link.
Click to expand...
Click to collapse
Maybe copy.com? Here is my ref for extra 5 GB: https://copy.com?r=qfhUoV
If this does not solve the problem, I can provide space for the script on my own server with a separate FTP account.
priard said:
Maybe copy.com? Here is my ref for extra 5 GB: https://copy.com?r=qfhUoV
If this does not solve the problem, I can provide space for the script on my own server with a separate FTP account.
Click to expand...
Click to collapse
Doesn't have a direct download link.
quetzalcoatl2435 said:
Doesn't have a direct download link.
Click to expand...
Click to collapse
Not quite. You can still download a file, for example using wget.
If You have a short public link, for instance: copy.com/PJzYgAUKECQm, You need to open it and copy the full link. In this case: copy.com/s/PJzYgAUKECQm/BetterBatteryStats_xdaedition_1.13.4.0.apk
then:
wget copy.com/s/PJzYgAUKECQm/BetterBatteryStats_xdaedition_1.13.4.0.apk
and done.
I will look at all the suggestions later today.
Thank you.
Delete
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.
Thanks to mamenyaka's efforts, we now have a running version of Ubuntu Touch on the Xperia Tablet Z. I'm attempting to do some customization of this kernel (such as add btusb support), but I'm not all the familiar with the Cyanogen build process. So looking for a little help here.
I've been following these instructions:
http://wiki.cyanogenmod.org/w/Build_for_pollux_windy
Now, I think the process is as follows:
Setup environment according to the wiki, up through the "repo init" step.
Add the "local_manifest.xml" from https://github.com/mamenyaka/android/ to ~/android/system/.repo/local_manifests
Run a repo sync in ~/android/system.
and this is where I get a bit confused. I _think_ the next step is then to run source build/envsetup.sh and breakfast pollux_windy, and then proceed according to the instructions as usual, excepting extracting the blobs. I think those are already included.
However, can someone confirm this? Or is there a step/steps I'm leaving out?
Thanks.
PS - yes, this should probably be in the dev forum, but the post count rules are forcing me to post it here...
If you want to build Ubuntu Touch, you should follow the porting guide.
You can't mix the two. The CM repo init and ubuntu's phablet-dev-bootstrap (ubuntu's repo init) use very different manifest.xmls. And if you want to build CM (advised if you never built android from source), you don't need the repos from my github.
Next thing: breakfast. It is a good to use when you build CM, but it's not good for building Ubuntu Touch. Breakfast adds CM repos specific to your device in a file in .repo/local_manifest (roomservice.xml). For Ubuntu Touch you don't need all of the device specific repos and you also need to apply some modifications in these repos (which I already done), and to use them, you will need to add the repos manually (local_manifest/local_manifest.xml, similar to roomservice.xml, but I prefer this file, because roomservice.xml is related to breakfast), so no breakfast needed.
Then simply repo sync to get the new repos.
The extra blobs are included thanks to TheMuppets repos.
To start building, simply $ . build/envsetup.sh and $ brunch pollux_windy. But all of this can be found in the guide or on CM wiki.
For building Ubuntu Touch you need a few extra things mentioned in the guide, like the phablet tool, and you need to update the ubuntu/platform-api bzr repo (bzr pull) - this isn't done by repo sync because it isn't a git repo, it's ubuntu's bazaar.
mamenyaka said:
If you want to build Ubuntu Touch, you should follow the porting guide.
You can't mix the two. The CM repo init and ubuntu's phablet-dev-bootstrap (ubuntu's repo init) use very different manifest.xmls. And if you want to build CM (advised if you never built android from source), you don't need the repos from my github.
Next thing: breakfast. It is a good to use when you build CM, but it's not good for building Ubuntu Touch. Breakfast adds CM repos specific to your device in a file in .repo/local_manifest (roomservice.xml). For Ubuntu Touch you don't need all of the device specific repos and you also need to apply some modifications in these repos (which I already done), and to use them, you will need to add the repos manually (local_manifest/local_manifest.xml, similar to roomservice.xml, but I prefer this file, because roomservice.xml is related to breakfast), so no breakfast needed.
Then simply repo sync to get the new repos.
The extra blobs are included thanks to TheMuppets repos.
To start building, simply $ . build/envsetup.sh and $ brunch pollux_windy. But all of this can be found in the guide or on CM wiki.
For building Ubuntu Touch you need a few extra things mentioned in the guide, like the phablet tool, and you need to update the ubuntu/platform-api bzr repo (bzr pull) - this isn't done by repo sync because it isn't a git repo, it's ubuntu's bazaar.
Click to expand...
Click to collapse
Okay, thanks for pointing me in the right direction. Thought I had to use CM build instead to use your repos. That's why this thread is here. I'd like to get instructions out here that could decrease the learning curve on some of this.
Are you aware of the state of CM on pollux_windy? I notice that Ubuntu has breakfast in their official porting guide now. Would you expect that to work, or are there further changes in your repositories to enhance their work?
In other words, Ubuntu's guide suggests doing a "breakfast pollux_windy", "repo sync", some tweaks, and then a build, under the Automatic build section.
I think your repo would work with the process under the "Manual (deprecated)" section. Is there a reason to use one over the other? Have you already integrated the required modifications in your repos, for example?
Sorry if this is all a bit pedantic. Just trying to come up to speed on the build process for all of this. I've built many a linux kernel, but I'm not at all familiar with this build process.
Thanks again for your help.
themikem said:
Okay, thanks for pointing me in the right direction. Thought I had to use CM build instead to use your repos. That's why this thread is here. I'd like to get instructions out here that could decrease the learning curve on some of this.
Are you aware of the state of CM on pollux_windy? I notice that Ubuntu has breakfast in their official porting guide now. Would you expect that to work, or are there further changes in your repositories to enhance their work?
In other words, Ubuntu's guide suggests doing a "breakfast pollux_windy", "repo sync", some tweaks, and then a build, under the Automatic build section.
I think your repo would work with the process under the "Manual (deprecated)" section. Is there a reason to use one over the other? Have you already integrated the required modifications in your repos, for example?
Sorry if this is all a bit pedantic. Just trying to come up to speed on the build process for all of this. I've built many a linux kernel, but I'm not at all familiar with this build process.
Thanks again for your help.
Click to expand...
Click to collapse
Don't worry, I am here to answer your questions.
So, breakfast in Ubuntu Touch is good when you want to start off a brand new port.
The advantage of using my repos and using the manual method is that I already integrated the required modifications and, most importatnly, the image builds. Simply using the CM repos, you would get build errors, which are fixed in my repos; for example, removing the android parts.
Also, if you are interested, you could join this group.
mamenyaka said:
Don't worry, I am here to answer your questions.
So, breakfast in Ubuntu Touch is good when you want to start off a brand new port.
The advantage of using my repos and using the manual method is that I already integrated the required modifications and, most importatnly, the image builds. Simply using the CM repos, you would get build errors, which are fixed in my repos; for example, removing the android parts.
Also, if you are interested, you could join this group.
Click to expand...
Click to collapse
Thanks for the tip. It worked!
For the record, it turned out to be this simple:
(~/phablet is arbitrary)
mkdir ~/phablet && cd ~/phablet
phablet-dev-bootstrap ~/phablet
repo sync
Add ~/phablet/.repo/local_manifests/local_manifest.xml from: https://github.com/mamenyaka/android
repo sync
. build/envsetup.sh
brunch pollux_windy
...and then flash the files from $OUT (~/android/system/out/target/product/pollux_windy)
Also note that I had a terrible time making git work through my NAT. Tried both a hardware router (Cisco) and my standard Vyatta VM. Ultimately had to put my build machine directly on a publicly-routable IP to make it go. If you're having problems with Git on 13.04, it could be the same issue. I'm not aware of any other fix, other than finding some way to switch the build system to http:// instead of git://
Now off to reconfigure the kernel. This should be interesting...
One thing, without this you won't be able too boot.
You need to replace boot.img from the .zip with ubuntu-boot.img from $OUT and rename, of course, to boot.img.
ubuntu-boot.img should be bigger in size.
Hope this is the right place, but am I correct to assume that its possible to run Ubuntu Touch on the Xperia Z Tablet?
If so are there any tutorials on this?
Tel'X
telx85 said:
Hope this is the right place, but am I correct to assume that its possible to run Ubuntu Touch on the Xperia Z Tablet?
If so are there any tutorials on this?
Tel'X
Click to expand...
Click to collapse
You gotta be kidding, right?
http://forum.xda-developers.com/showthread.php?t=2336018
mamenyaka said:
You gotta be kidding, right?
http://forum.xda-developers.com/showthread.php?t=2336018
Click to expand...
Click to collapse
Nope, but thanks for that.
Looks very promising.
mamenyaka said:
Don't worry, I am here to answer your questions.
So, breakfast in Ubuntu Touch is good when you want to start off a brand new port.
The advantage of using my repos and using the manual method is that I already integrated the required modifications and, most importatnly, the image builds. Simply using the CM repos, you would get build errors, which are fixed in my repos; for example, removing the android parts.
Also, if you are interested, you could join this group.
Click to expand...
Click to collapse
I have some questions, for example I want to try build the ubuntu touch to a new port (actually not new port, just the progress of development of my phone is held on), I just refer to your local manifest.xml file? Sure I know need to change to device specific repo, I have it on other developer github.
Just the question is, how do I recognise which part is belong to android parts and remove them? Or which part should be remained?
Sent from my SGP311 using xda app-developers app
Trevor Chuah said:
I have some questions, for example I want to try build the ubuntu touch to a new port (actually not new port, just the progress of development of my phone is held on), I just refer to your local manifest.xml file? Sure I know need to change to device specific repo, I have it on other developer github.
Just the question is, how do I recognise which part is belong to android parts and remove them? Or which part should be remained?
Sent from my SGP311 using xda app-developers app
Click to expand...
Click to collapse
You have a cm.dependencies file in your device's repo which tells what other repos it needs (for example kernel).
You can instantly remove any android app related repo (like android_packages_apps_FMRadio).
But if you tell me what phone, I can give you some hints.
mamenyaka said:
You have a cm.dependencies file in your device's repo which tells what other repos it needs (for example kernel).
You can instantly remove any android app related repo (like android_packages_apps_FMRadio).
But if you tell me what phone, I can give you some hints.
Click to expand...
Click to collapse
The phone I'm using is Xperia S. The developer has his github name OpenSEMC.
Thank you.
Sent from my Xperia S using xda app-developers app
Trevor Chuah said:
The phone I'm using is Xperia S. The developer has his github name OpenSEMC.
Thank you.
Sent from my Xperia S using xda app-developers app
Click to expand...
Click to collapse
You could start over from scratch. Just fork the CM repos. The OpenSEMC repos are not really ubuntu touch oriented.
mamenyaka said:
You could start over from scratch. Just fork the CM repos. The OpenSEMC repos are not really ubuntu touch oriented.
Click to expand...
Click to collapse
Okay. So basically the post #5 is applicable to every phone right?
I just follow it and modify the
1) local manifest to correct repo
2) remove the android part
Right?
I will try it.
Thank you.
Sent from my Xperia S using xda app-developers app
May I ask?
If I use phablet-dev-bootstrap, it will follow the android.git in http://phablet.ubuntu.com/gitweb right?
I did it, and
I checked the default.xml inside the android repo, to roughly compare with the file synced into local.
I found that it has many thing missing, for example the following:
Code:
<project path="external/mockwebserver" name="CyanogenMod/android_external_mockwebserver" />
<project path="external/mp4parser" name="CyanogenMod/android_external_mp4parser" />
<project path="frameworks/opt/inputmethodcommon" name="CyanogenMod/android_frameworks_opt_inputmethodcommon" />
<project path="frameworks/opt/mailcommon" name="CyanogenMod/android_frameworks_opt_mailcommon" />
and many of them.
Is it ubuntu automatically not download these file since they are not important?
Trevor Chuah said:
May I ask?
If I use phablet-dev-bootstrap, it will follow the android.git in http://phablet.ubuntu.com/gitweb right?
I did it, and
I checked the default.xml inside the android repo, to roughly compare with the file synced into local.
I found that it has many thing missing, for example the following:
Code:
<project path="external/mockwebserver" name="CyanogenMod/android_external_mockwebserver" />
<project path="external/mp4parser" name="CyanogenMod/android_external_mp4parser" />
<project path="frameworks/opt/inputmethodcommon" name="CyanogenMod/android_frameworks_opt_inputmethodcommon" />
<project path="frameworks/opt/mailcommon" name="CyanogenMod/android_frameworks_opt_mailcommon" />
and many of them.
Is it ubuntu automatically not download these file since they are not important?
Click to expand...
Click to collapse
Be sure to check out the phablet-saucy branch of default.xml, that's what phablet-dev-bootstrap pulls.
---------- Post added at 11:40 AM ---------- Previous post was at 11:30 AM ----------
Trevor Chuah said:
Okay. So basically the post #5 is applicable to every phone right?
I just follow it and modify the
1) local manifest to correct repo
2) remove the android part
Right?
I will try it.
Thank you.
Sent from my Xperia S using xda app-developers app
Click to expand...
Click to collapse
Mostly right, but there is always something extra that needs to be done with every device.
Be sure to get the sony proprietary blobs from TheMuppets on github and post any questions, errors you need help with.
mamenyaka said:
Be sure to check out the phablet-saucy branch of default.xml, that's what phablet-dev-bootstrap pulls.
---------- Post added at 11:40 AM ---------- Previous post was at 11:30 AM ----------
Mostly right, but there is always something extra that needs to be done with every device.
Be sure to get the sony proprietary blobs from TheMuppets on github and post any questions, errors you need help with.
Click to expand...
Click to collapse
The following is my local_manifest.xml file
Code:
<project path="device/sony/common" name="OpenSEMC/android_device_sony_common" remote="github" revision="cm-10.1" />
<project path="device/sony/nozomi" name="OpenSEMC/android_device_sony_nozomi" remote="github" revision="cm-10.1" />
<project path="device/sony/fuji-common" name="OpenSEMC/android_device_sony_fuji-common" remote="github" revision="cm-10.1" />
<project path="device/sony/qcom-common" name="OpenSEMC/android_device_sony_qcom-common" remote="github" revision="cm-10.1-legacy" />
<project path="kernel/sony/msm8x60" name="OpenSEMC/android_kernel_sony_msm8x60" remote="github" revision="cm-10.1-legacy" />
<project path="vendor/sony" name="OpenSEMC/proprietary_vendor_sony" remote="github" revision="cm-10.1-lagacy" />
<project path="hardware/sony/DASH" name="OpenSEMC/android_hardware_sony_DASH" remote="github" revision="cm-10.1" />
<project path="hardware/qcom/media" name="OpenSEMC/android_hardware_qcom_media-legacy" remote="github" revision="cm-10.1-legacy" />
I referred to your local_minifest.xml and the original author xml file and conclude this.
I do not know is it correct or not.
May I ask, will the recovery automatically add into the compile device image? What will it use? CWM?
Trevor Chuah said:
The following is my local_manifest.xml file
I referred to your local_minifest.xml and the original author xml file and conclude this.
I do not know is it correct or not.
May I ask, will the recovery automatically add into the compile device image? What will it use? CWM?
Click to expand...
Click to collapse
I think you should go with CyanogenMod for all repos except vendor, and TheMuppets for the vendor/sony (revision=cm-10.1 for all) if you want to start clean. Then just follow the porting guide.
It will use CWM.
mamenyaka said:
I think you should go with CyanogenMod for all repos except vendor, and TheMuppets for the vendor/sony (revision=cm-10.1 for all) if you want to start clean. Then just follow the porting guide.
It will use CWM.
Click to expand...
Click to collapse
But CyanogenMod (FXP) did not publish CM10.1 for Xperia S, heard that they do not fix for the display.
Therefore I do not know whether if use the CM repo, what should I modify for the video to display.
Still newbie...
Trevor Chuah said:
But CyanogenMod (FXP) did not publish CM10.1 for Xperia S, heard that they do not fix for the display.
Therefore I do not know whether if use the CM repo, what should I modify for the video to display.
Still newbie...
Click to expand...
Click to collapse
I don't know much about nozomi. There exists the CM 10.1 repo for nozomi, but true, there is no cm-10.1 release.
You might have to experiment a little, stuff like common, qcom, DASH are available in CM, but if they have device specific fixes, than it may be the only route to use OpenSEMC repos.
Building AOSP for the Nexus 6 - Continued!
Scott is no longer working with the N6 and he has graciously allowed me to continue his thread . We all owe @scrosler a special THANKS for his work on the original thread. Better yet please go buy him a beer!! I also want to personally thank all who contributed to the original thread. You all make it work!!
Preface
1. I want to start by saying that I am still a relative newb. I built my first aosp rom for my N9 using the the guide from the original thread and followed up with one for my N6. I hope that by moving this thread forward we can continue to help others get started while we continue our own learning.
2. All questions concerning the build process and setup are welcome. They may not all get answered but please ask.
This guide continuation assumes the following:
1. You have read the original thread's OP and scanned the remainder of that thread before posting here.
2. To get things started you can test a rom built from android-5.1.1_r14. Get rom below. Vendor blobs updated from here and include the updated LYZ28E blobs. I also added some missing build props.
3. I am also linking the github source for the rom. You can build your own. Get github source below.
4. I hope to add a short get started github tut in OP#2 and add a vendor folder setup discussion in OP#3. I'm still trying to figure out how @sykopompos did his. All help on this subject is welcome.
FYI TO ALL!!! All my testing is on USA Verizon netwok.
LINK TO ORIGINAL THREAD OP
Get ROM HERE
Get GIT SOURCE HERE
==========================================================================================================
The following copied from original OP with some minor editing.
This guide assumes the following
Have Ubuntu 14.04 or equivalent setup, fully operation, and up to date. Hard Machine or Virtual, makes no difference. Must meet the minimum specs for compiling. Info from Google HERE
Understand terminal command line entry as this is all command line processes.
Lets Begin!
Add Java
Code:
sudo apt-get install openjdk-7-jdk
Add Build tools (Adds the required packages at the time of this posting)
Code:
sudo apt-get install git gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386
Add Repo command (Syncs Google Repository with your local machine)
Code:
mkdir ~/bin && curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo && chmod a+x ~/bin/repo
Add bin folder to path for repo command (After you do this close Terminal and re-open to institute changes (easy way))
Code:
sudo gedit .bashrc
export PATH=~/bin:$PATH <-(add to end of bashrc)
Identify Yourself to the Repo (One day you may make commits so think about that when choosing your info!)
Code:
git config --global user.email "[email protected]"
git config --global user.name "yourpreferredusername"
Sync Repo (Download source... Sit back and grab a pop and a sandwich...)
Code:
mkdir ~/AOSP
cd ~/AOSP
repo init -u https://android.googlesource.com/platform/manifest -b android-5.1.1_r14
repo sync
Note: I use AOSP as my directory name. You can use what you want. You could use "aosp" or "Source" or "android" or "whateveryoulike"
Set up ccache (this makes subsequent compiling much faster!)
First: Close then re-open the terminal so you are in the home root
Code:
sudo gedit .bashrc
export USE_CCACHE=1 <-Append that line to .bashrc then save and close
cd AOSP
prebuilts/misc/linux-x86/ccache/ccache -M 25G <-I use 25 gigs but you can change that value to any size you feel appropriate)
fhem Alternate ccache setup.
Install ccache using package manager (I use synaptic)
set ccache size - One ccache for all directories.
Code:
ccache -M 35G (I use 35 gigs but you can change that value to any size you feel appropriate)
I do not edit my .bashrc I use the following before my final make command. See Readme Build It
You can choose to use or not use ccache for any build/operation from any directory.
Code:
export USE_CCACHE=1
ccache manual
Install proprietary binaries (Needed for things like GPS and Bluetooth, they are not Open Source like Android) (Install proprietary binaries from here in the root of AOSP folder (or whatever you called yours))
Code:
https://developers.google.com/android/nexus/drivers
Run envsetup.sh
Code:
source build/envsetup.sh
Choose Device
Code:
lunch aosp_shamu-userdebug
Build it!
Code:
make -j16 otapackage
Note: using -j16 means 16 worker threads. This is fine if you have 8 logical CPU's so you may need to adjust that to a smaller or larger number if you have more or less Logical CPU's. Example: I have an i7 K edition Haswell so I have 8 logical cores; so I build with -j16. If you have an i5 quad core CPU which is 4 logical cores then you may want to consider -j8 as the set number of worker threads. Oddly enough Google actually recommends 3 to 4 times the number of logical CPU's. When I do that I have nothing but build crashes. You may need to experiment to get the right blend of performance and stability during build!
If you use
Code:
make -j `getconf _NPROCESSORS_ONLN` otapackage
it may take a little longer but it won't crash.
Find it
Should be located here: /home/yourusername/AOSP/out/target/product/shamu
Congrats!
Your know among the elite enthusiast that can build from source! Pat yourself on the back!
Git Hub Tips
There is already much written on git use so I am not going to try and reinvent that wheel!!!! I will provide some usefull links for your reading pleasure. I will also provide some tips based on my personal experiences using git. I have found there are many ways to get the same result using git and there are also many ways to break your your work. I did a lot of trial and error and deleting to learn what works best for me. Start small, don't be intimidated, and stay patient -- it will come. The following assumes we are using a linux distro.
1. Open a GitHub account ----- its easy. Keep it simple. Follow the setup instructions and use recommended HTTPS connection.. I also suggest caching your login info - I use 60 mins for my default cache time.
2. Install git. It is easiest to install Git on Linux using the preferred package manager of your Linux distribution. I use Synaptic Package Manager. Keep it simple. Follow the setup instructions and use recommended HTTPS connection.
3. Git Tools: I prefer using Geany with terminal and File and Tree Browser and VC control plug-ins. There are many tools available and you may need to find one that works for you. You can install Geany and its plug-ins using your distro package manager.
4. ROM Tree Structure Very Important. I recommend keeping your rom GitHub tree structure in line with the Android Git Repositories.
Useful links:
1. http://git-scm.com/docs
2. http://gitref.org/creating/
3. http://forum.xda-developers.com/showthread.php?t=1877040 Thanks @eagleeyetom
4. http://forum.xda-developers.com/showthread.php?t=2763236 Thanks @jabza
5. http://forum.xda-developers.com/showthread.php?t=2329228 Thanks @Red Devil
I hope the above is helpful to getting you started on GitHub. Good Luck!!
reserved vendor folder discussion.
fhem said:
Building AOSP for the Nexus 6 - Continued!
Scott is no longer working with the N6 and he has graciously allowed me to continue his thread . We all owe @scrosler a special THANKS for his work on the original thread. Better yet please go buy him a beer!! I also want to personally thank all who contributed to the original thread. You all make it work!!
Preface
1. I want to start by saying that I am still a relative noob. I built my first aosp rom for my N9 using the the guide from the original thread and followed up with one for my N6. I hope that by moving this thread forward we can continue to help others get started while we continue our own learning.
2. All questions concerning the build process and setup are welcome. They may not all get answered but please ask.
This guide continuation assumes the following:
1. You have read the original thread's OP and scanned the remainder of that thread before posting here.
2. To get things started you can test a rom built from android-5.1.1_r4 using Sykopompos vendor blobs for 5.1. Get rom below.
3. I am also linking the github source for the rom. You can build your own. Get github source below.
4. I hope to add a short get started github tut in OP#2 and add a vendor folder setup discussion in OP#3. I'm still trying to figure out how Sykopompos did his. All help on this subject is welcome.
FYI TO ALL!!! All my testing is on USA Verizon netwok.
LINK TO ORIGINAL THREAD OP
Get ROM HERE
Get GIT SOURCE HERE
Click to expand...
Click to collapse
Lots and lots of dark magic ?
Hey great to see you. I thought you were kyaking LOL. You coming back for M????
fhem said:
Hey great to see you. I thought you were kyaking LOL. You coming back for M????
Click to expand...
Click to collapse
I actually just ordered my kayaking last night so hopefully I'll have it in time for next weekend.
Just popping in really and checking M out and seeing how it develops
sykopompos said:
I actually just ordered my kayaking last night so hopefully I'll have it in time for next weekend.
Just popping in really and checking M out and seeing how it develops
Click to expand...
Click to collapse
Still waiting for the full platform on aosp. Hey did you diff the stock rom and aosp rom to get your vendor blobs. I was setting up with BeyondCompare to give it a look. LOL Enjoy your time off and your family. Life is too short.
fhem said:
Still waiting for the full platform on aosp. Hey did you diff the stock rom and aosp rom to get your vendor blobs. I was setting up with BeyondCompare to give it a look. LOL Enjoy your time off and your family. Life is too short.
Click to expand...
Click to collapse
For the most part, you can diff and find file differences but aosp has it's own files and stuff like that so you gotta be able to figure out what they do
sykopompos said:
For the most part, you can diff and find file differences but aosp has it's own files and stuff like that so you gotta be able to figure out what they do
Click to expand...
Click to collapse
I was afraid you were going to tell me that. :laugh: Oh well It will give my old brain and google a workout. hahahaha Thanks and enjoy yourself.
Hey @fhem! Glad to see you take over, you're always very helpful!
In your Repo Int code above, did you mean "android-5.1.1_r4"? I wanted to double check that part for the guide.
purian23 said:
Hey @fhem! Glad to see you take over, you're always very helpful!
In your Repo Int code above, did you mean "android-5.1.1_r4"? I wanted to double check that part for the guide.
Click to expand...
Click to collapse
Yep. That's the latest. That's what I built above if you look at the fhemaosp default manifest.
fhem said:
Yep. That's the latest. That's what I built above if you look at the fhemaosp default manifest.
Click to expand...
Click to collapse
Okay cool! Just trying to save some headache if someone grabs the guide one listed lol.
purian23 said:
Okay cool! Just trying to save some headache if someone grabs the guide one listed lol.
Click to expand...
Click to collapse
Fixed thanks for catching that typo.
sykopompos said:
I actually just ordered my kayaking last night so hopefully I'll have it in time for next weekend.
Just popping in really and checking M out and seeing how it develops
Click to expand...
Click to collapse
Hello @sykopompos, I am just glad to see you here! Thanks for all your contributions!
I let @fhem take over the thread since he is more active than I. But I appreciate all the help you have given and will continue to give!
Knowledge is TRULY priceless!
-Scott
EDIT: Can someone put that on my tombstone, lol
Can we have guide about building ROM from open source? e.g LG open source. Actually I was trying to build a M1 review ROM with the LG open source but it fails. I tried several times and finally give op due to errors. I downloaded the android source and then follow this guide and then download LG G4 ROM from following.
http://opensource.lge.com/osSch/list?types=ALL&search=H815
I set up the environment and then started building but it fails again and again. I think it will be very helpful for every one who interested in building ROM from open source. Thanks
Sent from my LG-H815 using Tapatalk 2
janjan said:
Can we have guide about building ROM from open source? e.g LG open source. Actually I was trying to build a M1 review ROM with the LG open source but it fails. I tried several times and finally give op due to errors. I downloaded the android source and then follow this guide and then download LG G4 ROM from following.
http://opensource.lge.com/osSch/list?types=ALL&search=H815
I set up the environment and then started building but it fails again and again. I think it will be very helpful for every one who interested in building ROM from open source. Thanks
Sent from my LG-H815 using Tapatalk 2
Click to expand...
Click to collapse
I have never worked with any LG source codes. I would suggest you start your own thread on the LG G4 Forum. It definately sounds like you got enough to get one rolling. Good luck with the G4.
Hello,
I am trying to build android 5.1.1_r6 for the Nexus 6 and was able to get it to build and install. Had a weird issue where gapps would not install, but I think I fixed that by flashing a different set of gapps. My issue is that I am unable to hear people through the handset speaker when I make phone calls. I have no idea what it is. Apparently they can hear me, but I cant hear them. I can use speaker phone, but even that seems lower volume than normal.
Also, side question, since I am building AOSP 5.1.1_r6 am I supposed to use the preview binaries found here: https://developers.google.com/android/nexus/blobs-preview
or just use the factory image binaries?
Thank you
KerryWood34 said:
Hello,
I am trying to build android 5.1.1_r6 for the Nexus 6 and was able to get it to build and install. Had a weird issue where gapps would not install, but I think I fixed that by flashing a different set of gapps. My issue is that I am unable to hear people through the handset speaker when I make phone calls. I have no idea what it is. Apparently they can hear me, but I cant hear them. I can use speaker phone, but even that seems lower volume than normal.
Also, side question, since I am building AOSP 5.1.1_r6 am I supposed to use the preview binaries found here: https://developers.google.com/android/nexus/blobs-preview
or just use the factory image binaries?
Thank you
Click to expand...
Click to collapse
I haven't been able to get _r6 to build due to errors in frameworks/opt ever since merging so good for you on that. As for the binaries It was found a while back that the Google one were incomplete. People were using The vendor files from chroma in their stead. I haven't spoken to fhem in a couple of days but it looks like his github is under construction atm. I forked the vendor repo from him since he had changes that fixed some no sound issues as well. Again I've yet to build _r6 successfully so no idea if these will solve your issue but you're welcome to try them out? You can get them from my github here: https://github.com/rockinroyle/platform_vendor_moto_shamu
Let us know how it goes? I'm trying again after I clone frameworks from scratch.
rockinroyle said:
I haven't been able to get _r6 to build due to errors in frameworks/opt ever since merging so good for you on that. As for the binaries It was found a while back that the Google one were incomplete. People were using The vendor files from chroma in their stead. I haven't spoken to fhem in a couple of days but it looks like his github is under construction atm. I forked the vendor repo from him since he had changes that fixed some no sound issues as well. Again I've yet to build _r6 successfully so no idea if these will solve your issue but you're welcome to try them out? You can get them from my github here: https://github.com/rockinroyle/platform_vendor_moto_shamu
Let us know how it goes? I'm trying again after I clone frameworks from scratch.
Click to expand...
Click to collapse
I had no luck with r6 either. I reverted back to r5. I looked at chroma/zephk on git and I don't think he took the whole r6 merge to his git repos - not sure what he did.
I'm sticking to to r5 for now.
I've been building r6 fine with zero issues. Did notice the speaker issue on call but fixed it with two commits from chroma in device/moto/shamu for audio. I've also been using the latest binaries posted by google on the aosp page, no issues that I can tell. WiFi calling/normal calling, sound all around, SMS/MMS, all works.
Sent from my Nexus 6 using Tapatalk