Database Users

Source code building a vanilla ROM

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.

[NEWS] My new kernel can run in stock 3.1 ROM finally

Hi all,
I am so excited now, can't wait to tell all you guys that news
Maybe someone know that I have upgraded our kernel to the newest kernel tree from nvidia's git and waiting for it to be stable for daily use. However, I found it can't boot in the newest ACER's stock ROM yesterday. After one full day hack, it finally can boot in the stock ROM now.
However, the last function I can't confirm is HDMI support, so I want some volunteers to test HDMI support and the stability. If you use vache's Taboonay 0.9.x and are interested in it, please PM me
Thanks

I can test the stability, but not the HDMI output.
P.S : Nice to see you here roggin

I can test hdmi, only 720p, but at least I can verify that.

roggin said:
Hi all,
I am so excited now, can't wait to tell all you guys that news
Maybe someone know that I have upgraded our kernel to the newest kernel tree from nvidia's git and waiting for it to be stable for daily use. However, I found it can't boot in the newest ACER's stock ROM yesterday. After one full day hack, it finally can boot in the stock ROM now.
However, the last function I can't confirm is HDMI support, so I want some volunteers to test HDMI support and the stability. If you use vache's Taboonay 0.9.x and are interested in it, please PM me
Thanks
Click to expand...
Click to collapse
What kernel is it? If I may ask.
Can it OC?

Johnny0906 said:
What kernel is it? If I may ask.
Can it OC?
Click to expand...
Click to collapse
Nvidia's kernel is the ORIGINAL kernel, all others base their continued work on, so Acer use these updates as reference..

Can you check up on the bluetooth issue on this kernel you make..
I know tiamat/xoom kernel is really close to stock nvidia kernel too (or fully supported with drivers). so maybe something dirty needs changing..
havent had chance to fix..
problem for now, seems to be it can scan, but seems to timeout on transmitting, so it suddenly cannot see new units after some minutes. maybe worth doublechecking.

vache said:
I can test the stability, but not the HDMI output.
P.S : Nice to see you here roggin
Click to expand...
Click to collapse
Hi vache,
Coooool, it's so nice to see you here
I have pm you the link, please take it a try
Thanks for your help again

Johnny0906 said:
What kernel is it? If I may ask.
Can it OC?
Click to expand...
Click to collapse
sorry, I haven't added OC code in it, but I will add it when it stable enough
Thanks

Dexter_nlb said:
Can you check up on the bluetooth issue on this kernel you make..
I know tiamat/xoom kernel is really close to stock nvidia kernel too (or fully supported with drivers). so maybe something dirty needs changing..
havent had chance to fix..
problem for now, seems to be it can scan, but seems to timeout on transmitting, so it suddenly cannot see new units after some minutes. maybe worth doublechecking.
Click to expand...
Click to collapse
Hi Dexter_nlb:
I have tested the bluetooth function in this kernel, it works fine in my kernel
If you are interested in it, I can mail or share a link of my kernel source for you
Thanks

roggin said:
However, the last function I can't confirm is HDMI support, so I want some volunteers to test HDMI support and the stability. If you use vache's Taboonay 0.9.x and are interested in it, please PM me
Click to expand...
Click to collapse
Hi Roggin,
I play with versions and can test HDMI 1080P with Taboonay 0.9.1. Please send me the link to kernel. Do you make also modules, especialy for 3G?

