yashsingh1/xdaforums huggingface dataset:
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Thanks for the log provided in PM - I have now understood the issue:

The crash happens here as a so-called "NullPointer" exception, because the attribute "installerPackageName" seems to be empty in your case. (I have taken over that commit from Iodé OS to improve app compatibility, as some poorly designed apps start to misbehave, if they think, that they haven't been installed from the play store).

Normally, the attribute "installerPackageName"

always

has a value - I was able e.g. on my own device to uninstall aurora store and install again.

There seem however to be rare cases, where this value is empty - in my next build, I will include a null check before using the equals operator.

To work around your issue, please try the following command in adb - it could however fail as well, if the system attempts to read the current package name before assigning a new one, so if it works, be happy, if not, you'll have to wait for my next update:

pm set-installer com.aurora.store com.aurora.store
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] P9_User:
Will do as soon I am back home. Anyway hats off for your investigation, explainations and update service. I am a simple user but this helps me to understand things better.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] P9_User:
Hi. Busy times...

Did the command via terminal (adb did not like to do pm) and I think it failed.

Security exception: Unknown calling UID: 0

Followed with some Java things: Unknown calling UID: 0

And so on...

Will wait for your next built.

Greetings. P9
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Gabriel7376363:
Still updated?! Wow amazing creator who still support this device
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
New build with backported July '24 ASB patches available

Hi all,

a new build is available for download (update instructions, see OP):

https://sourceforge.net/projects/lin16-microg/files/treble_p9eva/treble_arm64_a_lineage16_20240717_system.img/download

Custom build release 2024-07-01

Fix of the app uninstall crash discussed last month

General information - please read carefully:

The /system partition of the P9 device is quite small with its ~1.8GB - due to mainly the meanwhile extraordinarily large size of the Webview component, I am faced with space restrictions in each build, which I can only overcome by either not any more shipping specific apps or, if that is not possible, by shipping older versions, which still fit, but you as a user must update them afterwards.

I have updated a comprehensive info in the OP, the main points are (again) listed below:

1. Mulch System Webview

The shipped version is from February '24 and hence outdated. Please configure the DivestOS F-Droid repository in F-Droid and always apply the offered updates accordingly, whenever available.

2. AuroraStore

Please download / install (and also update!) the AuroraStore always from here. (After initial setup, you should change the installation method to "AuroraServices", despite this being shown as "outdated") - the most recent version is 4.5.1, I recommend to update now.

3. microG updates

With its most recent release 0.3.2, also microG app size has significantly grown and caused this time a size exceeded issue during build. microG is shipped in version 0.3.0 and I recommend to update. Its main component is signed with the platform key of this build, so it can't be updated via F-Droid.

To keep microG current, please proceed as follows:

Check, if you have already version 0.3.2.x - only if your version is lower, download and install the latest GmsCore*.apk from here

Activate the microG F-Droid repository in F-Droid (if not done, yet)

Update the "microG Companion app" to the same version as the microG main component (you need to manually select the version, ignore the "recommended version")

4. microG advice

Quote from this issue: https://github.com/microg/GmsCore/issues/2237

"If you are using microG 0.3.2, you can configure https://api.positon.xyz/?key=74600654-2aec-11ef-aa95-3b7218da6865 as an API endpoint in microG Settings -> Location -> ⋮ -> Configure service URL."

Happy flashing - M.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] NervReaper:
SafetyNet it's ok for you? Last time I've tried phh-treble, i didn't make it pass. Safety net and the battery drain are the only reasons cause i prefer stock over GSI.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Wattsensi:
Yeah. On the P9. EVA-L09. Firmware 8.0.0.540 Patch02. Oreo vendor. Hotspot working, on Phh-Treble v119 downloaded from the release tag. I don't have enough computer power to build Android for ARM64 myself, unfortunately

---------- Post added at 15:58 ---------- Previous post was at 15:52 ----------

Unfortunately I know no way to get it to pass myself.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] zgfg:
Spoof props from the official EVA-AL10c00b550:

