Hi!
If I want to build AOSP for N6P how should I obtain the necessary binaries & native apps?
I interested in the process logic, please don't post links to already extracted files.
So I have system.img & vendor.img - what files to grab for AOSP successful build?
http://lmgtfy.com/?q=how+to+build+your+own+ASOP+rom
dratsablive said:
http://lmgtfy.com/?q=how+to+build+your+own+ASOP+rom
Click to expand...
Click to collapse
This doesn't help I already spent 2 weeks reading different guides.
No one is complete & detailed.
ynedelskiy said:
This doesn't help I already spent 2 weeks reading different guides.
No one is complete & detailed.
Click to expand...
Click to collapse
You are better off doing the research yourself than asking people to do it for you.
I build CM instead of AOSP, but for your reference, I always sync the proprietary files from TheMuppets repo.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
AndyYan said:
I build CM instead of AOSP, but for your reference, I always sync the proprietary files from TheMuppets repo.
Click to expand...
Click to collapse
Thank you! That's easy path )
But what if I want to understand how that repo is constructed - I mean, which files should i extract from Nexus 6P system / vendor images to create such a repo by my own hands?
ynedelskiy said:
Thank you! That's easy path )
But what if I want to understand how that repo is constructed - I mean, which files should i extract from Nexus 6P system / vendor images to create such a repo by my own hands?
Click to expand...
Click to collapse
Might want to look inside corresponding device in the TheMuppets repo to see what's contained. Other than that I don't have a clue - I do quick and dirty builds once a month and don't care much about technical details.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
Related
I keep getting this sync error:
Code:
Unexpected end of command stream
Fetching projects: 99% (415/419) fatal: Couldn't find remote ref refs/heads/android-4.4.2_r1
error: Cannot fetch android_frameworks_opt_mms
error: Cannot fetch TheMuppets/proprietary_vendor_htc
also, if i have a working cm official, what can i pull from it that would work with omni?
pandasa123 said:
I keep getting this sync error:
Code:
Unexpected end of command stream
Fetching projects: 99% (415/419) fatal: Couldn't find remote ref refs/heads/android-4.4.2_r1
error: Cannot fetch android_frameworks_opt_mms
error: Cannot fetch TheMuppets/proprietary_vendor_htc
also, if i have a working cm official, what can i pull from it that would work with omni?
Click to expand...
Click to collapse
The error is incomplete... I have no idea WHICH repo it's looking for that branch on since it's failing on multiple repos.
My guess would be a malformed omni.dependencies or a bad manifest in .repo/local_manifests/
I can tell you that syncing TheMuppets will result in broken builds 90% of the time.
What should I do for device props instead of muppets? And malformed omni.dependencies? That can affect it?
Sent from my One Xl using Tapatalk
pandasa123 said:
What should I do for device props instead of muppets?
Click to expand...
Click to collapse
https://github.com/DonkeyCoyote/
pandasa123 said:
And malformed omni.dependencies? That can affect it?
Click to expand...
Click to collapse
Yes, because what's in omni.dependencies gets synced as well. So if it tells repo to sync something that isn't there...
So omni is like building other ROMs? Just like building cm but change the cm parts to omni and adding twrp?
On the HTC one xl (Evita) and I really liked the multi window and thought we were overdue for an Omni build, so I wanted to try building it myself instead of waiting for one
Sent from my One Xl using Tapatalk
pandasa123 said:
So omni is like building other ROMs? Just like building cm but change the cm parts to omni and adding twrp?
On the HTC one xl (Evita) and I really liked the multi window and thought we were overdue for an Omni build, so I wanted to try building it myself instead of waiting for one
Sent from my One Xl using Tapatalk
Click to expand...
Click to collapse
In essence, yes. And I applaud you for being proactive and starting to compile for yourself.
PonsAsinorem said:
In essence, yes. And I applaud you for being proactive and starting to compile for yourself.
Click to expand...
Click to collapse
everything is syncing beautifully now...just one quick question...
for omni, should i add to the sync the CyanogenMod/android_device_htc_evita git repo with the build? i mean, with the build, the only thing that's really specified is the kernel and thats it, so there has to be more variety than just that, isn't there?
pandasa123 said:
everything is syncing beautifully now...just one quick question...
for omni, should i add to the sync the CyanogenMod/android_device_htc_evita git repo with the build? i mean, with the build, the only thing that's really specified is the kernel and thats it, so there has to be more variety than just that, isn't there?
Click to expand...
Click to collapse
Nope, not really. I'd try to sync only Omni's repos (and Google's), and leave other ROMs out of it. Assuming you're trying to build for the evita, and Omni doesn't have one for that, then you're best bet is to:
1. Fork (or create) a device tree
2. Make sure it's omnified
3. Add it to local_manifest
4. Once you have it up and running with minimal bugs, request to have Omni fork your device tree so it can be supported.
PonsAsinorem said:
Nope, not really. I'd try to sync only Omni's repos (and Google's), and leave other ROMs out of it. Assuming you're trying to build for the evita, and Omni doesn't have one for that, then you're best bet is to:
1. Fork (or create) a device tree
2. Make sure it's omnified
3. Add it to local_manifest
4. Once you have it up and running with minimal bugs, request to have Omni fork your device tree so it can be supported.
Click to expand...
Click to collapse
Omnified? This always confuses me. How do users have twrp if they have cwm installed? Will it overwrite?
And for the Evita tree, its basically me downloading cm tree locally and changing it to comply with omni? And then uploading it to my git so it can be added to local_manifest with that?
Sent from my One X using Tapatalk
pandasa123 said:
How do users have twrp if they have cwm installed?
Click to expand...
Click to collapse
They don't. It's either one or the other.
pandasa123 said:
Will it overwrite?
Click to expand...
Click to collapse
If you install it, yes. You don't have to, but it's recommended.
pandasa123 said:
And for the Evita tree, its basically me downloading cm tree locally and changing it to comply with omni? And then uploading it to my git so it can be added to local_manifest with that?
Click to expand...
Click to collapse
More or less. If you haven't seen this yet:
Porting Omni To Your Device
everything is synced and i followed the guide about the .mk files and vendorsetup.sh
at the beginning of the build, it showed these issues and i was wondering what they meant
Code:
build/core/product_config.mk:241: *** No matches for product "omni_evita". Stop.
WARNING: Trying to fetch a device that's already there
EDIT: the build died:
Code:
build/core/product_config.mk:241: *** No matches for product "omni_evita". Stop.
** Don't have a product spec for: 'omni_evita'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
I am currently looking into porting SailFish onto the nexus 5. I have been doing a lot of reading and one of the first things it looks like you need to do is to get Mer onto the device. In order to do that one has to be able to create a mer image for the device. There is a detailed description of the process here: https://wiki.merproject.org/wiki/Image_Creation
My question is how can I get a functioning kickstart file (.ks) for the nexus 5 seeing as the reference kickstart link is dead. I know this deals in part with partitions so I am a little nervous just guessing it.
Please keep requests of ports and off topic discussion out of here. This is for dev discussion only.
aeppacher said:
I am currently looking into porting SailFish onto the nexus 5. I have been doing a lot of reading and one of the first things it looks like you need to do is to get Mer onto the device. In order to do that one has to be able to create a mer image for the device. There is a detailed description of the process here: https://wiki.merproject.org/wiki/Image_Creation
My question is how can I get a functioning kickstart file (.ks) for the nexus 5 seeing as the reference kickstart link is dead. I know this deals in part with partitions so I am a little nervous just guessing it.
Please keep requests of ports and off topic discussion out of here. This is for dev discussion only.
Click to expand...
Click to collapse
First of all you link is obsolete. MIC command now called mic, and arguments is changed a bit
https://wiki.merproject.org/wiki/Platform_SDK_and_SB2#Make_your_own_target
you can use tool mer-kickstarter to generate .ks
also on emulator there is kickstarter configs for Sailfish OS and you can use Jolla repos instead of Mer so you can partialy skip Mer part now
EnErGy[CSDX] said:
First of all you link is obsolete. MIC command now called mic, and arguments is changed a bit
https://wiki.merproject.org/wiki/Platform_SDK_and_SB2#Make_your_own_target
you can use tool mer-kickstarter to generate .ks
also on emulator there is kickstarter configs for Sailfish OS and you can use Jolla repos instead of Mer so you can partialy skip Mer part now
Click to expand...
Click to collapse
what do you mean by partially skip mer?
Also thanks for the sources!
aeppacher said:
what do you mean by partially skip mer?
Click to expand...
Click to collapse
Instead of installing packages from Mer repository and then reinstalling them by packages from Sailfish OS repo you can install it from Sailfish OS repo from the begining when creating image using mic.
Hi,
I synced the CM10.1 source last weekend. I mucked about with the kernel. I pointed it to Christopher83's custom toolchain. I built it. It works. I'm content.
However my plan was to revive 4.2.2 and actually ADD to it, otherwise you could just go and download the zip which the Andromadus team uploaded. Unfortunately I've discovered that I'm completely incompetent when it comes to firstly finding things to add, secondly finding the commit, and then thirdly trying to cherry pick and apply the commit so it works. I haven't really got to stage 3 yet.
So here's my suggestion: could someone please work with me or if syncing sources etc. is not possible, at least help me by being knowledgeable enough to know some good features, point me to the commits, and help me fix conflicts so that I can apply them successfully. Therefore I either want a team, the 4.2.2 revival team as it were, or someone or some people to help me if they can't directly interact with the sources. Don't worry if you can't build for whatever reason: if you can sync specific repos, e.g. settings, frameworks base, and modify them, and push them, so that I can build the ROM, that's fine. Anyone who helps at all will be deemed equally if not more important than myself, as I expect I'll ultimately just end up being the builder.
Thanks very much for your support.
I can help you with that. Tell me when you start your project and what errors did you get
Best Regards,
MarcoMarinho
RE: [DEV] CM10.1 builds | help needed adding features | "4.2.2 Revival Team"
_MarcoMarinho_ said:
I can help you with that. Tell me when you start your project and what errors did you get
Best Regards,
MarcoMarinho
Click to expand...
Click to collapse
Thanks firstly I thought a simple thing to do would be to add the recent app screen ram bar from SlimBean, but I can't find the commit anywhere in the SlimRoms github. Perhaps you know where it is or can find it for me, then I could cherrypick it and we could fix the conflicts together and we'd have our first unofficial CM10.1 ROM with additional features!
HTCDreamOn said:
Thanks firstly I thought a simple thing to do would be to add the recent app screen ram bar from SlimBean, but I can't find the commit anywhere in the SlimRoms github. Perhaps you know where it is or can find it for me, then I could cherrypick it and we could fix the conflicts together and we'd have our first unofficial CM10.1 ROM with additional features!
Click to expand...
Click to collapse
Sure
Here is the commit: https://github.com/SlimRoms/frameworks_base/commit/9c1c3c0955d51adc589ec6fbb667a0ae482de24e
You need this to: https://github.com/AOSB/android/commit/a512f16890af8c277c3d1a88c8bca36711b82328
RE: [DEV] CM10.1 builds | help needed adding features | "4.2.2 Revival Team"
_MarcoMarinho_ said:
Sure
Here is the commit: https://github.com/SlimRoms/frameworks_base/commit/9c1c3c0955d51adc589ec6fbb667a0ae482de24e
You need this to: https://github.com/AOSB/android/commit/a512f16890af8c277c3d1a88c8bca36711b82328
Click to expand...
Click to collapse
That looks interesting, but it's for KitKat... I'll try later once I'm confident. In the meantime, how can I get this to work: https://github.com/SlimRoms/packages_apps_Settings/commit/fb2ea42468bea20f09b99048c9e7535b6cde643f I'm OK apart from the very last bit in UserInterface.java, although I'm applying that code to SystemSettings.java anyway. Thanks
@demkantor @_MarcoMarinho_ I've synced the PA source, can you help me at all setting up the vision.adds file? Thanks
Sure thing, assume this is for 4.2 android right?
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Sure thing, assume this is for 4.2 android right?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep, as you know I synced the CM10.1 source a while ago so I used repo init --reference to sync the PA jellybean-legacy sources. Thanks for helping
paste this in a folder and title it
local_manifests
then add it to your .repo folder in ROM directory
I commented out a few things you may need to add, and there is possibly more but i dont have time to look into it all right now. just start with this, repo sync, and then build and check for errors
best of luck!
damn.... giving me uknown file, had to zip it first, so unzip the contents!
demkantor said:
paste this in a folder and title it
local_manifests
then add it to your .repo folder in ROM directory
I commented out a few things you may need to add, and there is possibly more but i dont have time to look into it all right now. just start with this, repo sync, and then build and check for errors
best of luck!
damn.... giving me uknown file, had to zip it first, so unzip the contents!
Click to expand...
Click to collapse
Thanks, do I only need to add these to the vision.adds file then, or do I not need a vision.adds file at all now?
HTCDreamOn said:
Thanks, do I only need to add these to the vision.adds file then, or do I not need a vision.adds file at all now?
Click to expand...
Click to collapse
cant say I've ever used a vision.adds file in a source build, I just find the files i need in github, download source, create a local_manifest, sync, check errors for somethings to add to manifest, build, check for errors, google how to fix, fix, fix, fix ,fix, then bam, got a rom that works.
but I can look into this vision.adds business, I don't think it will be necessary as this will place need files in the proper directories in your source code for you, I assume that's what the vision.adds would do?
demkantor said:
cant say I've ever used a vision.adds file in a source build, I just find the files i need in github, download source, create a local_manifest, sync, check errors for somethings to add to manifest, build, check for errors, google how to fix, fix, fix, fix ,fix, then bam, got a rom that works.
but I can look into this vision.adds business, I don't think it will be necessary as this will place need files in the proper directories in your source code for you, I assume that's what the vision.adds would do?
Click to expand...
Click to collapse
Here's the bit from their guide: http://forum.xda-developers.com/showpost.php?p=30958881&postcount=2 I'm not sure what it does though. I'm completely clueless about that whole post actually. I think it just syncs stuff after a sync.. or something. I don't know why though, isn't that what a local manifests file is for?
hmm... it looks like there will be a bit more to make than just the local_manifests
but i would attempt this first and if it doesnt work than follow the direction in that post as there me be a special way needed to build for pa, which i never have tried to build
most of what they are after will get pulled from local_manifests folder and placed appropriately. but at the same time... never used ./rom-build.sh before so this may be specific to pa, as in you need to follow their steps....
eh, just give it a try, if it doesnt work ill help you create those json files and build it the way laid out in their guide!
HTCDreamOn said:
Here's the bit from their guide: http://forum.xda-developers.com/showpost.php?p=30958881&postcount=2 I'm not sure what it does though. I'm completely clueless about that whole post actually. I think it just syncs stuff after a sync.. or something. I don't know why though, isn't that what a local manifests file is for?
Click to expand...
Click to collapse
Isn't easy, you need to add more repos to configure it for our phone.
This is very diferent:
http://forum.xda-developers.com/showpost.php?p=45827346&postcount=3467
As I said before, you need extra repos than CM needs. You can talk to the dev that made the SlimBean for our phone, as it's based on AOSP he needed to configure it as well.
Hey all,
I know people have tended to build an empty Flashable Zip file where non-devs can package, sign and create zip files for general flashing.
Would one of you hot shot devs be willing to build one? I'm trying to build a few flashable files to load various apps into the N6P system folder for others to use. I just have to mine working first before I can post for others to use. For now im just doing it the old school way and loading the folders and files into the System/Priv-App directory and testing.
Thanks in advance!
I've been using the one I used for older devices and it's working just fine. You should actually try some trusted ones and see if they still work now before you come and ask for a new one.
As of mine... I won't upload unless other solutions won't work, and I bet there are plenty out there that still works. Mine is actually based on one found on XDA too.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
AndyYan said:
I've been using the one I used for older devices and it's working just fine. You should actually try some trusted ones and see if they still work now before you come and ask for a new one.
As of mine... I won't upload unless other solutions won't work, and I bet there are plenty out there that still works. Mine is actually based on one found on XDA too.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
Click to expand...
Click to collapse
The other empty flashable zip files found on the internet are not working with android 7.1.1 operating system. Can anyone please help me with a flashable zip ?
I too would be interested in this.
Sent from my Nexus 6 using XDA-Developers Legacy app
Enjoy:
https://www.androidfilehost.com/?fid=529152257862693076
Enviado desde mi Nexus 6P mediante Tapatalk
G6 Play Sources​
A huge thanks to the anonymous user who sent this post to Motorola. This issue is fixed. We can now clone all the Jeter kernel sources in one shot!!!
For Oreo:
Code:
git clone -b oreo-8.0.0-release-jeter https://github.com/MotorolaMobilityLLC/kernel-msm jeter
For Pie:
Code:
git clone -b pie-9.0.0-release-pcp29 https://github.com/MotorolaMobilityLLC/kernel-msm jeter
This will clone the kernel sources into a folder named "jeter".
Deprecated Information:
In an effort to combat Motorola's anti open source practices, I've collected all available kernel sources for the G6 Play and placed them into a single zip. Inside this zip are 43 gzips which contain all parts needed to build the kernel for our device.
Back story:
For those of you who don't know, Motorola has split the kernel sources into many parts. There is no easy way to grab them, sync them, or pull them. GitHub also lacks the ability to search for specific release tags.
Example: You can't search for "MMI-OCPS" in all of Motorola's repos, and you can't search like this inside of a single repo either.
So you have to manually open each repo one by one, and scan every page for the tag that matches the release you need. Sometimes there's nothing. Sometimes it's 5 pages down. Then you have to unpack all the kernel parts you found, and some of them need to be merged into the same folder. There is no explanation on what gets merged where. You have to try building it, get an error, then find the part you're missing in one of the zips and add it. Then repeat the process.
This is the most anti open source practice I've ever seen. I'm hoping this spurs some development for our device.
Link is now void.
Nice work putting all of these together.
kwiksi1ver said:
Nice work putting all of these together.
Click to expand...
Click to collapse
I almost have a tree going! I clobbered one together so I can rebuild twrp using Omni 9.0 sources. I'm stuck at 99% but I'm slowly chomping the bit. It seems like I can easily build a 64bit twrp if I get the last kinks out. A complete build is slowly inching closer and I can finally taste it!
Well boy howdy this is just grand news
Good news and bad news. I finally got the build to complete. However, it's not booting because for some reason, it's not building the ramdisk. I can't figure out why. No amount of searching has helped me with this. I can't find any information about it. It shouldn't even be possible as far as I can tell. It produces a recovery.img, kernel, and dt.img but no ramdisk. I'm really lost on this one.
Spaceminer said:
Good news and bad news. I finally got the build to complete. However, it's not booting because for some reason, it's not building the ramdisk. I can't figure out why. No amount of searching has helped me with this. I can't find any information about it. It shouldn't even be possible as far as I can tell. It produces a recovery.img, kernel, and dt.img but no ramdisk. I'm really lost on this one.
Click to expand...
Click to collapse
Did you have any luck figuring this out?
Sands207 said:
Did you have any luck figuring this out?
Click to expand...
Click to collapse
Not at all. I've given up on it.
Spaceminer said:
Not at all. I've given up on it.
Click to expand...
Click to collapse
Can you link me to the kernel source? I'll repo sync and try it on my dev machine
At this point I'm willing to pay someone ? 20-30 bucks to whoever gets us a decrypted twrp that ain't bugged out and works for all variants and models lol
Spaceminer said:
G6 Play Sources
In an effort to combat Motorola's anti open source practices, I've collected all available kernel sources for the G6 Play and placed them into a single zip. Inside this zip are 43 gzips which contain all parts needed to build the kernel for our device.
Back story:
For those of you who don't know, Motorola has split the kernel sources into many parts. There is no easy way to grab them, sync them, or pull them. GitHub also lacks the ability to search for specific release tags.
Example: You can't search for "MMI-OCPS" in all of Motorola's repos, and you can't search like this inside of a single repo either.
So you have to manually open each repo one by one, and scan every page for the tag that matches the release you need. Sometimes there's nothing. Sometimes it's 5 pages down. Then you have to unpack all the kernel parts you found, and some of them need to be merged into the same folder. There is no explanation on what gets merged where. You have to try building it, get an error, then find the part you're missing in one of the zips and add it. Then repeat the process.
This is the most anti open source practice I've ever seen. I'm hoping this spurs some development for our device.
Release Tag:MMI-PPP29.55-25 Pie (281mb)
Click to expand...
Click to collapse
I can't find Jeter pie source anywhere on their GitHub.
Mind throwing up a link?
Sands207 said:
Can you link me to the kernel source? I'll repo sync and try it on my dev machine
Click to expand...
Click to collapse
madbat99 said:
I can't find Jeter pie source anywhere on their GitHub.
Mind throwing up a link?
Click to expand...
Click to collapse
They don't exist in a single location on GitHub. There's literally no way to sync their sources that I'm aware of. I had to untar all the files that I have zipped together in the OP, into a rudimentary tree I found. Here's the closest thing we have.
https://github.com/SyNtheticNightmar3/android_device_motorola_jeter
Sure wish we had squid2 working on it I miss my g4 play
ninjakira said:
Sure wish we had squid2 working on it I miss my g4 play
Click to expand...
Click to collapse
I was praying for the same thing when I bought this phone.
Spaceminer said:
I was praying for the same thing when I bought this phone.
Click to expand...
Click to collapse
Right tbh that's why I even stuck with Moto is because of his work. I just popped over at the g7play forum and there doing slightly worse because the g7play is a/b partition and all they have is a dirty port of twrp for the g7
Spaceminer said:
They don't exist in a single location on GitHub. There's literally no way to sync their sources that I'm aware of. I had to untar all the files that I have zipped together in the OP, into a rudimentary tree I found. Here's the closest thing we have.
https://github.com/SyNtheticNightmar3/android_device_motorola_jeter
Click to expand...
Click to collapse
Did the g6 play start out on Nougat? I have been out of development since i got sick last year. I wish between us all we could get this mess sorted out. I'm bummed Moto doesn't have an open source website besides github where we could just download the source code and build from scratch.
Sands207 said:
Did the g6 play start out on Nougat? I have been out of development since i got sick last year. I wish between us all we could get this mess sorted out. I'm bummed Moto doesn't have an open source website besides github where we could just download the source code and build from scratch.
Click to expand...
Click to collapse
No. It came shipped with Oreo which means its treble compatible which is why you don't have to do the stuff people with phones before oreo need to do to "make" there phone treble compatible so they could flash gsi
ninjakira said:
No. It came shipped with Oreo which means its treble compatible which is why you don't have to do the stuff people with phones before oreo need to do to "make" there phone treble compatible so they could flash gsi
Click to expand...
Click to collapse
Then why is the nougat branch cloned for omni sources?
Sands207 said:
Then why is the nougat branch cloned for omni sources?
Click to expand...
Click to collapse
Hmmm I honestly couldn't even tell you why at this point ?? the development for this phone has been absolute hell from people stealing twrps to people trying to sell overpriced source and tress to making fake trees ?? like it's one giant "bruh, what the hell" moment
ninjakira said:
Hmmm I honestly couldn't even tell you why at this point ?? the development for this phone has been absolute hell from people stealing twrps to people trying to sell overpriced source and tress to making fake trees ?? like it's one giant "bruh, what the hell" moment
Click to expand...
Click to collapse
I can tell, wow
Sands207 said:
I can tell, wow
Click to expand...
Click to collapse
Yea but hey we're doing better than the G7 play guys right now so there's a win I guess ? o and hope your feeling better. Noticed you were kinda absent from all the chaos lol