Related
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..
Hi there,
I'm trying to build some froyo rom for g1 from source. The problem is that lot of stuff lying here is old, unusable slow or hopelessly broken. The only rom that seems to work is hxxp://forum.xda-developers.com/showthread.php?t=1273549
[Rom][2.2.3 AOSP] DREAMteam Froyo v2.0.0 [9/3/2012]
The kernel source can be easy found by Ezterry
hxxps://github.com/ezterry/kernel-biff-testing/tree/ezgb-2636-v1.5.2-20111106
but I can't find any (git) repo or hint how the "DREAMteam" guys built it. :crying:
Thanks in advance for any hints,
ptau
pm the devs
Sent from my HTC Vision using xda premium
All you need for building the kernel is here at this url:
https://github.com/ezterry/manifest-gingerbread-DS/blob/gingerbread/README.mkdn
It used to be on the ezgingerbread rom thread but seems he has a link to the guide which is now on github ^_^
Sent from my GT-I9300 using xda app-developers app
xillius200 said:
All you need for building the kernel is here at this url:
https://github.com/ezterry/manifest-gingerbread-DS/blob/gingerbread/README.mkdn
It used to be on the ezgingerbread rom thread but seems he has a link to the guide which is now on github ^_^
Click to expand...
Click to collapse
Building the kernel for froyo or building the ezgingerbread rom is no problem:
http://forum.xda-developers.com/showthread.php?t=882356
Unfortunately (Ez)gingerbread is an overkill for the tiny G1
My problem is to find out how to build a froyo rom that is not
broken (e.g. cm6). The DREAMteam's
http://forum.xda-developers.com/showthread.php?t=1273549
rom seems to have the most bugs fixed, but again I don't know
how to build it. I need the right android manifest, git repo, etc.
The DREAMteam changelog is astonishingly sparse:
V2.0.0 - 2012-03-09
Update to android 2.2.3. Some changes from 1.9.2 included.
Thanks ptau
ptau said:
Building the kernel for froyo or building the ezgingerbread rom is no problem:
http://forum.xda-developers.com/showthread.php?t=882356
Unfortunately (Ez)gingerbread is an overkill for the tiny G1
My problem is to find out how to build a froyo rom that is not
broken (e.g. cm6). The DREAMteam's
http://forum.xda-developers.com/showthread.php?t=1273549
rom seems to have the most bugs fixed, but again I don't know
how to build it. I need the right android manifest, git repo, etc.
The DREAMteam changelog is astonishingly sparse:
V2.0.0 - 2012-03-09
Update to android 2.2.3. Some changes from 1.9.2 included.
Thanks ptau
Click to expand...
Click to collapse
Well I got in touch with tval aint spoke to him for a while. He said a repo was never made for DREAMteam froyo and the way in which it was created some by pushing files not everything was coding, there was not much point in a repo and he has not got around to it lol and I totally agree with him. So best thing would be to compile a rom from plain AOSP and begin to modify it yourself, this way you learn and better understand rom creation. Plus doing it straight from AOSP will give you the updates you want and in most ways will actually be better ^^ If you want any help I could always introduce you to a few devs see if they would be willing to help ^^
PS: From how you worded your first post it sounded like you were trying to compile just the ezterry kernel xD so I apologise that I misunderstood ^^
99%
xillius200 said:
As far as I remember when it was first started they never had a repository and unless it has changed they still do not lol ill email tvall later lol seems Ldrifta is gone.... :'( if not you can always just compile a normal aosp and then customize it to your liking and speed helps you learn on how to speed up roms that way unlike having an already fast rom of which you learn less from.
Click to expand...
Click to collapse
Thanks. After I looked in the zip, I thought something like that.
Seriously, you don't need speed with this hardware.
Think of cheap, stable, not battery eating
and hackable ARM11 development platform
After that incident with kernel.org they removed all the old android repos
so I have hard times to find the G1 pieces again. ezterry rocks. The kernel
changes are in his git, I could tweak+build the kernel with all the
modules I needed.
Let's see how to get the aosp together ...
(any hints greatly appreciated
PS: From how you worded your first post it sounded like you were trying to compile just the ezterry kernel xD so I apologise that I misunderstood ^^
Click to expand...
Click to collapse
I know, but my German is much better, I swear :angel:
Well.. I'd be happy to help rebuild my rom. Been wanting to set up a repo, but I'm lazy..
tvall said:
Well.. I'd be happy to help rebuild my rom. Been wanting to set up a repo, but I'm lazy..
Click to expand...
Click to collapse
Thanks for the email with tips.
I try to document the building process here:
hxxps://sites.google.com/site/aospdream/
As always, any hints or help from anybody are greatly appreciated ...
Thanks,
ptau
Hi All!
I have been trying to compile a Kernel for Android from Kernel.org Source. Avidly awaiting a Nexus 7 I got straight to work. I have created a zImage. I have been trying to document the process but rather than type it again I have been doing it here. If someone with a Nexus 7 wants to give this a go I would be very much grateful. This is an ongoing process. I have included the file and necessary instructions here...
It looks like I cant post external URL's .... YET! If you want to post here or PM Me I will send you the links.
If someone could test this for me it would be greatly appreciated.
Thanks
I'd like to help. How do you intend to test the kernel though? (since I'm not sure if it would work in Android, but of course you're probably more experienced than me)
Bogdacutu said:
I'd like to help. How do you intend to test the kernel though? (since I'm not sure if it would work in Android, but of course you're probably more experienced than me)
Click to expand...
Click to collapse
Basically people flash it and then test it. People can provide their own benchmarks if they want. Against their previous Kernel versions etc. I have a sort of active thread on the Neowin Forums about this but I cant post links yet on XDA. I also got my VPS setup today to build and host the files.
JamesSawyer said:
Basically people flash it and then test it. People can provide their own benchmarks if they want. Against their previous Kernel versions etc. I have a sort of active thread on the Neowin Forums about this but I cant post links yet on XDA. I also got my VPS setup today to build and host the files.
Click to expand...
Click to collapse
Okay then, I can do that. I assume you can PM links?
You might be able to state the URL address in your post for your kernel. I'd test it and I guess others may also.
Hi All,
I have someone from Neowin who is going to post the links for me.
At the moment my guide and files are all disjointed I am trying to organize it better.
Great idea! I'll look around your thread @neowin.
What supposedly differences are there from the native android kernel and one compiled using the code from kernel.org?
Personally I just like playing with Bleeding Edge code. You would get all the latest features from source as well as bug fixes most end users wouldn't see. Performance is to be determined, Battery life and CPU performance etc. Its also quite a little Niche that I like been a part of if it all works and comes off.
The kernel you're compiling most likely won't work if you don't even have the machine definitions nor the drivers for your nexus (seeing that you have taken the source directly from kernel.org)
The best of testing a new version would be to backport it but doing so takes an incredible amount of time and considerable skills.
Envoyé de mon Nexus 7 en utilisant Tapatalk
I have used the Prebuilt ToolChain from git and also the defconfig to build the kernel from Google. I have created a boot.img this should make it easier. I am just waiting a Nexus 7 myself to test this anyway.
JamesSawyer said:
I have used the Prebuilt ToolChain from git and also the defconfig to build the kernel from Google. I have created a boot.img this should make it easier. I am just waiting a Nexus 7 myself to test this anyway.
Click to expand...
Click to collapse
You need to have proper board files, proper drivers (device-specific ones) and tons more. I don't think it will work without those. Then chances are it's not going to compile properly; it will throw tons of errors. After you get it to compile, you have to get it to boot. After you get it to boot, you have to get it fully-functional (not necessary if this is a test kernel). So unless you have gone through it all, I don't think it'll work.
BUT I may be wrong.
It compiles no problem, That's what I am wanting people to test :good:
JamesSawyer said:
It compiles no problem, That's what I am wanting people to test :good:
Click to expand...
Click to collapse
Ready to test! Check that neowin thread, but all the links I've tried lead to 404
vrutkovs said:
Ready to test! Check that neowin thread, but all the links I've tried lead to 404
Click to expand...
Click to collapse
Hi!
Well I have not been on this for a few days however I set up a quick and dirty VPS. Looks like the process fell over. I have restarted it and published any files people might find useful on here.
http://svm24652.vps.tagadab.com:8000/
All actual builds are in the build folder.
JamesSawyer said:
Hi!
Well I have not been on this for a few days however I set up a quick and dirty VPS. Looks like the process fell over. I have restarted it and published any files people might find useful on here.
http://svm24652.vps.tagadab.com:8000/
All actual builds are in the build folder.
Click to expand...
Click to collapse
wow you are building 3.13 kernel?! Impressive if it boots
I have a patched 3.4.76 AOSP kernel in my repo thats all hahaha
poondog said:
wow you are building 3.13 kernel?! Impressive if it boots
I have a patched 3.4.76 AOSP kernel in my repo thats all hahaha
Click to expand...
Click to collapse
I am trying to ha! :highfive:
Do you have your 3.4 Kernel? Do you have notes how you built it?
Edit: Updated to include 3.13rc8
I have done some more merging from latest Mainline and Flo Kernel from Google. Its building as we speak. Time to head to Tesco.
Hopefully what I have done will get rid of a compile time error I was having.
Has anyone got the ones I made previous to boot. I have my Nexus 7 on the way as of today so I will be testing it on my own sooooon!! :good:
http://linux.jamessawyer.co.uk:8000/
A bit more easy to remember. There are some test builds and experimental stuff on there too. I might do requests if anyone wants me to make a build for their device let me know. Rather than the Nexus 7 2013. I only did that because thats the device I am getting
The link is down
Hi people,
With the recent announcement of @pedestre (creator of apolo kernel) that the development of apolo kernel comes to an end and Gustavo kernel does not be updated since a long time, we have no costum kernel for the many 5.1.1 roms that are coming to our phones....
Many people uses bln, cpu and gpu voltages control etc.
I want to ask someone with skils who can compile latest cm kernel, witch i think that will be compatible with all newest 5.1.1 roms, with basiclly feautures like bln and others... and if its possible, keep it update with lates cm realises....
Thanks, i hope some dev can help us
Yes, we need kernel developers
Maybe @Resync , @stelistcristi , @chhapil or @warrior1208 ?
Here is tutorial: How to build Gustavo kernel http://forum.xda-developers.com/showthread.php?p=54997129
Zile995 said:
Yes, we need kernel developers
Maybe @Resync , @stelistcristi , @chhapil or @warrior1208 ?
Here is tutorial: How to build Gustavo kernel http://forum.xda-developers.com/showthread.php?p=54997129
Click to expand...
Click to collapse
Always been considering to build a kernel, especially porting dorimanx to lollipop. Having trouble on ubuntu with dorimanx's instructions, so I will try bbqlinux instead and see how it goes.
Zile995 said:
Yes, we need kernel developers
Maybe @Resync , @stelistcristi , @chhapil or @warrior1208 ?
Here is tutorial: How to build Gustavo kernel http://forum.xda-developers.com/showthread.php?p=54997129
Click to expand...
Click to collapse
I can develop if @pedestre can give me the permissions to let me continue Apolo. Although, I'll do that and all the other ROMs' building stuff after 6th of June.
warrior1208 said:
I can develop if @pedestre can give me the permissions to let me continue Apolo. Although, I'll do that and all the other ROMs' building stuff after 6th of June.
Click to expand...
Click to collapse
I'm sure he would give you persmission to do that.
Right now I'm cloning my repo of dorimanx kernel. Have made a few changes like chhapil (except no uber tc yet). I'll see if I can release something next week (however will be very busy with exams). I'm still very new at building kernels so expect a few quirks with the kernel.
---------- Post added at 07:12 AM ---------- Previous post was at 07:10 AM ----------
Nightshadow931 said:
I'm sure he would give you persmission to do that.
Click to expand...
Click to collapse
Should be alright since android kernel is open source.
This thread is already awsome!
Yes please LL Kernel! CM sourced RR for galaxy s2 gt i9100 needs kernel!
Developers please come forward we beg you!
@warrior1208 Instead of continuing a Kernel, why not make and develop one yourself and name the kernel yourself as well? It would be nice if there's a new kernel name in our device. Just suggesting here...
:good:
souler456 said:
@warrior1208 Instead of continuing a Kernel, why not make and develop one yourself and name the kernel yourself as well? It would be nice if there's a new kernel name in our device. Just suggesting here...
:good:
Click to expand...
Click to collapse
Let's see. I'll try. But first, I have to update all the three ROMs and then a custom kernel. Although, as I stated, I'll be able to do that after 6th of June.
Regards.
warrior1208 said:
Let's see. I'll try. But first, I have to update all the three ROMs and then a custom kernel. Although, as I stated, I'll be able to do that after 6th of June.
Regards.
Click to expand...
Click to collapse
Sure, man. Take your sweet time, and thanks for the response :good:
:good:
I vote for gustavo's kernel since last version of it was just everything i needed. Miss it's colour control very much
I would love to see a TWRP kernel, as I use the file manager to delete unwanted system files on rom updates.
I do think it has a more friendly UI too.
We need 2 type of kernel. One like gustavo_s' and other is like apolo.
One for full control
And other is daily usage and more stable
Or maybe one based on apolo with CPU and GPU OC
OskarUA said:
I vote for gustavo's kernel since last version of it was just everything i needed. Miss it's colour control very much
Click to expand...
Click to collapse
I'm pretty sure there not much work needed to get Gustavo's kernel working on newer lollipop builds. Right now, I've made changes to io schedulers, TCP algorithm, supersu. Still have no clue how to get build started, at least there's progress. Change of mind. Will be busy with exams.
Zile995 said:
Or maybe one based on apolo with CPU and GPU OC
Click to expand...
Click to collapse
Then apolo configurator must be updated too
Latest twrp CM based kernel is available in my threads...second post.
http://forum.xda-developers.com/showthread.php?p=61055230
Where is your thread? Link please.
JudgeDread11 said:
http://forum.xda-developers.com/showthread.php?p=61055230
Where is your thread? Link please.
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...dirtyunicorns-v9-3-unofficial-builds-t3111998
nhmanas said:
Then apolo configurator must be updated too
Click to expand...
Click to collapse
Actually no, everything can be done through terminal. That is, indeex, how apolo configurator/stweaks or any other such app works. Just executing commands.
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 !