https://xdaforums.com/showpost.php?p=83338777&postcount=3921

Use e.g. MHPC Magisk module (that thread is about).

Use its option for fingerprint and navigte to Huawei P9 Android 8 b550 (or how is it named there) for the above fingerprint and sec. patch date.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Wattsensi:
Solve the battery drain by disabling USB debugging, it's broken on Android and I can't debug it either.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
New build with September 2020 ASB patches

Hi all,

a new build is available for download (install instructions, see OP):

https://sourceforge.net/projects/li..._a_lineage16_20200912_system.img.zip/download

ASB Security string 2020-09-01

Bromite Webview on 85.0.4183.86

Added eSpeak TTS engine (FOSS TTS solution)

Added P9 overlay with proper power profile & battery stats (thanks [MENTION=9152969]Wattsensi[/MENTION])

If you make sure to switch off 'Android debugging', when you don't need it, the device now has a good battery behavior.

The only still open issue known to me is the WiFi Hotspot (still working on it).

Happy flashing, regards, M.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] NervReaper:
Doesn't work for me. I flash Andy Yan's LOS 16 and did what you said, even try some tips from here unsuccessfully. ctsProfile and basicintegrity shows as false.

---------- Post added at 01:07 AM ---------- Previous post was at 12:56 AM ----------

I tried this Andy Yan's LOS 16 unofficial build today from this thread and Wifi Hotspot works perfectly (tested using my laptop).
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] zgfg:
I looked to what you linked. I'm not familiar with GSI but your system is not read-only hence you don't need systemless changes - you can setup the props by:

https://play.google.com/store/apps/details?id=by4a.setedit22

or simply from Terminal, with su:

setprop ro.build.fingerprint HUAWEI/EVA-AL10/HWEVA:8.0.0/HUAWEIEVA-AL10/550(C00):user/release-keys

setprop ro.build.version.security_patch 2020-07-01

setprop ro.product.model EVA-AL10

As that, it should be permanent and not depending on timing issues at boot

Maybe it needs one or two more props but at the end, passing Safety Net if no suspicious modules are installed, depends only on spoofing the props

Check them upon rebooting, to make sure they were actually applied:

getprop ro.build.fingerprint

getprop ro.build.version.security_patch

getprop ro.product.model
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] md sabuj:
Thanks
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
I have double-checked the v119 build indicated by [MENTION=9152969]Wattsensi[/MENTION] with the exact build manifest and could not see any forgotten patch. I have had two suspicions with vendor/interfaces and vendor/vndk, where I tried to revert some commits, but no success. Also tried to look at the logs, but no obvious entries (except for the entries stating that the AP interface could not be established).

So for me, two possible reasons remain:

- The v119 is one year old, so maybe Andy Yan has some additional patch (will check later)

- One of my additional specific hardening measures needs some adaptation in regards to the treble/vendor setup

As said, any hint appreciated, so if one of you detects something in the logs and has any idea, I'll be grateful.

(E.g., I tried already, what [MENTION=9152969]Wattsensi[/MENTION] did with the overlay, but I was too impatient, and did not wait at least 45 minutes to let the battery stat build up and thought it would not work after ten minutes and reverted again. Only because he said it worked, I let it for some hours on my device for testing purposes, and it finally worked.

So maybe I have also overlooked something obvious in regards to the hotspot, when looking into the logcat...?)
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] dkionline:
Settings open too slow, dont know what happens.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Not with my P9; only issue I have with this ROM is the nonfunctional hotspot.

EDIT: Finally, the Hotspot issue is solved, will work in my next build
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Nightwish1976:
Hi.

I'm trying to add a Google account to my Outlook for Android and I'm getting an error message like: "Adding accounts is not available now". It allows me to add non-google accounts.

Any idea what can I do?

LE: I managed to do it, just ignore the previous message.

