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.
Related
Hey guys!
My device (the HTC One X for AT&T) currently has a CM9 and AOKP port. I really wanted to get started with developing though. I wanted to create a full AOSP ROM (directly from Google) just to learn the process and get my hands dirty with ROM development (I've already done quite a few mod packs and a kernel).
We have an open sourced CM9 device tree available. I've tried using that device tree for building the AOSP ROM but of course, it has errors because the AOSP source isn't CM9...
So what I'm asking is how can I use this CM9 device tree with a pure AOSP ROM? Like, how exactly do I edit the CM9 device tree so that it creates an AOSP ROM? I'm aware its no easy task, but if someone could point me in the right direction it would be greatly appreciated. I'm a noob when it comes to ROM development, I've never made one before haha I have compiled ROMs before, I maintain the AOKP nightlies for the HP Touchpad.
If someone could help me make this device tree work it would be awesome. Thanks!
P.S. Here is the tree in case someone wanted to look at it: https://github.com/vmagro/android_device_htc_evita
Delete cm.mk
Edit vendorsetup.sh (remove "cm_").
That is all you need to do, I believe.
Like you know, sync the AOSP source, include your device folder amd build.
Sent from my Galaxy Nexus using Tapatalk 2
mDroidd said:
Delete cm.mk
Edit vendorsetup.sh (remove "cm_").
That is all you need to do, I believe.
Like you know, sync the AOSP source, include your device folder amd build.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I found this thread and this is exactly what I'm doing. Would you be interested in answering my questions in exchange for a nice donation? I haven't had much luck getting help and being a single parent of three toddlers I really need to maximize my free time to work on this.
You also would have to delete any offending overlays from CM that are present within your device repo. As you compile you may run into errors which you could work through.
私のEVO 3Dから送信される。
dastin1015 said:
You also would have to delete any offending overlays from CM that are present within your device repo. As you compile you may run into errors which you could work through.
私のEVO 3Dから送信される。
Click to expand...
Click to collapse
Removing overlays doesnt work here. Have many issues regarding the kernel.
hey
Good luck
rohan32 said:
Hey guys!
My device (the HTC One X for AT&T) currently has a CM9 and AOKP port. I really wanted to get started with developing though. I wanted to create a full AOSP ROM (directly from Google) just to learn the process and get my hands dirty with ROM development (I've already done quite a few mod packs and a kernel).
We have an open sourced CM9 device tree available. I've tried using that device tree for building the AOSP ROM but of course, it has errors because the AOSP source isn't CM9...
So what I'm asking is how can I use this CM9 device tree with a pure AOSP ROM? Like, how exactly do I edit the CM9 device tree so that it creates an AOSP ROM? I'm aware its no easy task, but if someone could point me in the right direction it would be greatly appreciated. I'm a noob when it comes to ROM development, I've never made one before haha I have compiled ROMs before, I maintain the AOKP nightlies for the HP Touchpad.
If someone could help me make this device tree work it would be awesome. Thanks!
P.S. Here is the tree in case someone wanted to look at it: https://github.com/vmagro/android_device_htc_evita
Click to expand...
Click to collapse
Were you able to port aosp device tree from cm.Please tell me how ?
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.
I have no experience compiling roms. I really like this rom and would like to use it on my phone. Is there a template, guide or something that can make porting this rom to my ZU GPE easy?
Also I've looked at some guides on how to port any rom to any device and on the lollipop build for the AICP builds there is no longer the folder for system with all the folders, instead there is a .dat file that holds all of that and I have no idea how to extract it.
It's easiest if @alia5 still has the source adapted for the Xperia - if so, he can just make a few changes to the GPe device tree and build it.
It is possible to port from Xperia to GPe, as shown by blueether here, but I don't know if it works well. I'd go for building it from source.
There's a good guide for building here, but you'll need to make some changes to the device trees for them to work with AICP. If alia5 is busy, I can probably do it for you, if you'd prefer.
Triflot said:
It's easiest if @alia5 still has the source adapted for the Xperia - if so, he can just make a few changes to the GPe device tree and build it.
It is possible to port from Xperia to GPe, as shown by blueether here, but I don't know if it works well. I'd go for building it from source.
There's a good guide for building here, but you'll need to make some changes to the device trees for them to work with AICP. If alia5 is busy, I can probably do it for you, if you'd prefer.
Click to expand...
Click to collapse
Thanks so much! It's funny you mentioned the thread @blueether created. I used the the AICP port @alia5 made and just flashed the togari2gpe mod and it worked so that's what i'm using now I see that the team for AICP have started development for Lollipop and have put out some nightly builds for other devices. I wanted to try to learn how to port the Lollipop to my GPE. I saw this guide http://anythingsyouneed.blogspot.com/2014/06/how-to-port-custom-rom-rom-porting.html and downloaded the CM12 rom for the GPE to use as my base and the nexus 5 AICP rom to use as the port but when I extracted both roms the system apps, framework, etc were in the form of .dat file. I searched to see how to extract the .dat files and I came up with nothing. So I guess in order to port the AICP(Lollipop) rom I would need to build it from source.....right? Also I would need to make some changes to the device tree to work with AICP?
Crickette said:
Thanks so much! It's funny you mentioned the thread @blueether created. I used the the AICP port @alia5 made and just flashed the togari2gpe mod and it worked so that's what i'm using now I see that the team for AICP have started development for Lollipop and have put out some nightly builds for other devices. I wanted to try to learn how to port the Lollipop to my GPE. I saw this guide http://anythingsyouneed.blogspot.com/2014/06/how-to-port-custom-rom-rom-porting.html and downloaded the CM12 rom for the GPE to use as my base and the nexus 5 AICP rom to use as the port but when I extracted both roms the system apps, framework, etc were in the form of .dat file. I searched to see how to extract the .dat files and I came up with nothing. So I guess in order to port the AICP(Lollipop) rom I would need to build it from source.....right? Also I would need to make some changes to the device tree to work with AICP?
Click to expand...
Click to collapse
I'm glad that that tool worked, I wrote that before I had access to a GPe.
Building for source is the best bet. Do they have a togari tree for lollipop? if they do build that and see if you can get it built without any errors then get the device/sony/togari and device/sony/togari_gpe from cm11 or 12 and compare to the aicp folder and work from there. If you want a hand with anything shoot me a pm or hangouts request
Crickette said:
Thanks so much! It's funny you mentioned the thread @blueether created. I used the the AICP port @alia5 made and just flashed the togari2gpe mod and it worked so that's what i'm using now I see that the team for AICP have started development for Lollipop and have put out some nightly builds for other devices. I wanted to try to learn how to port the Lollipop to my GPE. I saw this guide http://anythingsyouneed.blogspot.com/2014/06/how-to-port-custom-rom-rom-porting.html and downloaded the CM12 rom for the GPE to use as my base and the nexus 5 AICP rom to use as the port but when I extracted both roms the system apps, framework, etc were in the form of .dat file. I searched to see how to extract the .dat files and I came up with nothing. So I guess in order to port the AICP(Lollipop) rom I would need to build it from source.....right? Also I would need to make some changes to the device tree to work with AICP?
Click to expand...
Click to collapse
Glad that it worked!
Into lollipop i will look sooner or later, just a matter of time (pretty busy atm)
I don't have access to a gpe, but i can take a look wheni'll look at lollipop
Thanks so much guys for the help!! I greatly appreciate it I will try it myself and see what I can come up with. You guys are awesome! @alia5 @blueether @Triflot
Hello!
I'd like to build my own rom from AOSP 8.0 official branch. I'm looking for some kind of guide but couldn't find any So, let's say I've got android source code and files from other custom rom that makes camera work. What have I to do to make my rom now? How can I build it and be sure that everything will work. Generally my target is to install android 8 on my Leeco le 2 x620 device with Mediatek chip
Any help is appreciated ^v^
LEGOL2 said:
Hello!
I'd like to build my own rom from AOSP 8.0 official branch. I'm looking for some kind of guide but couldn't find any So, let's say I've got android source code and files from other custom rom that makes camera work. What have I to do to make my rom now? How can I build it and be sure that everything will work. Generally my target is to install android 8 on my Leeco le 2 x620 device with Mediatek chip
Any help is appreciated ^v^
Click to expand...
Click to collapse
"I'd like to build my own rom from AOSP"
So you mean an aftermarket os like lineageos or carbonrom or do you mean that you take the aosp repo and compile aosp for your device? You can look in source.android.com
"source code and files from other custom rom that makes camera work"
Is that an already compiled rom? Because you won't get source code out of that
"How can I build it and be sure that everything will work"
Ya don't. Nothing can ever be 100% bugfree, it can either be from your device tree's source code, or the aosp code itself.
Generally, if there is a caf tree for your device, it's going to be 3x as hard to create an aosp tree.
It is going to be 100000x as hard to create an aosp tree that is for a newly released, new hardware requirement operating system.
Wanna know the topping of the cake? Mediatek is notorious when it comes to releasing the source (in fact, it has become a meme in the Mediatek users world) but don't let that stop you son.
You can try, but don't give up just because it won't compile the first couple of hundred times. The errors when compiling should give you a great start
Good luck.
ramiabouzahra said:
"I'd like to build my own rom from AOSP"
So you mean an aftermarket os like lineageos or carbonrom or do you mean that you take the aosp repo and compile aosp for your device? You can look in source.android.com
"source code and files from other custom rom that makes camera work"
Is that an already compiled rom? Because you won't get source code out of that
"How can I build it and be sure that everything will work"
Ya don't. Nothing can ever be 100% bugfree, it can either be from your device tree's source code, or the aosp code itself.
Generally, if there is a caf tree for your device, it's going to be 3x as hard to create an aosp tree.
It is going to be 100000x as hard to create an aosp tree that is for a newly released, new hardware requirement operating system.
Wanna know the topping of the cake? Mediatek is notorious when it comes to releasing the source (in fact, it has become a meme in the Mediatek users world) but don't let that stop you son.
You can try, but don't give up just because it won't compile the first couple of hundred times. The errors when compiling should give you a great start
Good luck.
Click to expand...
Click to collapse
Oh God, how am I meant to do this ;0 There is Lineage 14.1 project on my device. I really want to have android 8 on my phone. Thank you for all the advice.
Yes im trying the same andere without any succes so far.
Im also trying to port from a different device ROM to the stock ROM what im running now.
The chip sets are the same but the Android versions not.
It would be really Nice if some mtk ROM developer find some time in his busy life to create a ROM for our phone.
Or a guide to compile/port Android o tot oud phone.
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: