Database Users

Tutorial on compiling AOSP 2.X for the HTC hero

Hey everyone, well, ironically, I'm asking for help . I've wanted to create a AOSP ROM, but I can't find a guide on getting AOSP to the Sprint Hero. Is there a step by step guide for compiling it, with all the config files needed? Thanks, I really would appreciate it, and I'm sure you'll appreciate the future ROM's of mine too .

EXTREMELY tempted to post a lmgtfy

justinisyoung said:
EXTREMELY tempted to post a lmgtfy
Click to expand...
Click to collapse
Uhh... I will literally scream if it's on google. I went through, so many pages googling it. I have compiled android before, yes. But not for the hero.

This is what i have been trying to make work.
http://android.modaco.com/index.php?s=&showtopic=301857&view=findpost&p=1179830
Its only a peice of the puzzle. I havent been able to do much with it, I wasnt able to find where I needed to shove libcamera for our hw to get past an error.

PM Darch....

kkruse said:
This is what i have been trying to make work.
http://android.modaco.com/index.php?s=&showtopic=301857&view=findpost&p=1179830
Its only a peice of the puzzle. I havent been able to do much with it, I wasnt able to find where I needed to shove libcamera for our hw to get past an error.
Click to expand...
Click to collapse
what make errors have you been receiving. sometimes when you compile using that vendor tree some of the libs don't get pushed into the target.

