Hey guys, since development for our Nexus 6P is taking off quite nicely, I was hoping to get a solid roomservice.xml written up so we can start compiling our own ROMs from source. Here is CM's Device and Kernel Tree, as well as the Vendor files from @TheMuppets. I am assuming though, there are a few other additions to this roomservice.xml that I have missed, but all in good time. If anyone wants to weigh in or advise please do, expect this post to change overtime.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_huawei_angler" path="device/huawei/angler" remote="github" />
<project name="CyanogenMod/android_kernel_huawei_angler" path="kernel/huawei/angler" remote="github" />
<project name="TheMuppets/proprietary_vendor_huawei" path="vendor/huawei/angler" remote="github" />
</manifest>
you dont really need an xml file though
just download the files manually and build
flex360 said:
you dont really need an xml file though
just download the files manually and build
Click to expand...
Click to collapse
Wow, to be honest I had no idea, I've only ever used the roomservice.xml method. Makes sense though. Just as a reference I'll add that in later when all the dependencies are figured out. Any idea what other dependencies are needed to build for Angler by chance?
Just lunch angler and add the muppets. Not sure why you are over thinking this. Room service is automatically created when you lunch (or breakfast) a device.
adzcache said:
Wow, to be honest I had no idea, I've only ever used the roomservice.xml method. Makes sense though. Just as a reference I'll add that in later when all the dependencies are figured out. Any idea what other dependencies are needed to build for Angler by chance?
Click to expand...
Click to collapse
you need device/huawei/angler/angler-kernel
akellar said:
Just lunch angler and add the muppets. Not sure why you are over thinking this. Room service is automatically created when you lunch (or breakfast) a device.
Click to expand...
Click to collapse
Perhaps I am over thinking all this. I was under the impression a roomservice.xml is handy for building a ROM for an unsupported device.
Say I wanted to build another ROM based on CM, that has outdated sources for Angler (or none at all), wouldn't a roomservice.xml pull updated CM sources to the project that I'm attempting to build?
That of course is just an example, I actually would prefer building Slim or something of the sort that utilizes Layers.
Damn I miss Slim..
adzcache said:
Perhaps I am over thinking all this. I was under the impression a roomservice.xml is handy for building a ROM for an unsupported device.
Say I wanted to build another ROM based on CM, that has outdated sources for Angler (or none at all), wouldn't a roomservice.xml pull updated CM sources to the project that I'm attempting to build?
That of course is just an example, I actually would prefer building Slim or something of the sort that utilizes Layers.
Damn I miss Slim..
Click to expand...
Click to collapse
6P is a supported device though. As far as building for another rom that doesn't have 6P support, there likely is much more to it than just pulling CM device trees.
akellar said:
6P is a supported device though. As far as building for another rom that doesn't have 6P support, there likely is much more to it than just pulling CM device trees.
Click to expand...
Click to collapse
Oh okay. Last time I built for an unsupported device all I changed to get a successful build was the cm.dependencies and cm.mk files (Maybe a few other minor changes), however that was on my old OnePlus One.
Thanks for clearing that up @akellar, I suppose it would probably be better to just wait for more ROMs to support Angler, then to screw around with the device tree. I may give it a go, just for testing sake though. Cheers!
Related
Hello there,while working on OMFGB and CM6,I decided to take ICS CAF sources and build them since andy is working at AOSP,arjen is working at CM9 and now I'm working at CAF. I opened this since I can handle various projects at a time,infact I'm developing for other stuff also.
Current status: Fixing build errors
All d best little genius..
@Bytecode, maybe this small info can be helpful:
you need to change a lot of configs in CAF to build - its like the AOSP configs.
the most pro on this project is, its made for MSM devices, possible you can get more
things to function (if things are fixed by CAF) as in CM9 or AOSP ... good luck
Good luck bro!
OT: Mind I ask u why u changed ur name?
Sent from my LG-P500 using xda premium
andy572 said:
@Bytecode, maybe this small info can be helpful:
you need to change a lot of configs in CAF to build - its like the AOSP configs.
the most pro on this project is, its made for MSM devices, possible you can get more
things to function (if things are fixed by CAF) as in CM9 or AOSP ... good luck
Click to expand...
Click to collapse
So developing for AOSP is same configs **** to fix
One thing I always asked myself: There is no msm7227 manifest in every caf build,but there's msm7627a,which is basically the same. Doesnìt matter if i build msm7627a?
Keep doing your thing Bytecode. Maybe just make one board for everything. Then when all is final release them in individual posts.
mentalityx said:
Keep doing your thing Bytecode. Maybe just make one board for everything. Then when all is final release them in individual posts.
Click to expand...
Click to collapse
You're right. But now i've already created them,so for the next time.
Bytecode said:
So developing for AOSP is same configs **** to fix
One thing I always asked myself: There is no msm7227 manifest in every caf build,but there's msm7627a,which is basically the same. Doesnìt matter if i build msm7627a?
Click to expand...
Click to collapse
dont know, the hw specs are the same - at least the same cpu/gpu and memory.
maybe only another camera^^
Building now
sooo... any news here?
Bytecode said:
Building now
Click to expand...
Click to collapse
Ha ha little bytecode is going again
Enjoy your build procedure well be waiting
Sent from my LG-P500 using xda premium
So... libskia is giving me ****:
make: *** No rule to make target "out/target/product/thunderg/obj/STATIC_LIBRARIES/libqc-skia_intermediates/libqc-skia.a", needed for per "out/target/product/thunderg/obj/SHARED_LIBRARIES/libskia_intermediates/LINKED/libskia.so". Stop.
(BTW: Used andy's device and vendor folder as well as his kernel).
Bytecode said:
So... libskia is giving me ****:
make: *** No rule to make target "out/target/product/thunderg/obj/STATIC_LIBRARIES/libqc-skia_intermediates/libqc-skia.a", needed for per "out/target/product/thunderg/obj/SHARED_LIBRARIES/libskia_intermediates/LINKED/libskia.so". Stop.
(BTW: Used andy's device and vendor folder as well as his kernel).
Click to expand...
Click to collapse
Seems like it's a missing file our a target file.
Sent from my LG-P500 using xda premium
Bytecode said:
So... libskia is giving me ****:
make: *** No rule to make target "out/target/product/thunderg/obj/STATIC_LIBRARIES/libqc-skia_intermediates/libqc-skia.a", needed for per "out/target/product/thunderg/obj/SHARED_LIBRARIES/libskia_intermediates/LINKED/libskia.so". Stop.
(BTW: Used andy's device and vendor folder as well as his kernel).
Click to expand...
Click to collapse
edit the Android.mk and remove that lib, its proprietary **** only
SWEATTAIMI said:
Seems like it's a missing file our a target file.
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
I don't have that anymore
Wow,I can already smell CAF optimized code: Frameworks base is different for lots of stuff: Using AOSP andy's framework base was a bad idea: I'll check on his github what he changed on frameworks base.
@andy: Did you change stuff in framework base for making it boot or you did it later?
I guess he changed things for his Phoenix Android look
Also some fixes needed there for loading old adreno-drivers.
_Arjen_ said:
I guess he changed things for his Phoenix Android look
Also some fixes needed there for loading old adreno-drivers.
Click to expand...
Click to collapse
I'm getting really,really confused here
Adding vendor and device folder from andy gives me libskia ****,adding all from andy gives me framework ****,I don't know what to do here
Lemme basically explain: What files are needed for building/booting CAF ICS succesfully? Don't post stuff necessary for fixing bugs later
Thank you
Just one little question, what branch did you use from framework_base?
You took the master-branch?
Guess you won't need the msm and qcom repo's, but need evereything else.
I can't remember I had problems related to skia during build, I have taken a look if I did change anything there, but I did not...
Don't have CAF-sources synced yet, so can't take a look what is going wrong.
Perhaps Lupohirp has them and can take a look.
Bytecode said:
I don't have that anymore
Wow,I can already smell CAF optimized code: Frameworks base is different for lots of stuff: Using AOSP andy's framework base was a bad idea: I'll check on his github what he changed on frameworks base.
@andy: Did you change stuff in framework base for making it boot or you did it later?
Click to expand...
Click to collapse
AOSP is not CAF, AOSP is not CM - each framework has its own code, it
has nothing to do with my changes, as you can see in my patches, its nothing
to make it "feel me like a phoenix"
To help you a bit:
some makefile variables cant be used in CAF, CM or AOSP and vice versa,
you have to look in relevant config variables ad what its used for,
than look in the source code if the name has changed or the variable
cant be used (or what ever).
_Arjen_ said:
Just one little question, what branch did you use from framework_base?
You took the master-branch?
Guess you won't need the msm and qcom repo's, but need evereything else.
I can't remember I had problems related to skia during build, I have taken a look if I did change anything there, but I did not...
Don't have CAF-sources synced yet, so can't take a look what is going wrong.
Perhaps Lupohirp has them and can take a look.
Click to expand...
Click to collapse
qcom repos are very needed to compile qcom related changes like audio/media.
I have a repo with android cm-12.1 as branch.
Now i want to update this repo to new CM version 13.0 without downloading the whole repo again.
Is that possible?
Unfortunately, no. Too many differences in the code bases.
MJPollard said:
Unfortunately, no. Too many differences in the code bases.
Click to expand...
Click to collapse
Okay,what happens if init a new branch (cm-13.0) in the same repo directory.
Is it faster than new repo?
Sent from my Micromax bolt
A27 using XDA Free mobile app
svprm said:
Okay,what happens if init a new branch (cm-13.0) in the same repo directory.
Is it faster than new repo?
Click to expand...
Click to collapse
Even if you could do that (and I'm not sure you can), the new branch would probably have to sync every single package over again, so you aren't really saving any time (and would likely cause major headaches). I think you really would be better off creating a completely new repo.
I have a kernel that I need to merge MM-mr2 in. So I have my kernel and MM-mr2 in my github. I just need to merge mr2 into my base. I have googled my a** of and havent had any luck. Someone who could help with the commands it would be greatly appreciated
Not sure I am tracking completely. I'll do what I can to answer your query.
From what you are describing, you have 2 branches, Master and MM-mr2 for your kernel. Refer to Basic Branching and Merging and more Visual explanation here.
The critical thing to know is that, both should be your branches. If one of them is owned by someone else, then you will be required to create a Pull Request.
Basically here are the steps you'd follow.
Checkout your master Branch where your other branch is going to be merged.
I assume MM-MR2 is another branch in the same repository Tree. If so, just issue ,
Code:
git merge MM-mr2
Now issue git status command to see the merge resulted in conflicts. It most likely will depending on what MR2 had that master did not.
Resolve the conflicts, then issue,
git add -A
this will add all the modified files to your commit. At which time you can do
git commit --amend
which will create a new commit on the master branch. This you can push to your git.
Oh and FYI, this thread is a good resource to me. [Guide] How to use Github
Perseus said:
Not sure I am tracking completely. I'll do what I can to answer your query.
From what you are describing, you have 2 branches, Master and MM-mr2 for your kernel. Refer to Basic Branching and Merging and more Visual explanation here.
The critical thing to know is that, both should be your branches. If one of them is owned by someone else, then you will be required to create a Pull Request.
Basically here are the steps you'd follow.
Checkout your master Branch where your other branch is going to be merged.
I assume MM-MR2 is another branch in the same repository Tree. If so, just issue ,
Code:
git merge MM-mr2
Now issue git status command to see the merge resulted in conflicts. It most likely will depending on what MR2 had that master did not.
Resolve the conflicts, then issue,
git add -A
this will add all the modified files to your commit. At which time you can do
git commit --amend
which will create a new commit on the master branch. This you can push to your git.
Oh and FYI, this thread is a good resource to me. [Guide] How to use Github
Click to expand...
Click to collapse
Heres my github https://github.com/APOPHIS9283
I need to merge shamu-mr2, into Project-Rachel
apophis9283 said:
Heres my github https://github.com/APOPHIS9283
I need to merge shamu-mr2, into Project-Rachel
Click to expand...
Click to collapse
Merging two repos is a immense undertaking. Not that it can not be done. But it means enormous amount of work. It is not the same as merging two branches, as I assumed earlier.
Would you care to explain why those two repos need to be merged? Is there a set of commits from one that you'd like in the other ?
Yeah my kernel is pretty much marshmallow. I need to bring in marshmallow mr2 to have it up to date with Google
*BUMP*
Anyone?
apophis9283 said:
Yeah my kernel is pretty much marshmallow. I need to bring in marshmallow mr2 to have it up to date with Google
Click to expand...
Click to collapse
In that case, do a Diff on github.com and choose those two to compare. That will create a Pull Request that you can merge. Please see this Tut.
Perseus said:
In that case, do a Diff on github.com and choose those two to compare. That will create a Pull Request that you can merge. Please see this Tut.
Click to expand...
Click to collapse
One last question. Sorry Github and such has always beena weak point.
https://android.googlesource.com/kernel/msm/+/android-msm-shamu-3.10-marshmallow-mr2/
I try to fork that but there doesnt seem to be a way
apophis9283 said:
Yeah my kernel is pretty much marshmallow. I need to bring in marshmallow mr2 to have it up to date with Google
Click to expand...
Click to collapse
apophis9283 said:
One last question. Sorry Github and such has always beena weak point.
https://android.googlesource.com/kernel/msm/+/android-msm-shamu-3.10-marshmallow-mr2/
I try to fork that but there doesnt seem to be a way
Click to expand...
Click to collapse
Trust me when I say, I HATE Git for the obnoxious, inane and downright silly errors it throws at me. You're not the first and most definitely not the last.
As to that link, unfortunately you will need to download a archive (See that .tgz link up top ? ). Expand the contents locally, then create a dummy repo in your own Git via web. Then Push the local unzipped folder to that Repo. The end result on Github should look exactly like what is at that link. Here's a Link that might help.
Perseus said:
Trust me when I say, I HATE Git for the obnoxious, inane and downright silly errors it throws at me. You're not the first and most definitely not the last.
As to that link, unfortunately you will need to download a archive (See that .tgz link up top ? ). Expand the contents locally, then create a dummy repo in your own Git via web. Then Push the local unzipped folder to that Repo. The end result on Github should look exactly like what is at that link.
Click to expand...
Click to collapse
I created a dummy github account and forked mr2. No matter what I do I cant even see mr2 as an option. This has been so frustrating I just dont have the patience to deal with it anymore. I truly appreciate your time
Thanks to xanax droid. I literally had to type in 4 commands and bam. I was fone that quick
LINEAGE OS 13 FOR HARPIA
In the wake of perfected Nougat and nearly complete Oreo for our beloved G4 Play… the ROM literally none of you have asked for is finally here!!!
:victory::victory::victory:
NOTE: This ROM has been discontinued, due to Xposed being released for Nougat, but more so due to sync errors whenever I try to pull the latest changes to my system with repo sync. I'll keep the thread here in case any of you want to build this for yourselves, since the steps needed to build everything differ from what the official Lineage wiki says about building Lin13.
What’s Working
Everything seems good to me
What’s Not Working
I can't find anything, so let me know
How To Build
Follow the standard procedure found on the Lineage Wiki for building Lineage 13, except DO NOT INSTALL OPENJDK 7!!! If you have this on your system, remove it before starting the process. JUST STICK WITH JAVA 8!!!
After doing your repo sync to get everything on your computer, run "breakfast harpia" so it creates a roomservice.xml file. After breakfast is done, replace the roomservice file it auto-generates with this one below:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Dark98/android_device_motorola_harpia" path="device/motorola/harpia" remote="github" />
<project name="Dark98/android_device_motorola_msm8916-common" path="device/motorola/msm8916-common" remote="github" />
<project name="SubhrajyotiSen/android_kernel_motorola_msm8916" path="kernel/motorola/msm8916" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_external_bson" path="external/bson" remote="github" />
<project name="LineageOS/android_external_stlport" path="external/stlport" remote="github" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="moto8916/proprietary_vendor_motorola" path="vendor/motorola/" remote="github" revision="cm-13.0" />
</manifest>
and do a "repo sync --force-sync". Once that's done, just brunch it and you'll be good to go!
As a side note, to add custom ringtones/alarms/sounds to your ROM, you need to wait for it to successfully build once, then put your desired .ogg files in the respective /system/media/audio/ folder that's contained in your specific device's /out directory, and build again (don't do a make clean or make clobber, it'll erase your work). Interpret me saying this however you want
Download Link
DOWNLOAD FROM GOOGLE DRIVE HERE
I also recommend a custom kernel, like SomeFeak or SquidKernel.
Questions You May Want To Ask
Why would I even want to use this ROM?
Since Xposed for Nougat just came out, there's literally no practical reason for you to need to use this anymore. I guess if you want some nostalgia, but that's it.
Why would you want to even make this ROM?
Something about me just wants at least one stable, updated MM ROM for this thing. I really can’t tell you why, just a weird urge I have.
I’m getting Java build errors when I try to compile!!!
Make sure you have only Java 8, and no Java 7.
I’m getting build errors at Gello when I try to compile!!!
You can disable Gello during the build process, which I did. Edit the moto8916.mk file in moto8916-common device directory and comment out all the stuff about Gello.
I’m getting status 2 errors at the kernel part when I try to compile!!!
GET RID OF JAVA 7!!!!!
How often will you be updating this?
This is obviously an unofficial build, so while I’ll try to make regular releases if everything works out alright, don’t expect that. I’m thinking maybe once a week or so, maybe every 2 weeks if life gets really busy.
Why won't my device encrypt? When I try to make it encrypt it just bootloops or reboots without doing anything
Make sure you're UNROOTED before you try and encrypt. Having a custom kernel/Xposed/etc. is fine, you just need to take off root before running the encryption process. Once it's done, you can reroot and be happy again.
There's something wrong with jack-admin when I try to compile and it won't work!!!
Run the following commands from inside the root of your build directory:
export JACK_SERVER_VM_ARGUMENTS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx#g" (REPLACE # WITH 1GB LESS THAN THE AMOUNT OF RAM YOU HAVE)
./prebuilts/sdk/tools/jack-admin kill-server
./prebuilts/sdk/tools/jack-admin start-server
Then try to brunch again, see if that fixes it
Special Thanks
My good man @Dark98 has been a huge help in getting this to work. He was actually the first to make a Lin13 build for Harpia about 2 months ago, so without his initial work in solving all the compiler error stuff (like the BoardConfig thing mentioned above) I wouldn’t be able to release what I did. Also, special thanks to all you guys in the SomeFeak telegram group!
One day I want to learn how to make ROMs and have that same willpower as you. xD
I've never used Xposed. Maybe I'll test the ROM to see what it looks like.
Good luck and good work!
Arushidesu said:
One day I want to learn how to make ROMs and have that same willpower as you. xD
I've never used Xposed. Maybe I'll test the ROM to see what it looks like.
Good luck and good work!
Click to expand...
Click to collapse
I just flashed back to MM firmware from soak test 7.1.1, and even when installing the ROM on this bootloader/firmware it still doesn't boot. Stay tuned though, I feel like I'm VERY close to getting this thing to work!
UPDATE: After fixing a command regarding GCC exporting, I'm getting new compilation errors with the kernel. I COULD skip kernel compilation, but I'm not sure how that would work out when trying to actually flash the ROM.
jasonmerc said:
UPDATE: After fixing a command regarding GCC exporting, I'm getting new compilation errors with the kernel. I COULD skip kernel compilation, but I'm not sure how that would work out when trying to actually flash the ROM.
Click to expand...
Click to collapse
Alright, I don't know a thing about what goes on under the hood here, but doesn't getting compilation errors mean a broken kernel? And as far as I know, a broken kernel would lead to booting errors, won't even boot up I guess? Correct me if I'm wrong, please
NovaKenn said:
Alright, I don't know a thing about what goes on under the hood here, but doesn't getting compilation errors mean a broken kernel? And as far as I know, a broken kernel would lead to booting errors, won't even boot up I guess? Correct me if I'm wrong, please
Click to expand...
Click to collapse
That's exactly what a broken kernel would do. Before the kernel would compile, but it still wouldn't boot even when flashing a different kernel. Something else under the hood is going on here, which I was told my gcc export commands would fix. Now that I put in the gcc export stuff, it can't compile the kernel, and therefore never finishes compiling the ROM. I'm looking into this right now, not sure when I'l get a solution though (seems harder than I thought to fix)
jasonmerc said:
That's exactly what a broken kernel would do. Before the kernel would compile, but it still wouldn't boot even when flashing a different kernel. Something else under the hood is going on here, which I was told my gcc export commands would fix. Now that I put in the gcc export stuff, it can't compile the kernel, and therefore never finishes compiling the ROM. I'm looking into this right now, not sure when I'l get a solution though (seems harder than I thought to fix)
Click to expand...
Click to collapse
Appreciate the amount of effort you're putting in here, but I really think it would have been worth the hard work if you had gone for LOS 15 instead. Not many seem to have interest in opting for a MM ROM now. Personally, I would like to try Xposed on MM at least once as I stumbled across XDA only after N.
Anyways, we'll be waiting for your ROM! All the best to you mate!
NovaKenn said:
Appreciate the amount of effort you're putting in here, but I really think it would have been worth the hard work if you had gone for LOS 15 instead. Not many seem to have interest in opting for a MM ROM now. Personally, I would like to try Xposed on MM at least once as I stumbled across XDA only after N.
Anyways, we'll be waiting for your ROM! All the best to you mate!
Click to expand...
Click to collapse
Some other developers are already working on O roms: There's an alpha build of GZOSP Oreo on Android File Host (made by the same guy that's helped me with building this ROM) if you'd like to look at that as well. I may move to Oreo eventually, but I'd REALLY like to get this working before I do. Even if it's not my daily driver forever, to be able to make builds if I want to would be ideal.
jasonmerc said:
Some other developers are already working on O roms: There's an alpha build of GZOSP Oreo on Android File Host (made by the same guy that's helped me with building this ROM) if you'd like to look at that as well. I may move to Oreo eventually, but I'd REALLY like to get this working before I do.
Click to expand...
Click to collapse
GZOSP done so soon? Well gotta try it out once anyway. Let's taste it once.
NovaKenn said:
GZOSP done so soon? Is that for harpia though?
Click to expand...
Click to collapse
It's far from stable, but yes it is for Harpia. Feel free to take a look and flash it if you want, help give Dark98 some support as a thanks for helping me with this
But back on topic though, I have another build running on my PC at home at the moment. I had to edit the gcc export script a little bit, if it fixes the problem I'll update the first post with the fixed command to add.
UPDATE: My good man @facuarmo suggested I take the boot.img of Josh's older (but more stable) Lin13 build and put it in my newer, non-booting Lin13 build for a sort of workaround until I can figure out how to get sources compiled correctly on my own. I've just uploaded a "fixed" ROM zip to my google drive if any of you want to try this out. I'll be making a NAND backup of my Nougat ROM then giving this a try myself.
EDIT: Replacing the boot image did nothing, so back to the drawing board
GOOD NEWS SORTA!!! Josh was able to compile a new Lineage 13 build, which I tested and can confirm it works. He's gonna share his local manifests with me so I can build and maintain it. If it still won't build even after that, I'll ask him if I can give a link to his build, to hold you guys over who are waiting for this.
Big shout out to Josh who's been a tremendous help this whole time. If I knew his XDA username I'd cite it, but otherwise you can find him on GitHub:
https://github.com/dark98
I am testing the update of Josh and it goes very well, I keep in touch with the (telegram)
Is Lineage 13 marshmallow?
Enviado desde mi Moto G Play mediante Tapatalk
mario156090 said:
Is Lineage 13 marshmallow?
Enviado desde mi Moto G Play mediante Tapatalk
Click to expand...
Click to collapse
yup
Neither Josh nor I have any idea why this isn't working for me. I've seemingly 1:1 copied everything he's done (besides the distro of Linux I use) and I still get weird errors when he gets none. My last hope is going to be replace Ubuntu with Debian for my Android Building VM, and if that doesn't work I'm going to have to abandon this since I'm not sure how to fix the problems I'm getting.
In the meantime though, here is his build of Lin13 in case you all want to run that.
jasonmerc said:
Neither Josh nor I have any idea why this isn't working for me. I've seemingly 1:1 copied everything he's done (besides the distro of Linux I use) and I still get weird errors when he gets none. My last hope is going to be replace Ubuntu with Debian for my Android Building VM, and if that doesn't work I'm going to have to abandon this since I'm not sure how to fix the problems I'm getting.
In the meantime though, here is his build of Lin13 in case you all want to run that.
Click to expand...
Click to collapse
Running stable? Or is it unstable-ish?
NovaKenn said:
Running stable? Or is it unstable-ish?
Click to expand...
Click to collapse
100% stable, everything works great from what I can see. I flashed SomeFeaK kernel as well, so maybe that's attributing to it, but still everything works fine.
Quick update though, I found out from Josh that I apparently DON'T NEED JAVA 7 AT ALL during the compilation, contrary to what Lineage WIki's build instructions say for Lineage 13. Not only am I removing Java 7 completely and trying again, but I'm editing my manifests as well. I hope this works.
Great news guys! It built on my own system!!! I'm not sure if it'll actually boot (since I'm rebuilding with a some little goodies in there to thank you all for your partience) but this is a very good sign! As usual, stay tuned for updates!
EDIT 1: New build is up, check the download link for Lineage 10062017. I haven't been able to test if it boots yet, but it's there nonetheless
I just flashed my new 10-06 build over the 10-01 one Josh made, and I was actually able to boot it!!!!! Everything is officially working now!
So I have successfully built OmniRom 8.1 Oreo for Shamu the zip file is a little over 500mb. The package flashes correctly but fails to boot. I have already tried to change the BoardConfig.mk file to be SeLinux=Permissive but it still fails to boot. My device is decrypted as well. What could be a source of the non boot issue other than what I have mentioned. This project is taking quite some time to complete.
HELP!!!!!
Does omnirom even have a 8.1 branch for shamu? I can't see it.
Elektroschmock said:
Does omnirom even have a 8.1 branch for shamu? I can't see it.
Click to expand...
Click to collapse
No it doesn't I am trying to bring it up, I know they don't officially support it for Oreo. They don't have a device maintainer for Shamu anymore. I have been using other device trees and filling in the required files for building Omni. Like I said I can get a successful build but in won't boot.
Rondeau79 said:
No it doesn't I am trying to bring it up, I know they don't officially support it for Oreo. They don't have a device maintainer for Shamu anymore. I have been using other device trees and filling in the required files for building Omni. Like I said I can get a successful build but in won't boot.
Click to expand...
Click to collapse
Well thats not how a bringup works. You need a ****load oft kernel and device commits for shamu to Boot Oreo.
The easiest way would be forking a working device and kernel repository...e.g. LineageOS. Next step would be adapting some makefiles and overlays.
Not much to do, as we have already done the Oreo bringup months ago.
Elektroschmock said:
Does omnirom even have a 8.1 branch for shamu? I can't see it.
Click to expand...
Click to collapse
Elektroschmock said:
Well thats not how a bringup works. You need a ****load oft kernel and device commits for shamu to Boot Oreo.
The easiest way would be forking a working device and kernel repository...e.g. LineageOS. Next step would be adapting some makefiles and overlays.
Not much to do, as we have already done the Oreo bringup months ago.
Click to expand...
Click to collapse
Yeah that's what I did. When the build first starts something in the vendor folder isn't being globed. It's only 99% of that folder that is accounted for. The build is successful but it just won't boot. I don't have much coding experience so this is really hard.
Rondeau79 said:
Yeah that's what I did. When the build first starts something in the vendor folder isn't being globed. It's only 99% of that folder that is accounted for. The build is successful but it just won't boot. I don't have much coding experience so this is really hard.
Click to expand...
Click to collapse
Do an -eng build and read logcat and dmesg via ADB. Usually you see whats wrong.
Rondeau79 said:
Yeah that's what I did. When the build first starts something in the vendor folder isn't being globed. It's only 99% of that folder that is accounted for. The build is successful but it just won't boot. I don't have much coding experience so this is really hard.
Click to expand...
Click to collapse
Hey how's it going? I know you've been trying hard to get an 8.1 Omni build running. FYI, @bthorne79 put out an Omni 8.1 build for Shamu back in December of last year. I tried it at the time and it was a nice build but if I remember correctly, the theming didn't work. I tried changing to a dark theme but it just stayed on default light theme. I always use a dark or black theme on Shamu and I'd rather not have to use substratum. Other than that, the rom ran very well.
Maybe give him a shout, after all you both have 79 in your name. Good luck, I definitely wouldn't mind seeing an Omni 8.1 build.
Mike T
webdroidmt said:
Hey how's it going? I know you've been trying hard to get an 8.1 Omni build running. FYI, @bthorne79 put out an Omni 8.1 build for Shamu back in December of last year. I tried it at the time and it was a nice build but if I remember correctly, the theming didn't work. I tried changing to a dark theme but it just stayed on default light theme. I always use a dark or black theme on Shamu and I'd rather not have to use substratum. Other than that, the rom ran very well.
Maybe give him a shout, after all you both have 79 in your name. Good luck, I definitely wouldn't mind seeing an Omni 8.1 build.
Mike T
Click to expand...
Click to collapse
Yeah this project has been a real headache! Nothing like before were most of the files and programming has been done. I am not done yet, I don't give up too easy. This has been quite an undertaking.
Follow this thread: https://forum.xda-developers.com/showpost.php?p=54118631&postcount=4
That'll give you an idea about what all things to consider while building for a device :fingers-crossed:
Nitin
Rondeau79 said:
Yeah this project has been a real headache! Nothing like before were most of the files and programming has been done. I am not done yet, I don't give up too easy. This has been quite an undertaking.
Click to expand...
Click to collapse
If you push your sources somewhere where we can see it, it should be easier for us to help you.
nitin.chobhe said:
Follow this thread: https://forum.xda-developers.com/showpost.php?p=54118631&postcount=4
That'll give you an idea about what all things to consider while building for a device :fingers-crossed:
Nitin
Click to expand...
Click to collapse
Yeah that guide is so outdated! I followed that kind of stuff years ago when I couldn't build from source. I have done many builds that boot for 3 devices. This is a different problem.
Elektroschmock said:
If you push your sources somewhere where we can see it, it should be easier for us to help you.
Click to expand...
Click to collapse
Yeah I am using Omni ROM source with device trees and kernel source from Lineage Oreo. I have modified files and make sources. I have all up to date vendor blobs cloned. There is no build errors just an issue with the system not booting. Pushing my source upstream would be to my personal GitHub account which I have never had to do. Usually I repo/clone source build and upload to Android File Host for working zips. I have never pushed anything up from my laptop!
Rondeau79 said:
Yeah that guide is so outdated! I followed that kind of stuff years ago when I couldn't build from source. I have done many builds that boot for 3 devices. This is a different problem.
Click to expand...
Click to collapse
Even though it is outdated it is still very much applicable. I linked that thread because you mentioned this.
Good that you know the problem. All the best!
Nitin
Rondeau79 said:
Yeah I am using Omni ROM source with device trees and kernel source from Lineage Oreo. I have modified files and make sources. I have all up to date vendor blobs cloned. There is no build errors just an issue with the system not booting. Pushing my source upstream would be to my personal GitHub account which I have never had to do. Usually I repo/clone source build and upload to Android File Host for working zips. I have never pushed anything up from my laptop!
Click to expand...
Click to collapse
It's not that you need to push it somewhere to get working zips, it's just for us to see your modifications.
Otherwise it is just guessing what you did.
Making it compile is one thing...making it work is a whole different story. When I did the Lineage Oreo bringup I had many things to fix untill it bootet properly.
Lineage's device tree for shamu depends on several other Lineage repositories. For example:
android_hardware_lineage_interfaces
android_hardware_qcom_gps
android_vendor_lineage
android_device_lineage_sepolicy
So just cloning the device repo without examining the reason for your 'bootloop' will get you nowhere.
I'd suggest you to do an engineering build which is easier to debug. Altought I would make this build permissive as selinux denials are a common reason for a bootloop.
How about trying a known working kernel such as popcorn? If the kernel works, you might be able to get some logs. And if you know whether your kernel is the problem, you are one step closer.
runekock said:
How about trying a known working kernel such as popcorn? If the kernel works, you might be able to get some logs. And if you know whether your kernel is the problem, you are one step closer.
Click to expand...
Click to collapse
If he is based of lineage's device tree, then Lineage's kernel is the best choice.
You should always be able to grab a log, no matter which kernel you are using.
Yeah willing to help out put your stuff up on git and give links
My webhost is down right meow but I can post my Oreo build I had of Omni here I didn't use Los trees i used aosp trees from camcory , joryb and mine cleanos
---------- Post added at 08:47 PM ---------- Previous post was at 08:28 PM ----------
i found my build i had it on afh if you want it to try this was early oreo so some things not fully functional i think gps was iffy https://www.androidfilehost.com/?fid=889964283620775520 i am syncing up omni oreo again for sure will help out if you want please pm
---------- Post added at 08:47 PM ---------- Previous post was at 08:47 PM ----------
nougat builds in that root folder also
bthorne79 said:
Yeah willing to help out put your stuff up on git and give links
Click to expand...
Click to collapse
My device and kernel tree GitHub link.
https://github.com/Rondeau79
Rondeau79 said:
My device and kernel tree GitHub link.
https://github.com/Rondeau79
Click to expand...
Click to collapse
Your probably going to want to fork the toolchains over that was used with cleanaosp
<!-- Prebuilts --> <project path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.9" name="joryb/arm-eabi-7.x" clone-depth="1" remote="bb" revision="master"/> <project path="prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9" name="joryb/arm-linux-androideabi-7.x" clone-depth="1" remote="bb" revision="master"/>