yashsingh1/xdaforums huggingface dataset:
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Normally, when you connect the phone via USB, you should have a message appearing, which you can "pull down", where you would jump into the screens, you were showing. And you would have to set "Dateiübertragung" as well to have a working adb.

If fastboot works, I don't think that you have a driver issue on your PC, but I don't want to exclude this, as adb is technically a different protocol compared to fastboot. When you say "driver issue' I would guess you have a Windows PC, so yes: try re-installing the USB drivers as a 1st step...
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
I'll have a look next week... (need to see, from where the audio_effects. xml file is taken...)
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] NPS-2750X:
Thank you. I tried this operation and it showed "owner died". View attachment 5684437
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] P9_User:
Yes, Win10 PC. Now I think I made a big mess and even fastboot is not working anymore. I tried to reinstall any Android related drivers with no success. I had both (fastboot & adb) working already a while ago, kept the drivers and tools and thought I can easily re-install everything.

Is there any simple step-by-step list of which drivers I need to make the P9 work fine with windows? Best how to clean all old drivers and which new ones (also tools) are needed after.

This is where I am lost now...

View attachment 5684681

In bootload mode showing this.

View attachment 5684683

View attachment 5684685
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Crohny:
Hi,

I'd like to start with a thanks for the great work on getting this lineage os to our good old P9!

I wanted to check in to see if anybody can get detailed battery stats after pressing the 3 dots in the battery menu. All I get is a unable to get battery use data. (Sorry it's a French littéral translation).

I also can't get net monitor to work either.

FYI, I'm using a P9 EVA-09L rebranded to EVA-AL10. Did anybody get confronted to this?

Build date: April 15th

Cheers!

Below is the log when I try to access to the detailed battery menu if it can help:

https://pastebin.com/BymewT36
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Hi, thanks for the log, will have a look at it. Yes, I can confirm your observation, will add it to the list of issues.

Regarding Netmonitor, that'll be fixed in the next build with May 2020 ASB patches, which I have already uploaded (see next post).

Regards, M.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
New build with May 2020 ASB

Hi all, a new build is available for download:

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

To install, download, unzip and follow instructions as outlined in OP.

The build has the following features:

Sec. string 2020-05-01

Bromite Webview on 81.0.4044.127

AuroraStore updated to 3.2.8

Fix of bundled 'netmonitor' app not starting

Regards, M.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] md sabuj:
Can I flash this rom via TWRP?
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
No.

TWRP can't decrypt the /data partition. You need the original Huawei recovery and fastboot is the only option.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] md sabuj:
Can you please tell me what's the difference between MicroG and Gapps? Will i face any problem if I install a ROM with MicroG insted of Gapps?

Does flashing Gapps with TWRP need data decryption?

And more thing is I previously flashed Andyan's Trebl GSI LOS17 rom via TWRP.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Info about microG can be found e.g. here:

https://microg.org/

https://lineage.microg.org/ (jump to the FAQ)

https://shadow53.com/android/no-gapps/faq/

Many apps with Google dependencies, but not all (especially not the "genuine" Google apps), run fine with microG - depends... Key is to focus more on FOSS alternatives.

Regarding TWRP, you may want to read some more explanation on the Openkirin pages (as indicated in the OP, I have no relationship to them, but their pages are really good). If you insist on using TWRP, by all means, use it. To simply flash the system.img, it should of course work (as you did already with the LOS 17.1 GSI), and if you absolutely want to try flashing Gapps over my build, it is your device and your decision. I don't recommend it, I expect issues. You can report your experience here, but don't expect any support from my side to solve issues, which result from not following my advice.

I recommend to read the information about microG. You will come to an opinion. You may want to give it a try...

If you decide, it is not your choice, so you would like to stay with Gapps, you should try the latest LineageOS 16.0 Openkirin build, rather than trying to flash Gapps over my build, but as said - your device, your choice, you dealing with the result.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] md sabuj:
Thank you for your reply?

I have tried all OpenKirin builds, All seems fine except battery. Battery draining so fast. I really like lineage os, I'm looking for a build with less Battery consumption no matter with MicroG or Gapps.

And do you have any plan to bring Los17.1 for P9?
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Battery usage of my build has been called OK by a thread participant; I feel there is room for improvement, but I have no good idea yet, how...

No plans yet for Lineage 17.1 - I usually focus on stable daily driver quality rather than latest & greatest, but still being "fine tuned"
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Kernel

Just gave a try to the ECO Kernel, which seems to run really fine on the P9.

Instructions in the linked thread (I flashed the "04.05.20 build with Linaro").

Advantages:

- Up to date with current patches (Stock kernel is from December 2018)

- Hopefully better battery behavior

I'll report my impressions soon, after using the device for some time.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] md sabuj:
Does Eco Kernel support fast charging?
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
My main motivation to flash this kernel on my device is to get a more up-to-date kernel with security patches included and also the hope, as written before, to have a better battery behavior (which seems to be the case).

I am however not an expert of this kernel, I think you should look at the ECO kernel thread and search there.

I think the following posts in that thread may lead you into the right direction:

https://xdaforums.com/p9/developmen...arter-v0-1-t3857029/post77962037#post77962037

https://xdaforums.com/p9/developmen...arter-v0-1-t3857029/post78627442#post78627442
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] mqb61a:
Isn't there a Pie version of the Huawei Camera?

And the lag issue is gone. I wiped the cache and now everything is working fine.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Many thanks for confirming, that the "lag" issue is gone after clearing cache!

In regards to Huawei Camera:

The /vendor partition with the hardware drivers is still based on Android 8.0.0 - so I am not sure there truly is a Huawei Cam app around fitting to an 8.0.0 android based /vendor partition but targeting Android 9.0.0 SDK level - why should an OEM, who is in control of all of it, do such things?

If there indeed is, pls. show me where it can be downloaded. Although not really my priority, I may want to give it a try...

Even if, I repeat my question about the benefit of it: What does not work with the shipped camera or e.g. the OpenCamera app (available via F-Droid or PlayStore), if you aim at more features?
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
June ASB - IMPORTANT INFORMATION

Hi all,

in regards to June ASB patches, we have for the lineage-16.0 branch (Android 9), a really weird situation this month:

Short story

All patches ARE already present in the current build! :confused:

So despite showing the 2020-05-01 sec. string, the build is already on 2020-06-01.

Long story

In May, the tag android-9.0.0_r56 was merged. One could notice, that the tag contained some patches more than the ASB patches; this happens sometimes, nothing unusual, there are sometimes "maintenance" patches not listed in the ASB.

The now published tag android-9.0.0_r57 however, representing the June ASB, simply contains all the stuff again, which was already present in _r56. It however uses _r55 as "parent", which gives the (wrong) impression that the patches are 'new'.

Especially for a treble build, where only the system image is delivered - and not e.g. an updated kernel, as this is the case for "regular" ROMs - simply providing the exact same image just with one different value for the sec. string in the build.prop file does not add any real value! As I wasn't able so far to fix the two open issues (battery stats per app and wifi hotspot), I really don't see any benefit to create a new build for the sole sake of showing the June version string in Settings => about phone . . .

I will therefore not provide a new build this month - the next new build will therefore either contain July ASB, or - if I really manage this month to solve at least one of the two open issues (not too optimistic right now) - a build with an updated version string and at least one solved issue would still be published in June.

Regards, M.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] plarfman:
Hey there, since its a treble build, could it be installed onto hi6250 devices (pralx1)
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Short answer: The P8 lite 2017 is also "A-only", right? So try it, why not?

Long answer: It is based on phhusson's work, which is generic and aims at overall device compatibility, including hi6250. I had to adapt it to make e.g. the camera work, but this adaptation also first checks for the proper hardware. So as long as the hi6250 devices are also "A-only", you should be able to give it a try. If you try, please report your experience, in case it works out for you, I'll update the respective info section in my thread.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
New build with July ASB patches

Hi all,

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

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

ASB Security string 2020-07-01

microG: updated prebuilt GmsCore fom /e/ project (fixed FCM registration issues)

F-Droid updated to 1.8 / F-Droid privileged extension updated to 0.2.11

Aurorastore updated to 3.2.9 / AuroraServices updated to 1.0.6

Bromite Webview on 83.0.4103.101

Sepolicy: Netmonitor exception f. "Tracker Control" app

Happy flashing - regards, M.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Magdy Doze:
thanks a lot for awesome work!

could this build work on p9 plus too?

& since some emui 8.0 devices have already received the emui 10 update recently (mate 10 pro for example)....could this build get updated to emui 10 too as such?
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
As I don't own a P9 plus, I can only guess: I think it is worth a try on any emui 8.0 device! So if you would like to give it a try, please do so and report back. If all OK, I'll update the respective info section in this thread.

Regarding emui 10 - same story: I don't own such a device, so I can't try a Lineage 17.1 build.

(BTW, honesty, Android 10 / Lineage 17.1 is at the moment not my highest priority. I would have to port all my hardening features first and whilst I don't see any "killer" feature of Android 10 making we want to switch, I in the contrary see feature losses like dropped privacy guard in 17.1 and no homegrown root support any more)
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Thanks for the info. Ok, so file ownership root:everyone and file permissions 660 are as expected, the SELinux context as well. However, the error "owner died" is really strange! Never saw that before.

Can you switch to root in your terminal app? (You would need to allow root for apps in the developer options, restart the terminal app and enter the command 'su'). If yes, try deleting the file as root and show me, what happens. If not, please show me the error.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
I use Linux, which understands fastboot and adb protocols 'out of the box'. I do not use Windows any more on any private device since a couple of years (only Win10 on my work laptop, which belongs to my employer and where I don't have full admin rights).

Therefore: Really sorry, no good advice - maybe other people from the thread know more?

P.S.: Ok, just for completeness: The most important Windows advice after a driver install: REBOOT! (even if the system does not force you to do so)
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] NPS-2750X:
If I switch to Root in the terminal , the file can be successfully deleted without any error . And I found some extra information about the /DCIM/Camera folder in the stock file manager app , as the pictures below show . I don't know if such items have something to do with the deleting failure.

View attachment 5685311View attachment 5685313View attachment 5685315View attachment 5685317
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
To be honest, I have no idea about your issue. Only a last guess:

What you could still try, and what usually does not harm, is to wipe the cache partition in recovery. There should be an option to wipe the cache partition, when you boot to recovery (important: DO NOT wipe the data, aka 'factory reset', only wipe the

cache partition

! Should be the 3rd option). From what I have understood, when you described, how you had installed the ROM, it seems you have left out that step, so maybe some cache data from the previous Stock EMUI install may still be present any maybe disturb something...?
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] NPS-2750X:
I tried to wipe cache , but it seems that the problem still exists . Well , it doesn't matter because I can delete photos with Root , and this P9 is not my mainly-used device , so there's no need to think about it anymore . I'm sorry for taking you so much time to deal with such a strange problem , and thank you for your developments and answering the questions . View attachment 5686305
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] P9_User:
Hi. back at my workdesk I set up my sandbox raspi and installed adb & fastboot. How funnny, fastboot works but adb still does not show any device number. Anything else I can check to make it work?
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Just to be sure: Did you enable debugging in the developer options?
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] P9_User:
View attachment 5688221

Yes. Via Network is not needed since I do connevt with USB, right?
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Correct, only that switch, and also "pull down" the silent messages and set your USB connection from "charge only" to "data transfer" (Dateiübertragung). It should then work (maybe kill and restart ADB in your PC)
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] P9_User:
I am working on the Rasperberry Pi now, no PC. Shure, forgot to connect to allowe raspberrys adress to connect. Did that, went to bootloader and adb still not working, killed and started server, does not help.

fastboot has no problems. So its the same thing going on, does not matter if I take my laptop, desktorp or raspi device.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
OK, other thing to make sure:

When you are in bootloader mode, only fastboot works, that is normal. When you run your system, and you have enabled debugging, then you can connect via adb (and not via fastboot).

I have understood your last post, that you have tried to use adb, while your phone was in bootloader mode, that of course will never work.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] P9_User:
Sir, and this is where I misunderstood everything...

adb is working, I will send you a log file regarding my webgl problem soon.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Okay, now I have found the time to create a test build here:

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

As the token dispenser server of AuroraStore is currently down, I can't install the Wavelet app to test myself, so please flash the test build and let me know, whether it's OK now. If yes, this will become part of the ROM.

The link provided by you did contain indeed the necessary information how to solve your issue, but the referred commit was at first misleading. This ROM is an Android 9.0 ROM, but uses the Android 8.0 vendor partition from EMUI 8. The Android 9.0 (LineageOS 16.0) ROM is already by default properly configured and expects the library to be present in the vendor partition, but the lib isn't there! So I had to "tweak" this a little, see here...
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] lo_ol:
I guess that’s where things went wrong. The problems you described, storage issues after fastboot -w and overheating, are caused by some ancient magisk versions. According to the hi6250 telegram channel, formatting /data via twrp is supposed to fix the mess and to fix overheating get rid off or update magisk. These old versions cause the big cluster to run constantly at its 2.5 ghz maximum frequency on any gsi that runs on top of emui8 vendor