I posted a "vendor overlay" ZIP for our CDMA hero elsewhere on this site (it's the LoX GSM hero overlay with edits for heroc plus some extra libs, etc, for 2.1), I was initially hoping for some feedback on it from some of the other devs. I was having the same issues darch mentions where some of the files don't copy over during the build so you just have to copy them into the target as the errors come up. Search my userID plus "vendor" and "voodoo" and it should come up.

5tr4t4 said:
I posted a "vendor overlay" ZIP for our CDMA hero elsewhere on this site (it's the LoX GSM hero overlay with edits for heroc plus some extra libs, etc, for 2.1), I was initially hoping for some feedback on it from some of the other devs. I was having the same issues darch mentions where some of the files don't copy over during the build so you just have to copy them into the target as the errors come up. Search my userID plus "vendor" and "voodoo" and it should come up.
Click to expand...
Click to collapse
you could do that to fix it... or we can fix the unzip scripts, because that is the root of all the problems in which the camera libs aren't making it to the target.
Btw, i'm gunna check out your vendor overlay. sounds like it'll help people compile cyanogenmod a bit more eaily.

darchstar said:
you could do that to fix it... or we can fix the unzip scripts, because that is the root of all the problems in which the camera libs aren't making it to the target.
Btw, i'm gunna check out your vendor overlay. sounds like it'll help people compile cyanogenmod a bit more eaily.
Click to expand...
Click to collapse
I never investigated it very deeply. If you know it's the unzip step, that would be great to have it fixed. BTW, there two extract-files.sh in my overlay, one that pulls needed files from the device, and another that pulls them from a ROM (came in handy at one point). I'm still not clear about how much variability there is with libs, etc, from version to version, you would know better.
Finally, the kernel zImage included is just Toast's .29 that I built from scratch the day I posted the overlay. There's probably a newer version now...and I assume you can just package with your own boot.img anyway.

darchstar said:
what make errors have you been receiving. sometimes when you compile using that vendor tree some of the libs don't get pushed into the target.
Click to expand...
Click to collapse
sorry to leave ya hanging but I just checked in... let me recompile it again and see.... Ill probably have the results back in the AM. Too tired now

dev activity

this is not to rush the devs, just asking, are they gonna wait till ( i really hope it actually hapens) jb update comes to us to start developing? couse i think our phone haves a lot more to give to us than the stock rom can, again i am not rushing the devs, just asking your oppinion, and since im kinda new to theese forums hardly think any dev is going to bother to even answer this thread
so im pretty much.asking your oppinion
this is just a question , please dont kill me
sent from the gray stuff inside my skull

demonoid phenomenom said:
this is not to rush the devs, just asking, are they gonna wait till ( i really hope it actually hapens) jb update comes to us to start developing? couse i think our phone haves a lot more to give to us than the stock rom can, again i am not rushing the devs, just asking your oppinion, and since im kinda new to theese forums hardly think any dev is going to bother to even answer this thread
so im pretty much.asking your oppinion
this is just a question , please dont kill me
sent from the gray stuff inside my skull
Click to expand...
Click to collapse
If you mean Custom Roms... we can't do anything until we can pack / unpack the boot.img/or recovery.img to make a custom recovery.

jeah thats right, i was wondering because my expirience with atrix 2 , previous to the ics update, i was using supercharger rom series, but again i understand that they got a leak to work on, and a bootstrap to flash the restores they where creating, and that stock leaked rom was awesome
sent from the gray stuff inside my skull

mattlgroff said:
If you mean Custom Roms... we can't do anything until we can pack / unpack the boot.img/or recovery.img to make a custom recovery.
Click to expand...
Click to collapse
Only for my own curiosity: what's prevents that ? The x86 arch ? or something else ?

Le_Poilu said:
Only for my own curiosity: what's prevents that ? The x86 arch ? or something else ?
Click to expand...
Click to collapse
Would be nice to know for sure. The current methods cannot find 'Android Magic'.

I'm looking forward to seeing this forum get some custom ROMs too...

Looks like progress is getting on with it now

Any updates on custom ROM making for this device?
I've followed the README from <link to Motorola's sourceforge for razr i, deleted because I'm a new user> , got to the final step, but now I'm stumped. What make target should I choose? 'make full_x86-eng' and 'make generic_x86' have no make rules. A simple 'make' generates a framework build error.
What do I have to do in order to get a bootable image (built from source) for the Razr i?
I'd appreciate any kind of advice. Thanks in advance.
PS: Many thanks Matt, turl1 and the other developers that worked on this device.

tiberiu24 said:
Any updates on custom ROM making for this device?
I've followed the README from <link to Motorola's sourceforge for razr i, deleted because I'm a new user> , got to the final step, but now I'm stumped. What make target should I choose? 'make full_x86-eng' and 'make generic_x86' have no make rules. A simple 'make' generates a framework build error.
What do I have to do in order to get a bootable image (built from source) for the Razr i?
I'd appreciate any kind of advice. Thanks in advance.
PS: Many thanks Matt, turl1 and the other developers that worked on this device.
Click to expand...
Click to collapse
You won't be able to build a full android system from that source. The most you can do is
Code:
$ . build/envsetup.sh
$ lunch generic_x86-eng
$ make [I]target[/I]
Where target is something like out/target/product/generic/system/bin/bluetoothd or bluetoothd

I am working on a device tree. Writing it from scratch isn't easy because there is no device I can base this on. No other x86 tree out there. And I still dont have a device. I did make threads requesting for a device but they got closed down. So once I have something built I'll make a new thread.
Sent from my GT-I9300 using xda app-developers app

hiemanshu said:
I am working on a device tree. Writing it from scratch isn't easy because there is no device I can base this on. No other x86 tree out there. And I still dont have a device. I did make threads requesting for a device but they got closed down. So once I have something built I'll make a new thread.
Click to expand...
Click to collapse
There's at least 10 device trees on the android-x86 project. And AOSP itself has a generic one, to build the x86 emulator platform. And I made a basic one to build recovery already, with support to generate the newer x86 boot image format.
Just saying
PS: I don't own the phone either

turl1 said:
There's at least 10 device trees on the android-x86 project. And AOSP itself has a generic one, to build the x86 emulator platform. And I made a basic one to build recovery already, with support to generate the newer x86 boot image format.
Just saying
PS: I don't own the phone either
Click to expand...
Click to collapse
Generic x86 and the razr I are too far apart. Also the android x86 ones are too far apart too (I am working on a android x86 tablet). I have already written more than 450 lines of the device tree by hand, and there is a lot more to go right now. I have patched bionic for x86 builds, I need to patch the build folder next, and even busybox needs patching, etc. I am now working on making a perfect set of the 3 important files, BoardConfing.mk, device.mk and proprietary-files.txt. My android x86 tree is a total of 181 lines (which in itself is twice the size of the trees on android-x86). Its fun, but really time consuming. Also the AOSP ones are generic ones, they will work on any system if you have all the correct drivers installed or compiled via the kernel, but Razr I needs the files to be pulled from the stock build, and it needs a lot of them, including kernel drivers.
-H

hiemanshu said:
Generic x86 and the razr I are too far apart. Also the android x86 ones are too far apart too (I am working on a android x86 tablet). I have already written more than 450 lines of the device tree by hand, and there is a lot more to go right now. I have patched bionic for x86 builds, I need to patch the build folder next, and even busybox needs patching, etc. I am now working on making a perfect set of the 3 important files, BoardConfing.mk, device.mk and proprietary-files.txt. My android x86 tree is a total of 181 lines (which in itself is twice the size of the trees on android-x86). Its fun, but really time consuming. Also the AOSP ones are generic ones, they will work on any system if you have all the correct drivers installed or compiled via the kernel, but Razr I needs the files to be pulled from the stock build, and it needs a lot of them, including kernel drivers.
-H
Click to expand...
Click to collapse
I'm playing a bit with AOSP 4.2 as I got some free time. This is what I found out so far:
bionic needed no patches. I seriously doubt it needs any on 4.1 (CM) either as recovery built fine.
build needed no patches either on both cases.
dalvik needed a 4-liner to build on AOSP (makefile fixes), I haven't tried to build it on CM
there's no busybox on AOSP, I patched the one on 4.1 already to be able to build recovery, it's all on CM Gerrit as you'd expect from a CM developer like myself
my tree is already 120 lines, as soon as you add the media decoder config and audio routing config you'll go over 180 lines
having proper drivers isn't enough, you need proper HALs too. And I haven't really looked, but I'd be surprised if you had to pull kernel drivers from the stock rom

turl1 said:
I'm playing a bit with AOSP 4.2 as I got some free time. This is what I found out so far:
bionic needed no patches. I seriously doubt it needs any on 4.1 (CM) either as recovery built fine.
build needed no patches either on both cases.
dalvik needed a 4-liner to build on AOSP (makefile fixes), I haven't tried to build it on CM
there's no busybox on AOSP, I patched the one on 4.1 already to be able to build recovery, it's all on CM Gerrit as you'd expect from a CM developer like myself
my tree is already 120 lines, as soon as you add the media decoder config and audio routing config you'll go over 180 lines
having proper drivers isn't enough, you need proper HALs too. And I haven't really looked, but I'd be surprised if you had to pull kernel drivers from the stock rom
Click to expand...
Click to collapse
1) bionic needs patching, patch already submitted to CM gerrit libdvm basically
2) build needs patching for the boot.img
3) dalvik has been patched
4) Odd, didn't notice that
5) Probably wont required pulling in kernel drivers, but would required pulling in the correct drivers for the defconfig
I'd be happy if you wanted to work together to get this working. PM me

hiemanshu said:
1) bionic needs patching, patch already submitted to CM gerrit libdvm basically
2) build needs patching for the boot.img
3) dalvik has been patched
4) Odd, didn't notice that
5) Probably wont required pulling in kernel drivers, but would required pulling in the correct drivers for the defconfig
I'd be happy if you wanted to work together to get this working. PM me
Click to expand...
Click to collapse
Let's continue talking on PM then
re. 2, I actually did need to patch build on AOSP after all . CM on the other hand, has BOARD_CUSTOM_BOOTIMG_MK from the tf tablets.

Hey I posted a rom over at droidrzr.com for use till aosp is ready. This should be enough till we get a jb leak
Sent from my XT890 using Tapatalk 2

Hi Folks
While I don't own a RAZR I , I have been Jaffing around with building CM10.1 and AOSP for x86, I've been getting in going on my FX8120, just need to sort the OpenGLES MESA drivers out.
Anyways I've got CM10.1 built for x86 using the mr1-staging branch ( I think it's been merged to cm10.1 ) and an edited mini-x86 device tree .
Busybox was a B**stard to build though, although on one of the branches there is an .config-minimal-x86 .config-full-x86, still needed tweaking tho.
I submitted my patches http://review.cyanogenmod.org/#/c/27377/ and http://review.cyanogenmod.org/#/c/27373/, however It seems x86 isn't top of cm's agenda.... or I'm missing something about assigning reviewers.
Obviously a base x86 build is only part of the story for you guys as you'll face all the regular problems that emedded devices have, not checked the specs for the RazR but I'm sure there's some binary blobs in your future,
Hack On Folks! :good:

Media-Caf Error

So now I am getting the below error while compiling Omni ROM:
hardware/qcom/media-caf/mm-video/vidc/venc/src/video_encoder_device.cpp:2450:17: error: 'struct venc_entropycfg' has no member named 'longentropysel'
Full Log:
http://hastebin.com/kudarekaqo.vhdl
Please help me in killing this last error

https://gerrit.omnirom.org/#/c/2940/
You need the equivalent of this patch for your kernel.

tilal6991 said:
https://gerrit.omnirom.org/#/c/2940/
You need the equivalent of this patch for your kernel.
Click to expand...
Click to collapse
The commit you shared seems to be related to Sony. I am building for AT&T Samsung Galaxy S3. So will that be applicable, if yes how to integrate the same into my setup considering Omni does not support AT&T S3

matrixzone said:
The commit you shared seems to be related to Sony. I am building for AT&T Samsung Galaxy S3. So will that be applicable, if yes how to integrate the same into my setup considering Omni does not support AT&T S3
Click to expand...
Click to collapse
That's why I said equivalent of that commit. If you make the same changes as was made in that change the error should be fixed.

tilal6991 said:
That's why I said equivalent of that commit. If you make the same changes as was made in that change the error should be fixed.
Click to expand...
Click to collapse
thanks man. How to see the code change from gerrit, checking the code change in github is very easy

Go to Omni github, find android_kernel_sony_msm8960 project, switch to android-4.4 branch, click on commits and scroll down until you find Nov 29.

chasmodo said:
Go to Omni github, find android_kernel_sony_msm8960 project, switch to android-4.4 branch, click on commits and scroll down until you find Nov 29.
Click to expand...
Click to collapse
In this particular case - look at the files changed by the commit and pull up the commit history for one of them - saves a lot of time.

Although, to be honest, we need to move to the fixed patch rather than continuing to revert kernels in this case.
We should have just fixed the remaining broken devices two weeks ago, oh well.
As to it appearing to be "sony" specific - keep in mind that many patches are merely "qualcomm specific" and apply to any Qualcomm-based device. This is one of them.

Entropy512 said:
Although, to be honest, we need to move to the fixed patch rather than continuing to revert kernels in this case.
We should have just fixed the remaining broken devices two weeks ago, oh well.
As to it appearing to be "sony" specific - keep in mind that many patches are merely "qualcomm specific" and apply to any Qualcomm-based device. This is one of them.
Click to expand...
Click to collapse
Also qcom devices that has "TARGET_QCOM_MEDIA_VARIANT := caf" in BoardConfig
I said that cause there are qcom devices that can work with no caf repos tbh..
An example would be Sony fusion3 devices.....
They worked on our android-4.4 branches perfectly fine prior to the qcom-4.4_2.7 merge
And fusion3 OmniROM/CyanogenMod Nightlies don't use any of the caf repos tbh . Though AOKP does

[DEV] CM10.1 builds | help needed adding features | "4.2.2 Revival Team"

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.

Stock AOSP Oreo on Mate 9

https://www.xda-developers.com/stock-android-oreo-huawei-mate-9-project-treble/amp/

wmfreak said:
https://www.xda-developers.com/stock-android-oreo-huawei-mate-9-project-treble/amp/
Click to expand...
Click to collapse
Let's hope more to follow.

His latest update has me super excited. He says it's now fully functional. Awesome work!!

Not quite fully functional
moxiot said:
His latest update has me super excited. He says it's now fully functional. Awesome work!!
Click to expand...
Click to collapse
I read the article along with the update, It's not quite fully functional, still quite a ways from being a working rom but he has shown that project treble does work and is somewhat viable. from looking at his screenshots the ril (sim stuff) is not working yet, I made some suggestions to him regarding his build that might fix that but he hasn't gotten back to me. Still not there yet but at least it shows that a generic AOSP Android can be installed and booted (at least the system and data images) by virtue of project treble. There are still a lot of things that are closed source relating to the hardware on our device and the SoC itself.

