Related
Hi guys,
I went to check for the HTC DX source code on htcdev.com, and saw there were around 31 sources, but they're are all CRC's...
Could anyone please explain to me, what is a CRC? I tried googling it, but it didn't really help.
Sent from my HTC Desire X using xda premium
kernel source
Lloir said:
kernel source
Click to expand...
Click to collapse
I have been reading up on making roms, mostly about AOSP and CM, since they have best info and tutorials and such. But at some point, they both say to port to a new device you need to have the proprietary files (non open source device-specific software) to be able to build a working rom, using ./extract-files.sh or ./proprietary-files.sh.
From what I've read, identifying these files is mostly educated (not my case, lol) guessing, trial and error,... But I was wondering : is this CRC source code what they are talking about and would there be a way to get all the necessary proprietary files from it ?
infernal77 said:
I have been reading up on making roms, mostly about AOSP and CM, since they have best info and tutorials and such. But at some point, they both say to port to a new device you need to have the proprietary files (non open source device-specific software) to be able to build a working rom, using ./extract-files.sh or ./proprietary-files.sh.
From what I've read, identifying these files is mostly educated (not my case, lol) guessing, trial and error,... But I was wondering : is this CRC source code what they are talking about and would there be a way to get all the necessary proprietary files from it ?
Click to expand...
Click to collapse
Search for vendor protou github.
Google it. You'll find proprietary files.
Regards
Sent from my Desire using xda app-developers app
Yasir Javed Ansari said:
Search for vendor protou github.
Google it. You'll find proprietary files.
Regards
Sent from my Desire using xda app-developers app
Click to expand...
Click to collapse
Thanks, Yasir, I know lli0r made a device and vendor tree, but he said the vendor tree might be incomplete. He tried to make us a CM9 but hasn't got the device itself. I also read you can extract the files from a running device, but for that you need extract-files.sh or proprietary-files.sh, which isn't in there. I'm sure I can google and find one of those files from another device and try to run them on mine, but they're probably device-specific as well. And there isn't one of those files in lli0r's github. I checked that I'm sorry, I am ompletely new to Android, let alone building roms, but I love to just experiment a bit
Btw, when are you getting your Desire X ?
Hello,
I wanted to discuss means of creating a device tree for the Samsung Galaxy S4 I9500 so the development can start for the ROM, What is putting us off the track ? What do we need to reach a fully working device tree ?
Hope we could reach something out together ..
Look here
Faryaab has already created one. Let's fork the main repo or branch it with individual repository.. Let's create a team and start working on it
I will set up my Linux machine tonight. Hopefully, we can achieve what we want
Rahulrulez said:
Faryaab has already created one. Let's fork the main repo or branch it with individual repository.. Let's create a team and start working on it
I will set up my Linux machine tonight. Hopefully, we can achieve what we want
Click to expand...
Click to collapse
Perfect .. As I want to release for this device and the lack of a properly working Device tree is stopping me !
We can not really start on Faryaab's tree. He has given up on the I9500. He is not willing to develop it further (as far as I know). But I still thank him for kick starting it
We need another complete tree now
There's a hell of a lot more involved than creating the device tree... There is no Exynos5 "Octa" platform support anywhere in the tree.
Each platform almost always requires some degree of customization to the frameworks to support it - the required customizations for Exynos5 "Octa" are undocumented. (search the tree for QCOM_HARDWARE or EXYNOS4_ENHANCEMENTS for some examples.)
Anyone can create a tree. Implementing support for a new platform throughout the codebase is a whole other story - and no one wanting to do THAT so far is why the I9500 has no CM support.
Entropy512 said:
There's a hell of a lot more involved than creating the device tree... There is no Exynos5 "Octa" platform support anywhere in the tree.
Each platform almost always requires some degree of customization to the frameworks to support it - the required customizations for Exynos5 "Octa" are undocumented. (search the tree for QCOM_HARDWARE or EXYNOS4_ENHANCEMENTS for some examples.)
Anyone can create a tree. Implementing support for a new platform throughout the codebase is a whole other story - and no one wanting to do THAT so far is why the I9500 has no CM support.
Click to expand...
Click to collapse
I know, what I am thinking is just try to port framework and other important libraries and see if that works. Exynos is badly documented
maradonaiconboy said:
Perfect .. As I want to release for this device and the lack of a properly working Device tree is stopping me !
Clubvegas999
Click to expand...
Click to collapse
Two posts above yours, He said that it's not going to be easy simply because Samsung just can't document a thing properly !
With lack of proper documentation , It would be extremely hard to create the device tree .. I too want to build my ROM for the i9500 but we need to figure something out to be able to continue ..
Folks just coming by and asking it to get/keep it going - that's not dev talk and plenty of other forums to post that in.
So if your post disappeared... that's why.
Thanks.
Did you guys see ewmno device tree for i9500?
Follow Me on Twiiter @razer1224
---------- Post added at 11:48 AM ---------- Previous post was at 11:45 AM ----------
johnhany97 said:
Two posts above yours, He said that it's not going to be easy simply because Samsung just can't document a thing properly !
With lack of proper documentation , It would be extremely hard to create the device tree .. I too want to build my ROM for the i9500 but we need to figure something out to be able to continue ..
Click to expand...
Click to collapse
Did you check camerawrapper. Cpp of Xperia... Since GT-I9500 uses a Exmor Rs sensor
Follow Me on Twiiter @razer1224
---------- Post added at 11:51 AM ---------- Previous post was at 11:48 AM ----------
I am forking farylaab repo too
Dont we need proprietary files?
Follow Me on Twiiter @razer1224
ill try to work on the vendor tree to
i will push today the basic files
RD's I think you guys can help me
Device Tree (Forked From Faryaab)
https://github.com/KiranSurath/android_device_samsung_i9500
Vendor Tree (Full Experiment)
https://github.com/KiranSurath/android_vendor_samsung_GT-i9500
We Can Work as a Team
razer1224 said:
Device Tree (Forked From Faryaab)
https://github.com/KiranSurath/android_device_samsung_i9500
Vendor Tree (Full Experiment)
https://github.com/KiranSurath/android_vendor_samsung_GT-i9500
We Can Work as a Team
Click to expand...
Click to collapse
I want to work with you as a team but my exams are not allowing me to do so. As soon as my exams gets ,I will join with you.
Sent from my GT-I9500 using XDA Premium HD app
Trying to build with only device tree
Follow Me on Twiiter @razer1224
Sent from my SCH-I545 using xda app-developers app
razer1224 said:
Trying to build with only device tree
Follow Me on Twiiter @razer1224
Click to expand...
Click to collapse
Did it work with you or not ?
johnhany97 said:
Did it work with you or not ?
Click to expand...
Click to collapse
No it didn't.
Status 7 error.
Akhil said:
No it didn't.
Status 7 error.
Click to expand...
Click to collapse
do you replaced folders in google source by the same from opesnsource.samsung com ?
and why in i9500-vendor.mk you wrote
$(call inherit-product, vendor/htc/samsung/i9500-vendor-blobs.mk)
Click to expand...
Click to collapse
Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing, called “asserts”
You can delete this assert in updater-script to bypass this verification
did anyone brick there device from compiling error ?
S.a.M.e.R_d said:
did anyone brick there device from compiling error ?
Click to expand...
Click to collapse
oh, common.. Why you think device can be bricked by this? It won't. Just don't mess with boot block (and don't use engineering bootloader because it doesn't set boot block hardware write protection) and you always will be able to enter download mode and then flash whatever you want through Odin.
Introduction:
SiriusAOSP is meant to be a clean, performance packed version of AOSP. The ROM is essentially AOSP with added features I feel are necessary for an enjoyable experience. SiriusAOSP delivers (and always will) the latest version of AOSP with all the up-to-date security patches by Google.
Prerequisites:
Unlocked Bootloader
TWRP
Latest vendor.img from Google*
Latest bootloader.img from Google*
Latest radio.img from Google*
* - Optional but HIGHLY RECOMMENDED
Instructions for Installation:
Download latest ROM build
Reboot into TWRP
Make backup (optional)
Wipe Data/Cache/System and Factory reset (if coming from another ROM)
Wipe Cache (if updating from a previous build of SiriusAOSP)
Flash ROM
Flash GApps
Reboot
Feature List (for intial release): LINK
Changelog: LINK
Download: ROM | GAPPS
DONATE: PayPal Link
NOTE: Every donation motivated me and helps me to continue this project. If you like my work a donation is always appreciated
Honorable Mentions: Link to GitHub
JOIN THE GOOGLE+ COMMUNITY: View Community
Kernel Source: Link
ROM Source: Link
XDA:DevDB Information
[ROM][ANGLER][6.0_r26][MDB08M] SiriusAOSP [11/15/2015], ROM for the Huawei Nexus 6P
Contributors
Shawn5162
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Alpha
Created 2015-11-16
Last Updated 2015-11-15
Reserved
Reserved by OP
What gapps u using banks fail on most ROMs
Added to Nexus 6P index thread:
[INDEX] Huawei Nexus 6P
Thanks gonna give it a go and let you know
Since the 6P is already on an AOSP rom, is there really any reason to flash a custom rom? I'm thinking of flashing a custom rom but I don't understand why it's advantageous when you already have an AOSP stock rom.
jksyankeesrock said:
Since the 6P is already on an AOSP rom, is there really any reason to flash a custom rom? I'm thinking of flashing a custom rom but I don't understand why it's advantageous when you already have an AOSP stock rom.
Click to expand...
Click to collapse
apparently you don't understand the difference between Google factory image and AOSP builds
jksyankeesrock said:
Since the 6P is already on an AOSP rom, is there really any reason to flash a custom rom? I'm thinking of flashing a custom rom but I don't understand why it's advantageous when you already have an AOSP stock rom.
Click to expand...
Click to collapse
Stock Google is not at all stock AOSP, though it's the closest thing to AOSP out of the box...that stated, the similitudes are far more than their differences...but they are most definitely not the same.
AOSP is the open source repository to which Google and a number of other handset manufacturers contribute code, and from which all in turn avail.
But make no mistake, this device ships with proprietary software.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
---------- Post added at 09:26 PM ---------- Previous post was at 09:24 PM ----------
opz187 said:
apparently you don't understand the difference between Google factory image and AOSP builds
Click to expand...
Click to collapse
And yet you provided nothing but sarcasm...without a hint of humor.
I see no need to post comments such as this to a fellow forum member, irrespective of how his or her words irritate.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
micmars said:
Stock Google is not at all stock AOSP, though it's the closest thing to AOSP out of the box...that stated, the similitudes are far more than their differences...but they are most definitely not the same.
AOSP is the open source repository to which Google and a number of other handset manufacturers contribute code, and from which all in turn avail.
But make no mistake, this device ships with proprietary software.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
---------- Post added at 09:26 PM ---------- Previous post was at 09:24 PM ----------
And yet you provided nothing but sarcasm...without a hint of humor.
I see no need to post comments such as this to a fellow forum member, irrespective of how his or her words irritate.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
Click to expand...
Click to collapse
my apologies
opz187 said:
my apologies
Click to expand...
Click to collapse
I understand...hope you have a terrific week.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
Where's the Gapps for this
micmars said:
I understand...hope you have a terrific week.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
Click to expand...
Click to collapse
you too bud. great explanation BTW. I did come off snarky and offensive. completely agree, no reason to treat anyone in the community that way. jksyankee sorry bro
waco2hot33 said:
Where's the Gapps for this
Click to expand...
Click to collapse
Experiment
And ofc let me know which one works...All I know is the bAnKs GApps DO NOT WORK
Has anyone tried OpenGapps?
I couldn't get past setup.. I think it said something about Google services crashing. I used pure Nexus gapps.
Sent from my Nexus 6P using Tapatalk
opz187 said:
you too bud. great explanation BTW. I did come off snarky and offensive. completely agree, no reason to treat anyone in the community that way. jksyankee sorry bro
Click to expand...
Click to collapse
Nothing to do with the rom but this is such a nice apology it needed mentioning!
OK let me try this rom
Add the Issue Tracker link in the OP. There you can view current and resolved issues. Also I can confirm that there is a GApps issue...It should be fixed in today's/tomorrow's update.
is there a feature list of what it/will have?
Here is the feature list for the first SiriusAOSP release. View it here: https://docs.google.com/document/d/1hNao-Hfz_DKL2iR2m95vD-bSsE5cyIrGEveYB8dhp7o/edit?usp=sharing
micmars said:
Stock Google is not at all stock AOSP, though it's the closest thing to AOSP out of the box...that stated, the similitudes are far more than their differences...but they are most definitely not the same.
AOSP is the open source repository to which Google and a number of other handset manufacturers contribute code, and from which all in turn avail.
But make no mistake, this device ships with proprietary software.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
---------- Post added at 09:26 PM ---------- Previous post was at 09:24 PM ----------
And yet you provided nothing but sarcasm...without a hint of humor.
I see no need to post comments such as this to a fellow forum member, irrespective of how his or her words irritate.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
Click to expand...
Click to collapse
OK.my bad in regards to understanding that. But my question still stands - what advantages are there to installing a custom rom with pretty good software out of the box?
Dirty Unicorns just updated sources to Marshmallow.
XDA: Dirty Unicorns ROM Updated to Marshmallow, Brings Lots of New Features.
http://www.xda-developers.com/dirty-unicorns-rom-updated-to-marshmallow-brings-lots-of-new-features/
Would be nice if someone could port and build for Onyx.
As far as I know, it's based on CM13.
Thanks
+1
I was literally just abut to make a thread about this
---------- Post added at 12:34 PM ---------- Previous post was at 12:34 PM ----------
Please devs
Officially I read that they had no plans to support it
I would look into maintaining it myself but my rig needs new parts. Otherwise with my laptop even compiling a kernel from source takes forever
RJDTWO said:
Officially I read that they had no plans to support it
I would look into maintaining it myself but my rig needs new parts. Otherwise with my laptop even compiling a kernel from source takes forever
Click to expand...
Click to collapse
If you intend to support it officially, they would probably let you use their build server to release builds.
Just guessing. If you're really interested in supporting DU, you can ask them
Sent from my OnePlus X using Tapatalk
Calvin2394 said:
If you intend to support it officially, they would probably let you use their build server to release builds.
Just guessing. If you're really interested in supporting DU, you can ask them
Sent from my OnePlus X using Tapatalk
Click to expand...
Click to collapse
I'll look into that and see what I can do then
@RJDTWO So what's up? Did you ask them if you can use their servers?
Calvin2394 said:
@RJDTWO So what's up? Did you ask them if you can use their servers?
Click to expand...
Click to collapse
Doesnt look like ill be able to unfortunately. However the dev working on Tamesek is working on an unofficial build.
RJDTWO said:
Doesnt look like ill be able to unfortunately. However the dev working on Tamesek is working on an unofficial build.
Click to expand...
Click to collapse
that would be @rohitporoli
Subhrajyoti Sen said:
that would be @rohitporoli
Click to expand...
Click to collapse
I've kept that aside for now! Having the same issue regarding server! :/
So well, I booted DU for onyx.
To my surprise, all basic functions are working. RIL is working flawless too.
What's broken :-
Selinux (Needs work)
Tristate keys (Will fix them)
Rest all is working as it should atleast in my case, I will make a thread and post the build when I fix the above two things.
Don't ask for links please. I won't post untill I fix the stuffs.
Vatsal said:
So well, I booted DU for onyx.
To my surprise, all basic functions are working. RIL is working flawless too.
What's broken :-
Selinux (Needs work)
Tristate keys (Will fix them)
Rest all is working as it should atleast in my case, I will make a thread and post the build when I fix the above two things.
Don't ask for links please. I won't post untill I fix the stuffs.
Click to expand...
Click to collapse
You´re awesome man! Thank you so much!
Vatsal said:
So well, I booted DU for onyx.
To my surprise, all basic functions are working. RIL is working flawless too.
What's broken :-
Selinux (Needs work)
Tristate keys (Will fix them)
Rest all is working as it should atleast in my case, I will make a thread and post the build when I fix the above two things.
Don't ask for links please. I won't post untill I fix the stuffs.
Click to expand...
Click to collapse
Oh sweet. Will they let you make this official? They wouldn't let me use their servers for releases
RJDTWO said:
Oh sweet. Will they let you make this official? They wouldn't let me use their servers for releases
Click to expand...
Click to collapse
No official sorry. I don't wish to apply for official.
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"/>