Related
So talking to my buddy about all the "junk" loaded on the Samsung, he kept raving about how his old Nexus One was just the way I would like it. I would like to have a "plain" version of Android 2.1 on my phone. I have a coworker friend that's a Linux guru that's willing to help. Here's my questions.
Can I take take the Samsung released source for the hardware drivers and compile it with a stock Android 2.1 platform? I'm not asking for step by step. More of a 10,000 foot how to. Is that possible?
Can you leave the CSC and Modem info the same and just install a PDA ROM with Odin? Or would you be overwriting all of that info on the phone?
Thanks and if this has been answered before, please fill free to say "search is your friend" and give me the links...
hallfleming said:
So talking to my buddy about all the "junk" loaded on the Samsung, he kept raving about how his old Nexus One was just the way I would like it. I would like to have a "plain" version of Android 2.1 on my phone. I have a coworker friend that's a Linux guru that's willing to help. Here's my questions.
Can I take take the Samsung released source for the hardware drivers and compile it with a stock Android 2.1 platform? I'm not asking for step by step. More of a 10,000 foot how to. Is that possible?
Can you leave the CSC and Modem info the same and just install a PDA ROM with Odin? Or would you be overwriting all of that info on the phone?
Thanks and if this has been answered before, please fill free to say "search is your friend" and give me the links...
Click to expand...
Click to collapse
I unfortunately haven't the answer but I'd like to add that I am curious about this too.
dalingrin said:
I unfortunately haven't the answer but I'd like to add that I am curious about this too.
Click to expand...
Click to collapse
I'll second this and ask that if you do figure it out, please share with the community.
I think that vanilla Roms are a little further away in the future. First step in the process right now would be for someone to be able to compile a kernel from the Samsung released source code that works. Unfortunately the current Captivate kernel source code, when compiled, causes issues (voices garbled, lag when waking up the phone) that are not present in the stock precompiled kernel. These bugs are apparently not present in the other versions of the source code. Once these initial bugs are ironed out, we can truly start down the path of having custom fixes, and the devs can start to focus on bigger challenges, like making the vanilla Eclair or Froyo Roms to start working with our kernel. Good thing about this phone is that there are going to be so many versions of it, that parallel development is happening on multiple platforms. This will likely produce independent breakthroughs that could be theoretically ported between the platforms, but unfortunately it also slows down the development of each platform due to the quirks that have to be overcome. I hope that, in the future, we get to a place where all the source codes are merged into master repository that has all the necessary improvements and the ability to overcome individual platform quirks, so that the development can proceed more rapidly.
hallfleming said:
So talking to my buddy about all the "junk" loaded on the Samsung, he kept raving about how his old Nexus One was just the way I would like it. I would like to have a "plain" version of Android 2.1 on my phone. I have a coworker friend that's a Linux guru that's willing to help. Here's my questions.
Can I take take the Samsung released source for the hardware drivers and compile it with a stock Android 2.1 platform? I'm not asking for step by step. More of a 10,000 foot how to. Is that possible?
Can you leave the CSC and Modem info the same and just install a PDA ROM with Odin? Or would you be overwriting all of that info on the phone?
Thanks and if this has been answered before, please fill free to say "search is your friend" and give me the links...
Click to expand...
Click to collapse
Check out this wiki from cyanogen:
http://wiki.cyanogenmod.com/index.php?title=Main_Page
On the bottom right you will see an advanced section that explains how to build from source code. (aosp)
Good luck!!! It's definitely not for me, not with kids and a full time job!
Good info. I haven't seen a post on people testing out the source code testing and their experience. Can you IM or point me to that?
Thanks!
rajendra82 said:
I think that vanilla Roms are a little further away in the future. First step in the process right now would be for someone to be able to compile a kernel from the Samsung released source code that works. Unfortunately the current Captivate kernel source code, when compiled, causes issues (voices garbled, lag when waking up the phone) that are not present in the stock precompiled kernel. These bugs are apparently not present in the other versions of the source code. Once these initial bugs are ironed out, we can truly start down the path of having custom fixes, and the devs can start to focus on bigger challenges, like making the vanilla Eclair or Froyo Roms to start working with our kernel. Good thing about this phone is that there are going to be so many versions of it, that parallel development is happening on multiple platforms. This will likely produce independent breakthroughs that could be theoretically ported between the platforms, but unfortunately it also slows down the development of each platform due to the quirks that have to be overcome. I hope that, in the future, we get to a place where all the source codes are merged into master repository that has all the necessary improvements and the ability to overcome individual platform quirks, so that the development can proceed more rapidly.
Click to expand...
Click to collapse
Also for clarification, when you bought a Nexus One straight from Google for AT&T, was it considered "Vanilla"? Is the build on that phone just like someone downloaded the source for 2.1 and compiled it with the hardware drivers and that's it? I'm wondering what all comes on a "basic" Andriod ROM straight from the source.
hallfleming said:
Also for clarification, when you bought a Nexus One straight from Google for AT&T, was it considered "Vanilla"? Is the build on that phone just like someone downloaded the source for 2.1 and compiled it with the hardware drivers and that's it? I'm wondering what all comes on a "basic" Andriod ROM straight from the source.
Click to expand...
Click to collapse
Nexus One is as Vanilla as it comes. Just straight up Android! I don't think there is anything added to stock 2.1 or 2.2 on the Nexus.
hallfleming said:
Good info. I haven't seen a post on people testing out the source code testing and their experience. Can you IM or point me to that?
Thanks!
Click to expand...
Click to collapse
Most of the kernel compiling struggles are documented here:
http://forum.xda-developers.com/showthread.php?t=740747
Mimocan himself has started some work on it here:
http://forum.xda-developers.com/showthread.php?t=747040
There are also people having success mixing Vibrant ROM on the Captivate with some GPS crash issues:
http://forum.xda-developers.com/showthread.php?t=746466
I am trying to follow those threads, and since I am not a developer, I can't personally contribute to the process. But it is interesting to me anyway.
I've seen these before. I thought they were just edited versions of ROM's sucked off a existing phone. Are these compiled from scratch?
rajendra82 said:
Most of the kernel compiling struggles are documented here:
http://forum.xda-developers.com/showthread.php?t=740747
Mimocan himself has started some work on it here:
http://forum.xda-developers.com/showthread.php?t=747040
There are also people having success mixing Vibrant ROM on the Captivate with some GPS crash issues:
http://forum.xda-developers.com/showthread.php?t=746466
I am trying to follow those threads, and since I am not a deveoper, I can't personally contribute to the process. But it is interesting to me anyway.
Click to expand...
Click to collapse
hallfleming said:
I've seen these before. I thought they were just edited versions of ROM's sucked off a existing phone. Are these compiled from scratch?
Click to expand...
Click to collapse
The first two are attempts to recompile the kernel to put in the ext3/ext4 mimocan fix. The third one I believe is a script for boot logo animation hack to achieve the same thing.
I forgot to mention one more thread:
http://forum.xda-developers.com/showthread.php?t=739823
So we've got the source code with drivers and know which ones to use from the T959 for fixing the voice issue. We've got the stock kernel. What's left to creat a plain jane captivate?
hallfleming said:
So we've got the source code with drivers and know which ones to use from the T959 for fixing the voice issue. We've got the stock kernel. What's left to creat a plain jane captivate?
Click to expand...
Click to collapse
I'm guessing not too much. There are somethings that would need to be edited such as handling the capacitive buttons. The i9000 roms handle buttons differently regardless of the kernel so, its apparently an OS level config.
I've been wanting to work on this but I've been neck deep in source code from work.
Here is a good how to: http://forum.xda-developers.com/showthread.php?t=704561
Thanks for the link. The US codes out there so we don't need i9000 port
Sent from my SAMSUNG-SGH-I897 using XDA App
hallfleming said:
Thanks for the link. The US codes out there so we don't need i9000 port
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
My point was that given the I9000 rom needs source level changes in order to work as expected(haptic feedback on certain buttons, etc) then running an AOSP build may require some source level changes as well. It may not be as simple as building and flashing.
Hi,
i know that the build would be slow as hell but has anyone compiled ICS for the G1? just for trying it ?
i would like to try it myself but i have no clue on how and from hat i`ve heard my computer would take ages to build it
It's done for droid eris, it can be ported to G1.
http://forum.xda-developers.com/showthread.php?t=1352170
Porting would be inefficient when it can be built from source.
Unfortunately I can't do neither
Sent from my GT-I9100 using XDA App
Ice Cream Sandwich Build Help
As soon as the source was released I was thinking about trying to build it for "old reliable" (my nickname for my old G1). I know it would be slow as mud but I still want to give it a try. Problem is I've never compiled the source of Android before so I would be going in blind. I've read the info at source.android.com so I have somewhere to start. If anyone has any other guides/tutorials on how to build Android for a device then I would be really appreciative. I'm a Computer Science major so don't be afraid to throw a little code at me either. I'll include the details of my phone below in case anyone needs it.
HTC Dream
SPL: HBOOT-1.33.2005 (DangerSPL)
Radio: 2.22.19.261
OS: CyanogenMod 6.1 (Android 2.2.1)
You can have a look at Terry' ezGingerbread thread. Here he explains what to do to compile his ezGingerbread from the sources. Principally compiling ICS is the same, but you need to exchange / modify the manifest to your needs.
Sent from my Gingerbread on Dream using XDA App
Thanks, I looked it up and it was really helpful. Just a couple of quick questions. Do you know how far from stock ezGingerbread is? What do you mean when you say manifest? When people port a new version to a new device how is it normally done?
Thanks for your help. If I manage to get anything useful I'll be sure to share it here first.
Sent from my DROID3 using XDA App
hyperspace290 said:
Thanks, I looked it up and it was really helpful. Just a couple of quick questions. Do you know how far from stock ezGingerbread is? What do you mean when you say manifest? When people port a new version to a new device how is it normally done?
Thanks for your help. If I manage to get anything useful I'll be sure to share it here first.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
It's almost stock, but there are some projects from CM included and some he cloned from CM or from other sites and manages them by himself. Details you can see it in his manifest.xml located in the .repo directory. The manifest defines, what projects are to be included and what branch you want to use for these projects.
You will not want my manifest for ICS (at least unless I make an ICS branch myself)
The reason is you will want to use the ICS git repos and not the GB git repos (original or cloned by me)
That said if you are new to building an android rom look at the structure using ezgb some, and build ezgb, then when you understand the structure clone ICS from aosp (see info on source.android.com) and create your own manifest from that including cloned git repos you need from ezgb with any addtl modifications required.
The first thing is:
* Git is the source control for all parts of android, however many (well over 200) git repos are used in ICS
* Repo is a tool (python script with plugins pulled from its own git repo) for maintaining all of the git repos used in an android build, and creating the true tree of repos needed for the work directoy.
* Manifest is a special git repository with default.xml (and sometimes other manifest xmls) used by the repo script to find all the projects other git repositories, as well as what branch/commit to checkout to the work directory.
Thanks for the advice guys. Glad to see the little G1 is still getting some love. I think I'll start by building ezGingerbread to get the handle on the build process for Android and at least get up to 2.3.
If anyone knows what kinds of modifications are normally needed for a port like this then I would appreciate the help. Is it normally just editing some config files or would I have to dive into the code? Thanks again.
Sent from my DROID3 using XDA App
Looks like someone has beaten me to the punch. Anyone interested shout go have a look at this thread: http://forum.xda-developers.com/showthread.php?p=19648827
not exactly.
that is a port from a source-build for the hero
but very close
looks like the dev is trying to make a source build for the dream.
you could contact him so you can work together
Really get the cm9 source, pull forward the dream/sapphire device trees from cm7 (or firerats port of that) and it ought to be alright.
There seems little in the way of true cm bits at current (sure to change soon) but most of the hardware backwards compatibility patches are alredy in cm9 from the looks of it.. for all I know this is a cm9 build since aosp has no hero device tree out of box.
I was going to reply to that thread but since I'm still considered new I can't post to development threads. I guess I will PM the dev later to let him know I'm interested in helping him out.
Why would you build for another device if the dream has built into AOSP? Doesn't make a whole lot of sense to me unless they flat out took out the board file in ICS but you could easily put it back by pulling it from an earlier revision.
Sent from my DROID3 using XDA App
So everybody knows, I have taken over as one of the Moderators for this forum.
Feel free to PM for questions,
Hit the report button if it's something you think I should take a look at.
Pax
EDIT FROM Moscow Desire,
Pax is now retired from FSM Duties. :crying:
MD
paxChristos said:
So everybody knows, I have taken over as one of the Moderators for this forum.
Feel free to PM for questions,
Hit the report button if it's something you think I should take a look at.
Pax
Click to expand...
Click to collapse
Welcome great job thanks for being a mod;-)
Welcome~!
welcome
http://forum.xda-developers.com/showthread.php?t=1711137
can u look at this thread and see if the thors kernel was ever present if it was fine if not can we get the thread reopened AOKP would be another good option for roms for the tablet.
Timelord83 said:
welcome
http://forum.xda-developers.com/showthread.php?t=1711137
can u look at this thread and see if the thors kernel was ever present if it was fine if not can we get the thread reopened AOKP would be another good option for roms for the tablet.
Click to expand...
Click to collapse
Why not just go get it from rootzwiki if you want it so bad?
bfranklin1986 said:
Why not just go get it from rootzwiki if you want it so bad?
Click to expand...
Click to collapse
I'll stick to XDA. Not everyone on here has social skills to participate in forum discussions but i find that this site has much more information and the groups of people are more eager to help troubleshoot. by unlocking the thread if its not thors kernel it opens it up to ALL of xda to help.
Timelord83 said:
I'll stick to XDA. Not everyone on here has social skills to participate in forum discussions but i find that this site has much more information and the groups of people are more eager to help troubleshoot. by unlocking the thread if its not thors kernel it opens it up to ALL of xda to help.
Click to expand...
Click to collapse
I'm not sure how many actually remember the events relating to this earlier this year... But it was a mess.
Thor decided to start developing a ICS rom providing (presumably under apache2) the device/vender tree to the build. Just two little tidbits were, how to say, off with his approach.
a) The device tree included his kernel still without the source code (so now we have some apache2 code.. nice but not required, and its poisoned with a closed source kernel)
b) he provided links to the github repo (now deleted and/or hidden) on XDA via adfly.
After this was reported, XDA closed the thread, Thor took down the git repo and tried to pan this off to his greater followers (probably successfully) as XDA not even allowing him in when him to work here even when his code is "open".
--
While the source was open blazingwolf, ProTekk, randomblame (and some others?) managed to get the repo and clone it (or parts of it) into their own projects.. Mostly with little or no credit, and not always properly removing all traces of Thors kernel (either the main kernel was replaced with blazingwolfs open kernel, but a second copy of Thors kernel in the repo was left, or they just used thors kernel as it existed in the device tree).
In addition to this there was a recovery that used blazingwolf's kernel but otherwise was a nearly unmodified thor recovery binary (simply a hex edit to change the title, and thus hide the upstream source)
--
AOKP is now using the CM9 base for the device and vender trees, so everything including the CM9 T20 kernel is open source. However I its up to the AOKP team to re-post here at this point and not someone just wanting a mirror with their own unrelated donate link.
Some locked threads to remember in relationship to this:
http://forum.xda-developers.com/showthread.php?t=1353252 - ProTekk bit of ICS locked
http://forum.xda-developers.com/showthread.php?t=1426617 - randomblame recovery - locked
http://forum.xda-developers.com/showthread.php?t=1524919 - original A500 AOPK thread - locked
Just to clear this up, roms are under Apache v2 license (which doesn't require source release) kernels are under GPL which does require source release.
Sent from my R800x using Tapatalk 2
ezterry said:
I'm not sure how many actually remember the events relating to this earlier this year... But it was a mess.
Thor decided to start developing a ICS rom providing (presumably under apache2) the device/vender tree to the build. Just two little tidbits were, how to say, off with his approach.
a) The device tree included his kernel still without the source code (so now we have some apache2 code.. nice but not required, and its poisoned with a closed source kernel)
b) he provided links to the github repo (now deleted and/or hidden) on XDA via adfly.
After this was reported, XDA closed the thread, Thor took down the git repo and tried to pan this off to his greater followers (probably successfully) as XDA not even allowing him in when him to work here even when his code is "open".
--
While the source was open blazingwolf, ProTekk, randomblame (and some others?) managed to get the repo and clone it (or parts of it) into their own projects.. Mostly with little or no credit, and not always properly removing all traces of Thors kernel (either the main kernel was replaced with blazingwolfs open kernel, but a second copy of Thors kernel in the repo was left, or they just used thors kernel as it existed in the device tree).
In addition to this there was a recovery that used blazingwolf's kernel but otherwise was a nearly unmodified thor recovery binary (simply a hex edit to change the title, and thus hide the upstream source)
--
AOKP is now using the CM9 base for the device and vender trees, so everything including the CM9 T20 kernel is open source. However I its up to the AOKP team to re-post here at this point and not someone just wanting a mirror with their own unrelated donate link.
Some locked threads to remember in relationship to this:
http://forum.xda-developers.com/showthread.php?t=1353252 - ProTekk bit of ICS locked
http://forum.xda-developers.com/showthread.php?t=1426617 - randomblame recovery - locked
http://forum.xda-developers.com/showthread.php?t=1524919 - original A500 AOPK thread - locked
Click to expand...
Click to collapse
sadly i do but the thread i linked is albeit messy with side stuff i made the assumption it was mod locked. after talking with the other people i have foudn out that the OP requested it be locked. i went and got the rom from AOKP website and as far as i can tell is Thor free and i run clockwork recovery and V8 ICS bootloader.
As for the motives for my request is i'd like to see more roms succeed for this tablet as it is "old" tech people are moving to the tegra 3 Tabs i am not ready to give up on my $567.87 less than year old purchase. I own the A501 ATT 4G LTE Variant i bought it from ATT without contract hence the price
Uhm... Hi paxChristos! Welcome to our slightly disfunctional family! I hope that you have a great time.:silly:
Timelord83 said:
As for the motives for my request is i'd like to see more roms succeed for this tablet as it is "old" tech people are moving to the tegra 3 Tabs i am not ready to give up on my $567.87 less than year old purchase. I own the A501 ATT 4G LTE Variant i bought it from ATT without contract hence the price
Click to expand...
Click to collapse
As do we all (want larger choices in roms).
But there-in lies the issue. We have an AOKP rom that has been through many hands, and at times, had some suspicious coding involved. Including getting closed on more than 1 occassion due to shady practices and non-GPL kernels. Might have been 3 seperate roms for all we know.
To post the rom now, would probably piss off quite a few people if enough credits were not given, even if the kernel proved to be legit. And even then, you would have several people claiming the rom was theirs and they were the original authors. That's the nature of these "KANG" roms and "MIUI" roms.
Well, we have polluted PaxChristo's welcome thread enough for now. I suggest we give it a rest, and probably open a new thread in the General Forum. I'll DL and install it, and see what's up with it. Post some results later.
MD
good job
paxChristos said:
So everybody knows, I have taken over as one of the Moderators for this forum.
Feel free to PM for questions,
Hit the report button if it's something you think I should take a look at.
Pax
Click to expand...
Click to collapse
t my a500wondering where to post question about how to root my tab. Sadly it is running 3.2 honey and I am very confused as what to do to get it rooted. I am in southern Louisiana, maybe there are folks close to me that could help.
Thanks everyone don
Hey thanks for being a mod' it is a lot of work I know. Listen I am knew as I just go
I am trying to build an image for angler. Looking for make files to build the image for angler (Nexus 6P) Where can i find the vendor/make files to build the image.
How do I see the angler option when I do lunch?
Do a quick search on Github, it should have everything you need.
Thanks for the reply. I looked at the git hub. But I saw so may files. Not sure, which files I need to make the build.
debby_8 said:
Thanks for the reply. I looked at the git hub. But I saw so may files. Not sure, which files I need to make the build.
Click to expand...
Click to collapse
Trying to build the kernel myself, would also appreciate some info. Samsung always at least always includes some help file to specify the toolchain needed etc.
to build angler you need all the device files from android_devie_huawei_angler im fairly sure. Iv gotten my new handset and been working with a guy whos helped me to get a booting port of Omni Rom up and running other than that im not sure exactly how to help.
if your trying to build a image you surely know what files you need to use?
mehmehmen said:
to build angler you need all the device files from android_devie_huawei_angler im fairly sure. Iv gotten my new handset and been working with a guy whos helped me to get a booting port of Omni Rom up and running other than that im not sure exactly how to help.
if your trying to build a image you surely know what files you need to use?
Click to expand...
Click to collapse
Well in my case, at this point I just want to build the kernel. It's really too bad that XDA doesnt accept posts like this on their 'development' forum. On this general FAQ forum I dont think it reaches the right audience and hence no reponse from anybody yet, to this fairly simple question. I wish XDA would support developers a bit more and would allow development questions on the development forum.
I understand what you mean, although the development forums used to get INUNDATED with questions similar to these which would usually be able to be remedied with a bit of googling and a decent amount of reading. I think you would find if you were to go to the actual angler kernel threads and be very concise and polite in asking for any help that someone would actually be happy to help at least a little bit.
You have to remember on the dev forums most people are kind of in the know of what they want to do and roughly how to do it hence why they prefer posts to remain within the realms of people contributing to thread projects and giving test feedback as opposed to asking for help on seperate (although maybe related) issues.
Im currently working on the angler with a couple of guys and we have a booting fully operational OmniRom port in testing stages now, which may end up to me then posting that as a full [ROM] thread and trying to offer support on the device for that rom. The guy that built the rom himself is very good and has helped me understand a lot, with the right attitude and willingness to learn I am sure you would be welcome in the IRC channel where I personally would be happy to try and help you get your head round some things, as the next goal for me regarding the 6p in terms of our project is going to be kernel based compiling as i want to try and get a really robust kernel built now we have a seemingly stable feature full rom built and booting.
Feel free to message me if this sounds like it may be of some help
Regards
Meh
mehmehmen said:
although the development forums used to get INUNDATED with questions similar to these which would usually be able to be remedied with a bit of googling and a decent amount of reading.
Click to expand...
Click to collapse
That happens on any forum.
I think you would find if you were to go to the actual angler kernel threads and be very concise and polite in asking for any help that someone would actually be happy to help at least a little bit.
Click to expand...
Click to collapse
Sure but that would be going off topic on someone's thread.
You have to remember on the dev forums most people are kind of in the know of what they want to do and roughly how to do it hence why they prefer posts to remain within the realms of people contributing to thread projects and giving test feedback as opposed to asking for help on seperate (although maybe related) issues.
Click to expand...
Click to collapse
Everybody has questions, regardless of their level. I was the maintainer for Cyanogenmod Note 4, so if the above would be true, I wouldnt be here I'm sure I can figure out myself how to get the Angler kernel compiling but it would save me, and others who will try the same in the future, quite a bit of trouble if someone who had done it would just post the used toolchain etc.
Anyway you used a lot of words without helping at all. That's exactly my point, when posting on a general forum you can expect these kind of replies. That's why I'd love to see a true development forum here on XDA, not just a 'developer' forum where people just support their projects. Giving support to a project, has not much to do with development.
Nah, I could have expected this. I'll figure it out myself. Thanks but no thanks.
*EDIT* I guess this will work, using toolchain 4.6 like they recommend, it's probably the latest anyway (?)
https://source.android.com/source/building-kernels.html
They dont mention Angler, but I'll try this anyway, I think it might work. And I'll let people know if it worked or not, so someone in the future who reads this thread will know how too. Although I kinda doubt a developer will search the general FAQ forum here ...
Might wanna try asking that on a kernel development thread in Dev section - kernel developers are usually friendly to people willing to rightfully use (and maybe improve) their work. They should be at least give you a vision on how go get the basic Angler kernel up and running.
As for me... I build CM, everything on the CM wiki is mostly enough for me.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
Use googles 4.9 aarch64 toolchain for kernel to start off. Any questions feel free to hit me up, better on hangouts though as I forget about XDA sometimes ha. Pm me for email.
rustyjay said:
Use googles 4.9 aarch64 toolchain for kernel to start off. Any questions feel free to hit me up, better on hangouts though as I forget about XDA sometimes ha. Pm me for email.
Click to expand...
Click to collapse
Thanks mate ! That's what I was looking for, will try that one.
---------- Post added at 03:23 AM ---------- Previous post was at 03:03 AM ----------
Ok and it's building !
Steps I took:
1) Download angler kernel here: https://android.googlesource.com/kernel/msm/+/android-msm-angler-3.10-marshmallow-dr
2) Download toolchain with: git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9
3) add the toolchain to the path, in my case: export PATH=~/android/toolchains/aarch64-linux-android-4.9/bin:$PATH
4) go to the unpacked kernel dir
5) export ARCH=arm64
6) export SUBARCH=arm64
7) export CROSS_COMPILE=aarch64-linux-android-
8) make angler_defconfig
9) make
Thanks again @rustyjay for the toolchain info !
---------- Post added at 03:32 AM ---------- Previous post was at 03:23 AM ----------
AndyYan said:
As for me... I build CM, everything on the CM wiki is mostly enough for me.
Click to expand...
Click to collapse
As much as I love CM (I was maintainer for the Note 4), I don't particularly see the point of running it on a Nexus device. I just want some kernel tweaks (for example that damn fuel gauge is giving me wakelocks), so I think l wont jump onto CM. But who knows ...
---------- Post added at 03:46 AM ---------- Previous post was at 03:32 AM ----------
Build completed So I guess I just insert the resulting Image.gz-dtb into the boot.img (with android image kitchen for example), right ? Will try tomorrow, but I think that should work. off to bed now ...
Yeah what it basically does when I build aosp, don't know too much about kitchen.
rustyjay said:
Yeah what it basically does when I build aosp, don't know too much about kitchen.
Click to expand...
Click to collapse
Ok I used android image kitchen to replace the Zimage, flashed it and ... it boots
Cool, so that's easy. Now for the next part: building the whole rom ! Any idea on how to do that ? Or where to even download the code ? Is there even a whole ROM to build, including the blobs etc ? I think i saw google releasing a device tree but not the whole ROM, right ? I must say I havent really googled myself this, will look into this today myself too.
*EDIT* yeah here's the device tree: https://android.googlesource.com/device/huawei/angler/ but I dont think it's the whole ROM, going to download it now ...
*EDIT2* No this definitely isnt the whole ROM,not even the device tree There's not a lot in there !?!
*EDIT3* Info here: https://source.android.com/source/running.html
*EDIT4* So as per the link above, it turns out that most drivers are blobs ! Hmm that's a bit disappointing. You buy a Nexus because supposedly it's 'open source', turns out most of it is not.... Anyway so it seems it's just a matter of compiling the sourcecode that IS there and then adding the blobs.
*EDIT5* So this section explains the whole process of setting up the environment, downloading, syncing and building: https://source.android.com/source/requirements.html looks very similar to the CM install/build process indeed !
To me its easier than cm but aosp is what I do the most. And to build for aosp you'll need angler device tree and vendor blobs. Ive been using the huawei vendor from pure nexus github.
Aosp out of the box is really unfinished though to me so it takes some work with cherry picks to get everything slick.
rustyjay said:
To me its easier than cm but aosp is what I do the most. And to build for aosp you'll need angler device tree and vendor blobs. Ive been using the huawei vendor from pure nexus github.
Aosp out of the box is really unfinished though to me so it takes some work with cherry picks to get everything slick.
Click to expand...
Click to collapse
Thanks for all your info, much appreciated. Currently syncing to AOSP like explained on that page I linked, will take a few hours I guess.
BTW, what are you exactly building this for ? Just some tweaks ? I saw this kernel wakelock qpnp_fg myself, I just disabled CONFIG_QPNP_FG=y in the defconfig, the wakelock is gone but like I expected, the battery gauge doesnt work anymore neither, lol. Will need to look into it for a real fix I guess.
Also I'm planning to make an option to default MTP as USB connection. It's just plain crazy Google left that out in 6.0 !
I've been building for myself for like 2 years now, kernels I just started really messing with about 6 months ago. I just had a hard time finding a ROM with stuff I like and not a million other mods added to it. Now its just hard for me to stay on stock or a ROM I didn't cook up.
rustyjay said:
I've been building for myself for like 2 years now, kernels I just started really messing with about 6 months ago. I just had a hard time finding a ROM with stuff I like and not a million other mods added to it. Now its just hard for me to stay on stock or a ROM I didn't cook up.
Click to expand...
Click to collapse
It's my first Nexus and am just loving it already. I mean, getting CM to run on a Samsung device is of course fun, but it's also just SO much work. I dont think I could do it all over again on another non AOSP device.
Now on nexus, just syncing directly from google and building it, what a breeze this is !
Oh yeah if your into building, nexus is really the only way to go. My first nexus was the ns in '10 and have had a nexus phone ever since
OK, so I don't know anyone else with a 6p but want a second opinion on my rom/kernel so far. I do not want to start and maintain a thread, why I'm posting this here.
https://drive.google.com/file/d/0B_f86wvdx8LKUm12NHpxSVBhVEk/view
Its not a kitchen sink rom, if there's interest I'll make a changelog with the proper credits to people and probably upload builds to my drive.
rustyjay said:
OK, so I don't know anyone else with a 6p but want a second opinion on my rom/kernel so far. I do not want to start and maintain a thread, why I'm posting this here.
https://drive.google.com/file/d/0B_f86wvdx8LKUm12NHpxSVBhVEk/view
Its not a kitchen sink rom, if there's interest I'll make a changelog with the proper credits to people and probably upload builds to my drive.
Click to expand...
Click to collapse
What are your main changes ?
Anyway I just finished building the ROM myself. It ends up with system.img, userdata.img, recover.img, ramdisk.img, ramdisk-recover.img. I'd probably just flash boot.img and system.img, right ? That userdata.img, what is that exactly anyway ? If I flash that I'll lose my user partition=installed apps, I guess ?
BTW I didnt pull any blobs so I guess it wont run anyway. I guess I first need to extract the blobs ? Does the AOSP build process include the blobs automatically ?
Thanks !
So I recently got into compiling ROMs from source. CM12.1 specifically. Thanks to cm's wiki page I managed to get a full unofficial build of cm12.1 zipped up.
But I don't want just stock cm12.1 I'd like to add custom features. Some of these features are from PAC rom and some from aokp. Some are from aicp rom.
Basically, I'm sick of ROMs having either too much or not enough, so I'd like to pick and chose exactly what initially gets installed.
The only problem I am having is that there aren't that many guides for extracting features from other ROMs, unless I am overlooking them.
Please help by pointing me in the right direction... An xda guide, a YouTube video, anything. Remember, I can already sync and compile. I'm just looking for help grabbing / cherry picking certain features.
caesar_ said:
So I recently got into compiling ROMs from source. CM12.1 specifically. Thanks to cm's wiki page I managed to get a full unofficial build of cm12.1 zipped up.
But I don't want just stock cm12.1 I'd like to add custom features. Some of these features are from PAC rom and some from aokp. Some are from aicp rom.
Basically, I'm sick of ROMs having either too much or not enough, so I'd like to pick and chose exactly what initially gets installed.
The only problem I am having is that there aren't that many guides for extracting features from other ROMs, unless I am overlooking them.
Please help by pointing me in the right direction... An xda guide, a YouTube video, anything. Remember, I can already sync and compile. I'm just looking for help grabbing / cherry picking certain features.
Click to expand...
Click to collapse
Typically, you would cherry-pick an addition to android_frameworks_base and android_apps_packages_Settings.
If you are just starting out, you will want to have a look at general guides on github and git in general.
For android-specific stuff, it's a good idea to see how cm-based ROMs, like temasek, CM-remix and Resurrection Remix add features, and then copy the ones you like.
After you get the hang of it, it's quite straigth-forward and fun.
I've been doing what you want to do since 4.2, and it's been a blast.
Feel free to PM me if you have any specific questions on how to include specific features.
Sent using XDA One
jisoo said:
Typically, you would cherry-pick an addition to android_frameworks_base and android_apps_packages_Settings.
If you are just starting out, you will want to have a look at general guides on github and git in general.
For android-specific stuff, it's a good idea to see how cm-based ROMs, like temasek, CM-remix and Resurrection Remix add features, and then copy the ones you like.
After you get the hang of it, it's quite straigth-forward and fun.
I've been doing what you want to do since 4.2, and it's been a blast.
Feel free to PM me if you have any specific questions on how to include specific features.
Sent using XDA One
Click to expand...
Click to collapse
Hey thanks for the response and your willingness to help.
Let me do some more research on git before I ask questions.