NFC not working, BT is wonky, FPS is not enabled, Keyboard is crashing when opening numbers/special chars, no HotSpot/Tethering, RIL does somewhat work but requires some more work on the actual device overlay.
But the essential things are working, Video Enc/Dec, Camera (Video, Photo), LEDs, Audio, HWC, vulkan, WiFi, BT (atleast its visible when i scan for it), power hal, maybe i forgot a few things ..
I've tested a self-compiled build on my H8 Pro, and thats the result, so i'd expect some similar situation for the Mate 9.
Regards

OldDroid said:
NFC not working, BT is wonky, FPS is not enabled, Keyboard is crashing when opening numbers/special chars, no HotSpot/Tethering, RIL does somewhat work but requires some more work on the actual device overlay.
But the essential things are working, Video Enc/Dec, Camera (Video, Photo), LEDs, Audio, HWC, vulkan, WiFi, BT (atleast its visible when i scan for it), power hal, maybe i forgot a few things ..
I've tested a self-compiled build on my H8 Pro, and thats the result, so i'd expect some similar situation for the Mate 9.
Regards
Click to expand...
Click to collapse
Thanks for the report. Let's hope to see a stable build in the near future.

AOSP
OldDroid said:
NFC not working, BT is wonky, FPS is not enabled, Keyboard is crashing when opening numbers/special chars, no HotSpot/Tethering, RIL does somewhat work but requires some more work on the actual device overlay.
But the essential things are working, Video Enc/Dec, Camera (Video, Photo), LEDs, Audio, HWC, vulkan, WiFi, BT (atleast its visible when i scan for it), power hal, maybe i forgot a few things ..
I've tested a self-compiled build on my H8 Pro, and thats the result, so i'd expect some similar situation for the Mate 9.
Regards
Click to expand...
Click to collapse
Did a build myself for the HiKey 960 reference board that uses the same SoC as the mate 9 and am doing a generic arm64 build right now, I'll be testing the both out when I get a chance. I think that I might have a little more luck with the HiKey build as it is the same SoC. It's a work in progress but project treble is showing some promise. I'm looking at making a flashable (in twrp) that will install the AOSP build (whichever one works)

revjamescarver said:
Did a build myself for the HiKey 960 reference board that uses the same SoC as the mate 9 and am doing a generic arm64 build right now, I'll be testing the both out when I get a chance. I think that I might have a little more luck with the HiKey build as it is the same SoC. It's a work in progress but project treble is showing some promise. I'm looking at making a flashable (in twrp) that will install the AOSP build (whichever one works)
Click to expand...
Click to collapse
Thanks my dear friend for your work and interest on our beloved Mate 9.

Thanks
albertobom said:
Thanks my dear friend for your work and interest on our beloved Mate 9.
Click to expand...
Click to collapse
You are very welcome, this all is a work in progress but from what I see so far project treble is going to make development easier in the future. I might try installing the boot image from my HiKey build to see how that works, it's the same SoC as our devices so it "should" boot, it's kernel version 4.9 which is the latest and supposedly greatest so we will see. If it doesn't boot I can always flash back the stock Oreo boot image.

I got a spare Mate 9 and can install and test stuff, happy to help

I'll keep that in mind
Exelios said:
I got a spare Mate 9 and can install and test stuff, happy to help
Click to expand...
Click to collapse
I'll keep that in mind, I will be uploading my system.img and custdata.img for both builds when this one gets finished (takes forever on my old PC) they can be flashed via fastboot provided your bootloader is unlocked. I'll post the links after I get them uploaded.

revjamescarver said:
I'll keep that in mind, I will be uploading my system.img and custdata.img for both builds when this one gets finished (takes forever on my old PC) they can be flashed via fastboot provided your bootloader is unlocked. I'll post the links after I get them uploaded.
Click to expand...
Click to collapse
Sounds good, yes my device is unlocked and on Oreo beta with oreo TWRP and everything, I'm not new to this