PS: thank you for this ROM, the user experience is superior to everything else I tried recently.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
[MENTION=9152969]Wattsensi[/MENTION]: Good news - I managed to fix the wifi hot spot issue - in the next build it'll work :highfive:

EDIT: [MENTION=9350973]All[/MENTION] - is there interest to upload a new build before the next regular build with October ASB patches included?

New features would be:

- Fixed WiFi hot spot

- Updated microG version with Exposure Notification API (would allow to run Covid tracing apps making use of that API)
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] xaweryp:
EDIT: [MENTION=9350973]All[/MENTION] - is there interest to upload a new build before the next regular build with October ASB patches included?

[/QUOTE]

This issue was actually blocking me from using it as a daily driver so great to hear it's gone now! :)

Would that fix also potentially apply for Lineage 17 as well? If got it right - on 17th the camera is still an issue, right?
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Nightwish1976:
That's great news indeed, especially about the hotspot.

Regarding the new build, I'm sure you know better when you have the time to work on this.

I have some issues with my phone. I'm pretty sure they aren't ROM related, but I would like to read your opinion on this anyway.

So, on this ROM, there is a large number of apps not available for my device on the Aurora Store. You mentioned something about Google doing google things to Aurora Store, but I think is more than that. I downloaded an app called Family Link for Parents (by Google). I've installed it and, when I opened it, I received the message "Family Link is no longer supported on Android 4.4 (Kitkat)".

I'm sure it's not connected to your ROM, as exactly the same thing happened while I was on the Havoc OS GSI (Android 10). That particular app had the same behaviour and, similarly, a lot of apps were not available for my P9 on Google Play .

So, I'm not sure what to do. What on my phone tells apps and app stores that the phone is running Kitkat? Is it related to the vendor? To the fact I have TWRP installed and no encryption?

I would like some opinions...
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Wattsensi:
Nice! Now all we need to fix is the USB debugging, it currently is activated automatically on every boot and hogs all the CPU, and doesn't work.

Oh and include the NFC fixes so it works out of the box please. By doing that, you will finish the perfect daily driver ROM for this unfortunate device.

October is a few days ahead, I'm sure they can wait. You should just prepare the October build for now.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
In fact, there are multiple things to look at:

1. AuroraStore in general

Google is continuously evolving their PlayStore infrastructure, and apps like AuroraStore need to be maintained to cope. There are some slight "glitches" sometimes to work around . . . (see own AuroraStore support thread or their Telegram chat)

2. AuroraStore on GSI builds

For whatever reason, on GSI builds, AuroraStore behaves worse - also on my P9, I can't find some apps, which are no problem on my other devices. I don't have a good solution for that, except for obtaining them alternatively (e.g. extract from other device, or APKmirror.com, ...)

3. Installed apps on this build

Once the app has been installed, the job of AuroraStore is done. So if an app behaves weird after install, it is related to the app and the environment, in which it finds itself.

This build for example has microG installed, and not the original Google Play services (I tend to call them Spy-Services, as this reflects the reality better). microG aims at providing compatibility to apps having Google play dependencies (for example, push messaging), but it is not designed and also not able to cover everything of the original Play services - this is partly intended (as nobody really needs all the advertising infrastructure and Spyware of the genuine Play services), and partly too difficult to achieve (Play services are closed source and difficult to reverse-engineer).

Especially apps directly developed by Google usually deeply integrate with the Play services and often expect to find the full range of play services functionality. So if a Google-developped app complains, I would not be too surprised.

It could therefore be (but I don't know), that the "KitKat" message is simply the result of the lack of a certain API function, this app is expecting to find on the device. Or the result of bad programming: if some check fails and instead of giving the proper details of the issue, the developer has made an "assumption" that "such things could only be possible in KitKat" . . .
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
??? - Not on my P9. USB debugging just works fine and when I switch it off, it remains switched off, also after reboot.

Could you please provide more details?

Honestly, I haven't tested NFC, yet - will do. But what NFC fixes are you talking about? Where could I find "the NFC fixes" ?

Usually ("usually" means: don't take it for granted!), Google publishes their ASB in the afternoon (Western US time zone) of the 1st Monday each month - that would be the 5th October 2020 next time.

Usually, one or two days later, the tags and source code links are published (rarely, it could take a couple of days longer).

Give it another day until the patches are picked and uploaded to the LineageOS Gerrit by the LineageOS community, from where I finally could pick them and do my own test builds.

This effectively means - that the earliest you could see an updated build with October ASB patches would be around the 10th October - assuming all goes well and - more important - I find the time . . .

(So this is no ETA! Just for information to better understand the context)
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Wattsensi:
On my P9 it doesn't work. adb devices reports no permissions for me. It is well configured, I use it everyday on other devices. It doesn't hog CPU unlike Phh-Treble AOSP 9.0 though. Perhaps it's your newer build though.

This fix, it pretty much adds some permissions, tells the framework to expose NFC and installs an APK along with some binary blobs.

https://xdaforums.com/showpost.php?p=81021365&postcount=26

---------- Post added at 13:41 ---------- Previous post was at 13:35 ----------

Flash the amend patch for GSI ROMs. This takes care of that. Phhusson-based GSI ROMs all lack a necessary system file detailing Play Store app compatibility so they're all missing. You need to re-add it by flashing my amend patch on top of the ROM. It also fixes Bluetooth settings.

/system/etc/sysconfig/features_eva.xml

Credit: [MENTION=5173428]lo_ol[/MENTION]

[MENTION=7929484]MSe1969[/MENTION] Please study this ZIP and add some changes into your ROM so offline charging, NFC and Aurora Store catalog can work out of the box

https://drive.google.com/drive/folders/1rpCeajjRfozMrTBgSvKELgtb9GwOeXfh
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Nightwish1976:
[MENTION=9152969]Wattsensi[/MENTION] Already installed the patch, I'm sure it helps with different things, but not this issue..
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
First of all, thanks for this - I will have a look and yes, whatever would be missing and prove useful, I'll of course add. :good:

Now, while having seen the ZIP files on the one hand side, and also reading this and some older statements from you, regarding things not working, like ADB (works perfectly on my device), Offline-Charging (works perfectly on my P9), NFC partly works (I can send files via Android Beam from other devices to my P9, but seems not from my P9 to another device...)

I have the suspicion that you may have partly messed up your device by flashing various ZIPs!

So I really recommend you going back to HUAWEI stock, maybe use that opportunity to get to the 550 firmware and afterwards really refrain from flashing things other than system.img and - once available, a new kernel.

Why do I say that?

In fact, a GSI should really only flash the system partition, whilst other partitions on the device remain untouched! The phh builds follow this philosophy and even "cheat" by e.g. mounting /product or /vendor stuff into the "nirvana" in order to r ZIPeplace them by own content through "over-mounting" (mount -o bind), which bypasses the file paths at runtime, but don't touch the original partitions.

EDIT correction:

The fist ZIP file overwrites e.g. the /product partition and the 2nd ZIP file stays in system, but brings a lot of stuff not necessarily needed, but to simply fit multiple different device setups.

Of course, I haven't seen your device (so I am "wild guessing"), nevertheless I would really recommend this activity to re-initialize your device and afterwards, only use TWRP a very last time to flash the network patch and then take the stock recovery back and only use fastboot to flash back system images, like e.g. my build ;)

If needed, I can write a separate post on how to get to the EVA-AL10 8.0.0.550(C00) firmware - (the method to simply let eRecovery do that job did not work for me, it wanted to downgrade my to device Stock Nougat ! :eek: (so I immediately stopped that)

I'll have a look at the zips provided by you and see, what I will include in my build...

Regards, M.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Cool! Many thanks - that one will definitely be added in my next build! It indeed fixes the AuroraStore behavior. :good:
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Okay . . .

1. features_eva.xml will be added :good:

2. Offline charging works already

3. The hw HALs (system/bin/hw/vendor.huawei.hardware*) are present in /vendor/bin/hw (vendor partition)

4. The overlay is already part of my build

5. The NfC app, libs and the extras.jar - if I understand correct, this is from the "manual fixes for hi6250 devices" thread, right? So extracted from Huawei firmware? Or from where does this come from? I'll have a look as well into the newest AL10 8.0.0.550(C00) firmware . . .
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Wattsensi:
They are from a PRA-L09 firmware so this may be the culprit because the NFC facilities are not 1:1. Indeed, I'll try going back to EMUI 8.0 and will update to B550 as a bonus too. I have no access to EMUI 8.0 firmware yet but I will try fetching the latest EVA-AL10 firmware. I will also update the amend patch to use EVA NFC libraries instead.

I do need to redo that ZIP...

Also, nevermind! USB debugging finally worked, but it only works while MTP is enabled. Is that intentional or just a bug?
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
This can be observed with many ROMS and also on some phones with Stock firmware.

For me not a show stopper - I would consider it a bug, but not worth for me to spend time on trying to fix it.

If anybody can point me to a solution, I will of course be happy to apply it to my build...
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Wattsensi:
I will try my hand at building LineageOS 18.0 once we have a stable enough phh base and eventually work on shimming the non-treblified parts, is 300 GB of disk space, dual core CPU and 8 GB of RAM enough? I've built AOSP 8 before for ARMv7

I have 8 GB of RAM, 8 GB of Swap and a 500 GB HDD, 450 GB free of which 50 GB will be used for ccache
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
It should work, but this setup tends to the minimum requirements (I know, building android is really demanding hardware resources).

Disk space should be fine, although it will allow mainly one build tree (unless you cut the clone-depth) and one "out" dir for one build.

Memory with 8GB will make you "practice your patience and meditate", that is your bottleneck.

I also have a question to you:

Can you give me a good link to a simple HowTo for pulling odexed apks including vdex files from a firmware and converting them into deodexed apks, for the purpose of pulling a single apk for re-use in a Custom ROM?

I mean explicitly NOT doing this directly on a rooted device (because I wish to reuse the Apk finally).

What I found so far is either targeting the affected device only (I.e. do it directly on the device and re-odex) or from 2013-2015 and therefore no vdex handling.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Wattsensi:
Sorry, I don't really know how odexing works on ART since Lollipop, never heard about such 'vdex'. I don't really know how to do it with new toolchains, I used to rely on ancient Windows tools to deodex and modify the smali files.

also NFC works partially out of the box, I just beamed a photo from my Galaxy S7 but I cannot beam it back. My amend patch borks it up so I'm going to update it so it doesn't patch the NFC libraries and other unneeded fixes. Turns out your ROM contains NFC patches already.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Nightwish1976:
Alright, I found a fix for the apps missing from Aurora/Google Store. It's an XML file that has to be copied to system/etc/sysconfig. It works for me on this ROM.

Source and download link: https://xdaforums.com/showpost.php?p=81021757&postcount=4

---------- Post added at 10:37 PM ---------- Previous post was at 10:33 PM ----------

PS: I can't make the fingerprint reader work on this ROM. When I want to set it up, it just doesn't read my fingerprint. It works on other ROMs, so it's not a hardware issue. Is it the same for you guys, or it's just my phone?
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
The first item will be solved in the next build, [MENTION=9152969]Wattsensi[/MENTION] brought me already to it, see our discussion.

Regarding Fingerprint, that works perfectly on my P9.

Again, as I told further above to [MENTION=9152969]Wattsensi[/MENTION], some flashable ZIPs available here on XDA, which target originally other devices, may have unwanted side effects, especially if they even aim at messing around other partitions outside /system - in such a case, the "damage" might even persist, if you reflash the system partition... (In such cases, one would have to go back to Stock)

I don't know your device setup, but I take my device as "reference", because I don't use TWRP on it and I therefore can't and don't flash Zips.