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 !
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 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
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
My friend owns an samsung galaxy tab 4 t-230 and would love to upgrade it into a more pure android. Since i kind of got into android ROMs and there are no AOSP or CM roms for the tab 4 t-230 this would be a great chance for me to build a AOSP or CM rom. I have ubuntu 14.10 and a decent enough pc with 16 gb of ram and an i7. If anyone could help me abit of how to build a AOSP or CM rom for the device i would be verry thankfull.
----------------------Edit-----------------------
I wanted to say thank to you guys! I did quite some progress by now. If you own a t230 / nu then feel free to check out my custom kernel
CTXz said:
My friend owns an samsung galaxy tab 4 t-230 and would love to upgrade it into a more pure android. Since i kind of got into android ROMs and there are no AOSP or CM roms for the tab 4 t-230 this would be a great chance for me to build a AOSP or CM rom. I have ubuntu 14.10 and a decent enough pc with 16 gb of ram and an i7. If anyone could help me abit of how to build a AOSP or CM rom for the device i would be verry thankfull.
Click to expand...
Click to collapse
Relevant post - some starting info, and check out the CM wiki he links to. Also, and this is a very basic step, but if you've never done this before it can be informative: download a rom zip file (preferably but not necessarily a stock-based kitkat rom for this device) and open it up in either 7zip or WinRar, check out the layout and structure, and familiarize yourself with the updater-script. (Actually you can do that with a firmware tar file too). Sorry I can't give you any more useful info, not a dev, definitely not a rom designer, just a guy who knows a fair amount of android stuff.
Also don't let the tone of that post discourage you; the poster was answering a guy who was basically asking about the feasibility of building a brand new rom for the sole purpose of being able to use one particular proprietary Samsung app. Yes it is difficult, but still doable, and you say you're motivated...
Yes i did forgot to say that any links for learning are appriciated
Well.. I would ask moonbutt74 for more info regarding commands and such, probably more info than I can give but.. keep in mind your going to have to download about 20+GB of source code and all that. Also a bunch more knowledge of more things I don't remember. But it is alot
-DUHA
Well I decided to revisit this thread. Never thought I would come so far. I really want to say thanks to all of you who supported me and still support me. Everyone has a beginning and here was mine. Now I am actually there where I really wanted to be. Releasing a custom kernel and finally work on a custom ROM! Thank you XDA!
CTXz said:
Well I decided to revisit this thread. Never thought I would come so far. I really want to say thanks to all of you who supported me and still support me. I mean everyone has a beginning and here was mine. Now I am actually there where I really wanted to be. Releasing a custom kernel and finally work on a custom ROM! Thank you XDA!
Click to expand...
Click to collapse
I'm amazed on how much people learn and achieve as well as myself. I've seen people who were total newbies then later built custom recoveries, CM12, Mods, Roms etc. Anyway good luck on working your rom!
Sent from my SM-T800 using Tapatalk
DUHAsianSKILLZ said:
I'm amazed on how much people learn and achieve as well as myself. I've seen people who were total newbies then later built custom recoveries, CM12, Mods, Roms etc. Anyway good luck on working your rom!
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
Also I thank you my life for introducing me to moonbutt74. He learned me everything from how to work with custom kernels to Roms. Sadly he decided to stop developing a few Werks ago but he's doing it for his own good. I still will mention @moonbutt74 on my future projects because he really is the one who changed me from confused to knowing what is actually going on. So thanks allot !
CTXz said:
Also I thank you my life for introducing me to moonbutt74. He leatned me everything from how to work with custom kernels to Roms. Sadly he decided to stop developing a few Werks ago but he's doing it for his own good. I still will mention @moonbutt74 on my future projects because je really is the one who changed me from confused to knowing what is actually going on. So thanks allot !
Click to expand...
Click to collapse
the erlkönig cant stop!
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.