revjamescarver said:
I'll keep that in mind, I will be uploading my system.img and custdata.img for both builds when this one gets finished (takes forever on my old PC) they can be flashed via fastboot provided your bootloader is unlocked. I'll post the links after I get them uploaded.
Click to expand...
Click to collapse
Only progress on this?

Rebuilding
tiennemannes said:
Only progress on this?
Click to expand...
Click to collapse
I'm rebuilding, there is a thread on AOSP here https://forum.xda-developers.com/project-treble so I'm following the work there to see what changes to the framework need to be made, my build hung at 99% so I ended up starting it over, I think my build machine is running out of memory and the Java compiler is chocking. his v2 build boots and is mostly functional you can download it on his thread. His build is based on the 8.0.0-vts_r4 testing branch and mine is the 8.0.0_r34 release branch. You can download a build based on his changes and the vts branch here https://drive.google.com/file/d/1wMa_dgkWrqbC9i4GxUNOQlH0qIwffPph/view?usp=drivesdk

revjamescarver said:
I'm rebuilding, there is a thread on AOSP here https://forum.xda-developers.com/project-treble so I'm following the work there to see what changes to the framework need to be made, my build hung at 99% so I ended up starting it over, I think my build machine is running out of memory and the Java compiler is chocking. his v2 build boots and is mostly functional you can download it on his thread. His build is based on the 8.0.0-vts_r4 testing branch and mine is the 8.0.0_r34 release branch. You can download a build based on his changes and the vts branch here https://drive.google.com/file/d/1wMa_dgkWrqbC9i4GxUNOQlH0qIwffPph/view?usp=drivesdk
Click to expand...
Click to collapse
Thanks. Can you confirm Galileo satellites are being picked up with AOSP Oreo? Should see EU flags in https://play.google.com/store/apps/details?id=com.android.gpstest
See stock ROM results at http://www.startlr.com/we-tried-galileo-huawei-mate-9-already-sees-the-european-satellites/

Galileo
tiennemannes said:
Thanks. Can you confirm Galileo satellites are being picked up with AOSP Oreo? Should see EU flags in https://play.google.com/store/apps/details?id=com.android.gpstest
See stock ROM results at http://www.startlr.com/we-tried-galileo-huawei-mate-9-already-sees-the-european-satellites/
Click to expand...
Click to collapse
Haven't tried it out, it's supposed to but I'll have to check that out, there was a report of taking a very long time to get a fix off GPS, but nothing specific to Galileo.

revjamescarver said:
Haven't tried it out, it's supposed to but I'll have to check that out, there was a report of taking a very long time to get a fix off GPS, but nothing specific to Galileo.
Click to expand...
Click to collapse
Yeah, saw the same (that's why I'm curious).

AOSP
tiennemannes said:
Yeah, saw the same (that's why I'm curious).
Click to expand...
Click to collapse
Yeah, the whole ASOP and treble thing is definitely a work in progress and it's going to take a little time to get that all working with the phone hardware properly but once it gets all figured out it is going to make updates easy and open the door to a lot of possibilities with custom ROMs

revjamescarver said:
Yeah, the whole ASOP and treble thing is definitely a work in progress and it's going to take a little time to get that all working with the phone hardware properly but once it gets all figured out it is going to make updates easy and open the door to a lot of possibilities with custom ROMs
Click to expand...
Click to collapse
Indeed, this stuff is exciting. My mate 9 should arrive tomorrow.... Can't wait.
Is the kernel compiled too from AOSP, or is that pre-compiled already in a boot.img?

Kernel
tiennemannes said:
Indeed, this stuff is exciting. My mate 9 should arrive tomorrow.... Can't wait.
Is the kernel compiled too from AOSP, or is that pre-compiled already in a boot.img?
Click to expand...
Click to collapse
No, in order to use the AOSP build you have to install Oreo beforehand, there are beta builds available for a few of the mate 9 variants right now but the "official" Oreo updates should start rolling out sometime in December. I had downloaded and installed the beta for the US variant.