@MSe1969

One small thing that might be worth including in your build is the openkirin signal strength icon fix to be placed in /system/framework. Alternatively there have also been open source patches committed to Phhusson’s A11/12 branches, however these files seem quite different to the A9 file versions. https://github.com/phhusson/platfor...mmit/64fa7c61a0a4b41b9e40a37b673699a45eb88b8c

In any case thanks a lot for the continued support. Very much appreciated(y)
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
OK, it'll be part of my next build, I have extracted the file from an Openkirin build and made it part of it. However, I don't really see any difference... What exactly does it do?
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
New build with backported September '22 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_20220910_system.img.zip/download

Custom build release 2022-09-01

Bromite Webview 104.0.5112.91

microG 0.2.24.214816-30

Contacts app slightly 'de-Googled'

Happy flashing!

Regards, M.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] lo_ol:
Thanks! It brings the otherwise static mobile network signal indicator in the top notification bar to life
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] kundifon:
I use this rom a little while. Instead of microG I relly need GApps. Prefered is Open GApps pico as allways.

(MicroG is great thing but don't suit my needs. It's not finish jet. So there is no contact sync, unreliable gmail notifications, google translate doesn't translate at all, google docks don't sync, you cannot buy apps in Aurora store)

I'm used to LineageOS, have it on my Galaxy S4, S8 for few years. Your rom is great to, preferred it from P9 eva stock rom.

How do I switch to GApps and clean up microG?

Whats about signature spoofing, have I to revert something? Will work if I simply patch over the GApps with twrp or Flashify?

https://xdaforums.com/t/how-do-i-install-gapps-manually.3652666/#post-82853227

Due the lack of info, can you @MSe1969 please direct me, where to start. Root is enabled already.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Thanks for the positive feedback about my ROM in general. You seem to feel comfortable in the "Googleverse", which is of course your choice. Hence I will try to give you a pure technical answer without further talking about the impacts on your device and your (then not any more existing) privacy.

First of all, I have no idea, whether this will really work or not - the ROM has some hardening features ported from GrapheneOS, which have privacy and security in mind and the ultimately very last topic, I was even considering, was the question, whether this could have any negative impact on Gapps not running properly. Therefore, I can give you some advice, what you *could* try, but I don't even know, whether this will work or at the end leave you stuck in an ugly boot loop - that is why

I do not recommend this

and you are on your own - "you have been warned !"

If you succeed, be happy - if not, this is not my problem and I simply cannot give you any further help. The "fix" for the boot loop would be to flash the system.img again via fastboot and then to wipe the /data partition in recovery.

If you still take the decision, that you would like to give this a try, this is, what you could do:

TWRP is a recipe for trouble for this device. Unless you have it already running AND your device is therefore unencrypted, I'd be very careful. If you have right now the EMUI recovery, your device is encrypted, and you would need to wipe the /data partition from TWRP after flashing it, which means you loose all your data on the phone.

If you by chance have already TWRP on your current setup (and hence an unencrypted device), make sure you will deactivate/freeze the following apps: GMS Core, GSF framework, FakeStore, before you reboot to TWRP (obviously, when you have to anyhow wipe your /data partition, this is not necessary) - I am however afraid, that even then, you may finally have to wipe your /data partition, but you may want to try first without...

In any case, having an

unencrypted

device with TWRP as recovery gives anybody with physical access to your device full access to everything on your phone, so make sure the device will not get stolen or contain any sensitive data

Assuming you have TWRP now and are able to flash things, keep in mind, that you will have to continue flashing the system.img of my ROM for each update and repeat all the steps listed below in TWRP, as flashing the system.img will remove the Gapps stuff:

Get into a root shell and remove (via command rm -rf) the following directories and their content:

/system/app/AuroraStore

/system/app/GsfProxy

/system/priv-app/AuroraServices

/system/priv-app/FakeStore

/system/priv-app/GmsCore

Afterwards, flash your preferred Gapps package (I can only advice you to use the pico flavor and nothing bigger)

The signature spoofing patch will not be an issue for you - if something goes wrong, it will be caused by the other hardening measures, but not the microG patch (if you look at its code, you'll know why)

Good luck !

Cheers, M.