roggin said:
Hi Dexter_nlb:
I have tested the bluetooth function in this kernel, it works fine in my kernel
If you are interested in it, I can mail or share a link of my kernel source for you
Thanks
Click to expand...
Click to collapse
please do i would love to play around with it "internally" and testing...
im little occupied atm, so hdmi can be tested, and regular use for now..
I can probably make you the oc add-ons and see how it turns out with your work and send you my diff back.. (don't know git commit)

I would be willing to due some stability testing with the acer stock rom.
Let me know.

Dexter_nlb said:
please do i would love to play around with it "internally" and testing...
im little occupied atm, so hdmi can be tested, and regular use for now..
I can probably make you the oc add-ons and see how it turns out with your work and send you my diff back.. (don't know git commit)
Click to expand...
Click to collapse
Hi Dexter_nlb,
It's a big big help that you can help me ,
I am not releasing kernel source is because I don't want to brick someone's tablet, but It's ok for power developer like you.
I am uploading the kernel, I will info you when uploading done
Thanks for your help

snickle said:
I would be willing to due some stability testing with the acer stock rom.
Let me know.
Click to expand...
Click to collapse
Hi snickle,
I think it's fine using Taboonay's ramdisk in stock rom, but not sure
If you can help me for test, I will pm the link for you
Thanks

roggin said:
I am not releasing kernel source is because I don't want to brick someone's tablet
Click to expand...
Click to collapse
If they know how to compile it, then I guess they can enjoy their brick
Just be careful not releasing the source code, as it is under a open licence. I'm pretty sure that's why thor2002ro's kernel thread was deleted by moderators off fo this forum. I don't want to see another Kernel development go south because it wasn't public .

roggin said:
Hi snickle,
I think it's fine using Taboonay's ramdisk in stock rom, but not sure
If you can help me for test, I will pm the link for you
Thanks
Click to expand...
Click to collapse
I think the usage of ramdisk should be optional, because it might not allow to encrypt your device, and as you hopefully know, encryption is necessary to allow exchange activesync connection for email push, except if somebody finds out a what has to be modified to use activesync without encryption.
I also join ShadowXVII concerning the kernel source, if somebody wants to brick his device, it's up to him, but be carefull not to get removed because you did not publish the source.
otherwise well done my friend.

zoubidou said:
I also join ShadowXVII concerning the kernel source, if somebody wants to brick his device, it's up to him, but be carefull not to get removed because you did not publish the source.
Click to expand...
Click to collapse
You only have to publicly release the source if you publicly release the binary - he's only obliged to give the source to the people he gave the binary to. So there's no problems
On that note: I've just flashed Taboonay and am happy to give your kernel a try. I don't have a dev environment set up these days, but if you can send me the boot.img I'll take a crack at it.

themono said:
You only have to publicly release the source if you publicly release the binary - he's only obliged to give the source to the people he gave the binary to. So there's no problems
Click to expand...
Click to collapse
Cool, thanks for the clarification. Just being cautious as I'd prefer Kernel development wasn't hindered at all. That being said, a public source may promote development as opposed to ending up with several different kernels by different developers. I'm all for collaboration, and it's great to see some within this thread
On a side note, any Kernel developers that may be able to shed some light onto this thread would be appreciated -- in particular, the kernel requirements for networking over USB; http://forum.xda-developers.com/showthread.php?p=15452414#post15452414

Hi all,
It's not I don't want to release it. It's almost 300+ patches between older and newer version, and include some regulator voltage patch. I want to sure not damage any part in all functions.
Give me one more days, when I collect all necessary response from tester, I will release it
Thanks

I did exactly the same on the tiamat kernel, waited and hoped to had time debugging the bluetooth issue, but got modarator complaints on not publicing any source
anyways, as long as no binary appear in this thread, i think you're safe from any mods attacking you on GPL issues (or do like thor200ro move it offsite, if you feel like breaking GPL)
Talk is just talk for now, no mods can argue against that for now..

Lollipop - OPO - Pure Aosp 5.0 - Test Build only -16/11/14

This is a pure AOSP 5.0 - Lollipop - build compiled from source .
I would highly recommend it to be used only by developers and advanced users.
The build just completed and am uploading the image files for you to do whatever you please.
The idea is to get it out there so others can take a look and use it to make it better.
Please give your comments and updates if you do plan to use it on your device.
ADVISORY -
First build -likely to be highly unstable.
I am not responsible for any damages caused whatsoever.
This is for test purposes only, however it should work well.
Link to Images -
https://www.mediafire.com/folder/c3mcyxash8z8y63,mx64j9929bp1zpw,nu1blqbnpu2siwe/shared
Credits - To clarify confusions
Team EOS - for device tree
Slim and Omni - for kernel.
Cyanogenmod - some common stuff.
Regards

Nice thanks can't wait to try it out much alohas

Which cm commits is it up to?

poczynek said:
Which cm commits is it up to?
Click to expand...
Click to collapse
Latest available

navendugoyal said:
Latest available
Click to expand...
Click to collapse
So its not AOSP.

keith.mcintyre26 said:
So its not AOSP.
Click to expand...
Click to collapse
Yes it is.
Just the Board changes to get everything working.
No CM source.

navendugoyal said:
I am out of town for next 24 hrs.. therefore can't provide too much hours into it as of now. Will await all of your responses.
Click to expand...
Click to collapse
have you tested it?

synergeticink said:
have you tested it?
Click to expand...
Click to collapse
testing

navendugoyal said:
testing
Click to expand...
Click to collapse
Images uploaded

navendugoyal said:
testing
Click to expand...
Click to collapse
Have you tested it? In all the builds I've worked on the hwcomposer library wasn't getting compiled, leading to display not working, although everything else is(I think). Although @Aaahh probably fixed it just now. Compiling though.
If it boots, mind telling me the things you changed?

lolzballs said:
Have you tested it? In all the builds I've worked on the hwcomposer library wasn't getting compiled, leading to display not working, although everything else is(I think). Although @Aaahh probably fixed it just now. Compiling though.
If it boots, mind telling me the things you changed?
Click to expand...
Click to collapse
Good work you guys.
I didn't have a problem with hardware composer.
The only issue i had was to get the kernel to compile inline.
so i compiled it separately and used the zimage as a prebuilt.
Not booting at the moment

Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon

No boot confirmed, stays on 1+ screen, and fastboot works from that screen as well.

Can people start testing their builds to see that it actually boots before making threads and sharing it with the community?
This is the second time in one day that this has happened.

Yeah that's building 101...don't make a thread until it boots :-/ smh

All the things wrong with this thread:
makes a thread without testing it.
Runs away for a day saying out of town.

2551990 said:
All the things wrong with this thread:
makes a thread without testing it.
Runs away for a day saying out of town.
Click to expand...
Click to collapse
Ok Now
It has taken very hard work to reach here and even get the rom to compile.
There are CM based roms already available which boot and work .
The purpose of posting this thread is to share my work so far on an AOSP build. The idea is, if I am missing something, someone else can pick it up and better it.
If someone still thinks it is a wrong idea, please delete this thread.
Happy for that, no worries.

navendugoyal said:
Ok Now
It has taken very hard work to reach here and even get the rom to compile.
There are CM based roms already available which boot and work .
The purpose of posting this thread is to share my work so far on an AOSP build. The idea is, if I am missing something, someone else can pick it up and better it.
If someone still thinks it is a wrong idea, please delete this thread.
Happy for that, no worries.
Click to expand...
Click to collapse
There's certainly no need to remove the thread. It's labelled appropriately as a test build, and this is what XDA is all about the core, this is development. Keep up the good work.
Transmitted via Bacon

timmaaa said:
There's certainly no need to remove the thread. It's labelled appropriately as a test build, and this is what XDA is all about the core, this is development. Keep up the good work.
Transmitted via Bacon
Click to expand...
Click to collapse
This AOSP rom is the work of Aaaah and lolbzballs so all credit should be given to them in the first post.
https://forums.oneplus.net/threads/development-lollipop.154589/page-305#post-7446071

daleski75 said:
This AOSP rom is the work of Aaaah and lolbzballs so all credit should be given to them in the first post.
https://forums.oneplus.net/threads/development-lollipop.154589/page-305#post-7446071
Click to expand...
Click to collapse
They are working totally different from what I am working upon.
It has nothing from their project.
Regards

How to make angler build

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 !

[Q] when we get android 8 for our nexus 4?

hi friends,
do you know, our nexus 4s get android Oreo by nitrogen or lineage or other roms? if yes, I know stable android Oreo version will release mid august, when we get custom rom?

we can't know this

When it comes fyi: asking for an ETA is kinda rude on xda
wait till October or November probably for a decently stable ROM

Excitedly expect first android Oreo Rom for nexus 4 on september 17

and first 32bit snapdragon android oreo port, fully work
https://forum.xda-developers.com/showpost.php?p=73494285&postcount=1356
so, now we have very big chance for our nexus 4...

and first nexus 5 android oreo port, booting and wifi working now, one similiar devices too
https://forum.xda-developers.com/showpost.php?p=73538437&postcount=6286

for now has boot problem but after all the first nexus 4 oreo
https://forum.xda-developers.com/showpost.php?p=73594437&postcount=231

I have compiled android 8 and I managed to get it booting(lots of changes on kernel and device tree). Need a lot of work but mako probably will get a fully fuctional android 8 rom.

good news
thanks for good news,
and maybe co-operation accelerates this work
equlog said:
I have compiled android 8 and I managed to get it booting(lots of changes on kernel and device tree). Need a lot of work but mako probably will get a fully fuctional android 8 rom.
Click to expand...
Click to collapse

If anyone wants to try Oreo in our lovely mako.
Original thread: Android 8.0 Mako
Download: here

equlog said:
If anyone wants to try Oreo in our lovely mako.
Original thread: Android 8.0 Mako
Download: here
Click to expand...
Click to collapse
Nice! At work and don't have my N4 to try it, but interested to hear how it is running, so I can try out when I get home. Is it mostly functional?

Can you share the device and kernel tree?

equlog said:
I have compiled android 8 and I managed to get it booting(lots of changes on kernel and device tree). Need a lot of work but mako probably will get a fully fuctional android 8 rom.
Click to expand...
Click to collapse
Just for my own curiosity, how do you know what changes need to be made to the device and kernel tree? Do you use officially supported device/kernel trees as a reference, or is there a guideline posted somewhere?

ariesgodofwar said:
Nice! At work and don't have my N4 to try it, but interested to hear how it is running, so I can try out when I get home. Is it mostly functional?
Click to expand...
Click to collapse
Really I haven't tested too much, busy at work... also my n4 have the touch screen broken and doesn't works very good lol.. but almost nothing works.
Its just to try out.
Renandelfanti said:
Can you share the device and kernel tree?
Click to expand...
Click to collapse
Sure, i'll upload to github later.
TheSt33v said:
Just for my own curiosity, how do you know what changes need to be made to the device and kernel tree? Do you use officially supported device/kernel trees as a reference, or is there a guideline posted somewhere?
Click to expand...
Click to collapse
The kernel is the used one in 7.1.2 and I added the Binder changes... the device tree is fixed by trying to booting and fixing the errors showed in last_kmsg .

equlog said:
Really I haven't tested too much, busy at work... also my n4 have the touch screen broken and doesn't works very good lol.. but almost nothing works.
Its just to try out.
Sure, i'll upload to github later.
The kernel is the used one in 7.1.2 and I added the Binder changes... the device tree is fixed by trying to booting and fixing the errors showed in last_kmsg .
Click to expand...
Click to collapse
Yes, I also flashed this and it boots. As you said, nothing works... But it is not less that it boots :laugh:
I've been trying since the source of O is released and could not boot it. Your work gives all mako users hope to see a working O build :good: Thanks for the work!
Nitin

I as well got a semi-working O build, but was a bit short on time to work on it. Could we collaborate somewhere? Perhaps a hangouts group?

I've flashed from mako 7.12, kind of like upgrade from 7.12

Sources up.
I used the vendor blobs from TheMuppets.
https://github.com/MakOreo
---------- Post added at 01:42 AM ---------- Previous post was at 01:24 AM ----------
Ziyan said:
I as well got a semi-working O build, but was a bit short on time to work on it. Could we collaborate somewhere? Perhaps a hangouts group?
Click to expand...
Click to collapse
:good:
I dont have too much free time, but I always follow the status of my devices. I Hope to see a fully working O rom asap.

Ziyan said:
I as well got a semi-working O build, but was a bit short on time to work on it. Could we collaborate somewhere? Perhaps a hangouts group?
Click to expand...
Click to collapse
That's a good idea... What do you say @equlog?
Thanks a lot for sharing the sources :good:
Nitin

as good as we hoped