I am trying to start my own custom source based ROM. It has a Slim base but as soon as I get it to where it can build, I will begin to add more features. I have source syncing just fine, but it will not build. I keep getting a crazy amount of bluetooth errors with THIS ONE being the latest problem. I am building for the VZW LG G2 (VS980) and this is a link to my source www.github.com/RageRom
Any help is greatly appreciated. I've been just doing trial and error building with little experience messing with source.
Related
I'm trying to build CM11 for LG L9 P760.
I tried following some of the tutorials and reached the point where I synced the CM11 repo.
I've also pulled the device tree to vendor/lge/p760 from a git and used extract_files.sh to get the files from device.
But I don't know where to go from here. I tried brunch p760 and got the following output.
http://paste.ubuntu.com/6626112/
There is an error towards the end.
I am also confused whether to add the kernel source, and if i have to, where and how i have to add it.
It'd be really great if you guys could help.
thanks.
Thanks
Thanks Master
Hi all,
I've been experiencing with Team-Gummy Rom source code for quite some time now. I usually compile from source to get the latest, along with some of my own addition. Lately I've been obsessed with having Android L code running on my Galaxy S4 (qcom) and so I downloaded AOSP source and after some failed attempts I was able to build it with the S4 device package from Team gummy.
So way cool! I may have in my hands the first (maybe not but as far as I know anyway) Android L build on the S4. But before going further, I have a question. In theory if I flash the system.img file produced by the build process and keep the kernel and boot.img from my current install, it should all come together right? Anyone here has an Idea what it would do?
I have been working on Cyanogenmod 12.1 for the LG G Stylo (codenamed LG G4 Stylus). We've gotten to the point where enough bugs are fixed where we can look at the possibility of porting new ROMs to the Stylo. Several roms are in progress, mainly AICP and XenonHD. I was looking at the possibility of taking up porting CarbonROM.
My approach that I currently have in mind is to sync the CarbonROM sources, along with all the dependencies, vendor files, kernel, and device tree from CM and resolve the errors from lunch and make from there. Is that approach on the right track? What other modifications do I need to make before starting?
Thanks in advance!
Sent from my LG-H631 using Tapatalk
Might take a look here http://forum.xda-developers.com/showthread.php?t=1798056
I'm no developer, but this thread will show you kernel and ROM building from source.
Saw it on Sony development Web yesterday...it will be awesome if any developers can make a fully functional rom
Well, haven't you seen the 7.1.1? The dev is still working on it, and the next build will be on O. We're working on it now. We have a channel for the news - https://t.me/joinchat/AAAAAELTVKqh1eeAesWWXw.
p.s. Thread must be deleted now, IMHO.
Thumbs-up to kamil ochman and other devs for your great work
To do list
https://gist.github.com/bartcubbins/69d44e166b529de192f2621b498f8030
What? Me?
Hi,
I downloaded the AOSP sources from Sony the other night to build a barebones from for my Z3. However, the Leo wasn't in the device tree, but what I did see were options for the E2303 & E2333. This was for 8.0.0 OPR3, mind you, so is an Oreo.
I was successful in building the images required for flashing, however the kernel fails to boot due to missing DTB. I am currently attempting to fix this so that the boot.img will boot and hopefully have a working Oreo for our M4. The inline kernel fails, so if anyone with skills in this particular area would be greatly appreciated. I'm not a developer, merely a tinker with determination. I am currently trying different patches seen on github for tulip, however no matter what I do I can not get the missing DTB into boot.img.
Dutch Burdock said:
I was successful in building the images required for flashing, however the kernel fails to boot due to missing DTB. I am currently attempting to fix this so that the boot.img will boot and hopefully have a working Oreo for our M4. The inline kernel fails, so if anyone with skills in this particular area would be greatly appreciated.
Click to expand...
Click to collapse
Write me in PM as quick as possible, we have a team of devs, and your help will be appreciated)
Hey there devs.
I'm looking forward to build a pure aosp rom based on oreo 8.1 for mido.
So far I've tried and successfully built los 14.1 and rr 5.8.5 from source, but I want to build aosp source so as to create a vanilla aosp rom. I've looked on the internet and asked a couple of devs here in the forum and they told me to merge caf patches. I totally understand the point of caf but then i don't know how to do it. Also I'm pretty sure that some patches (caf maybe) need to be added to source since the compilation always gives an error related to board config, when i followed the official guide at android website. (But then I don't understand what overlays i have to apply or even what they are)
Edit : i use gcloud to build.
If anyone can guide me as to how i can build aosp, it would be really helpful:fingers-crossed:
But then any help is appreciated.:good:
Thanks in advance!
i've no knowledge on building rom but im waiting for your vanilla for sure, hopefully you made it from Note 4X as base since all 8.1 rom i have tried are giving me various app are stopping after using it for sometime. i hope i can help you in some way though i have limitation in helping. thank you for your spirit!
groovepeppy said:
i've no knowledge on building rom but im waiting for your vanilla for sure, hopefully you made it from Note 4X as base since all 8.1 rom i have tried are giving me various app are stopping after using it for sometime. i hope i can help you in some way though i have limitation in helping. thank you for your spirit!
Click to expand...
Click to collapse
Don't worry man, I'll find out some way to build it. I'm Waiting for los 15.1 to get official so that the kernel source and other sources are out which i can use. But still I'm trying to learn and build.:laugh: