yashsingh1/xdaforums huggingface dataset:
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Wattsensi:
[MENTION=7929484]MSe1969[/MENTION]

I solved the audio jack problem, build and apply the treble-device-huawei-EVA overlay in this repo

https://gitlab.com/insaane/vendor_hardware_overlay

It also has the correct power profile and battery stats
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Thanks a lot! Indeed, the battery stats issue is now solved, this will be part of my next build. :good:

Regarding audio jack, I did not have those issues before, but if that solves the issue for you, it will probably also for others.

Now, the only open issue (besides the missing boot animation after decryption, which is not really a big deal) is the non-working wi-fi hotspot.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Mywayorthehuawei:
Yea the wifi hotspot works in official lineage - Tested with openkirin's emui 8 build on a p9.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Wattsensi:
I'm working really hard on this device to divorce ourselves from OpenKirin as much as possible. Unlike them I always open source my work so if I get bored of working on EVA or someone wants to work too it will ease the work. We still pretty much have no access to Android 10, but at least with this new development we have access to a large gamut of Pie GSIs rather than what just OpenKirin cooks for us. I myself use AOSP 9 for development. I am trying to diagnose AOSP 10 v213 (v220 doesn't get to the boot animation and I have no way to debug that early stage boot)
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Right - and yes, really a pitty that they keep their work a "secret". It is of course their right to do so, but I don't even see the benefit of doing so: They don't earn money with that, have no other necessity to hide their work (unless they have some secret contact with somebody obliging them to non-disclosure - which I don't believe, as their builds aren't perfect either) and they could for sure benefit from people making suggestions etc. - But enough of that, why wasting energy on things we cannot change?

Let's hope we'll find out how to fix the Hotspot issue. Looking at phh's treble_experimentations repo and the open issues, the Hotspot seems to be tricky also for other devices . . .
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Wattsensi:
Hotspot looks like it works on Phh-Treble
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Seems to work, but not for all devices. . . - anyhow, as indicated already, I am glad for any hint to make it work.

I have tried already the configurations/overlays, but the current config is the same as in Huawei Oreo stock, so my guess is, that there is some Emui/Huawei specific mod necessary to work with the emui-vendor partition properly.

But that's a wild guess from my end and not really a helpful one. . .
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Wattsensi:
Weird, I can engage the AP and make a network appear on my computer's WLAN scanner when I'm using Phh-Treble. Haven't tried other GSIs. Shame that the "Open"Kirin guys are so secretive, if they weren't like that we would already be running all the ROMs we wanted to with few issues, but alas they have all the right to withhold their work from us. I'm about to release a joint fix ZIP that will make Pie ROMs bearable in the meantime that fixes offline charging, NFC, ROM features and adds the device overlay, if you flash it between the GSI and the gapps then it should behave like the OK ROM.

Also, modern Treble ROMs only modify the system partition. The vendor partition and the kernel are separate and stay untouched by the OS.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
When you say, you can do so with phh-treble:

On the P9

, right? Did you compile a test build yourself using directly the phh source tree? If yes, could you please share the build manifest?

Or did you use an already compiled GSI? In that case, which one exactly?

My build is fully based on phh, but with the following modifications:

- Applied the additional LineageOS patches by AndyYan to all affected repos

- Additional patches in device repo (see branch lin-16.0-eva-p9): Camera, Offline-Charger, declaring the print feature (needed for Lineage Settings menu)

- The "microG" specific platform changes (should have no impact on AP)

- In general, I refer in my manifest to the "pie" branches of phh, when they exist - or should I use master instead? => I understand "pie" being the build I make (as LineageOS 16.0 is pie), or does "pie" here mean "pie vendor partition" (as opposed to Oreo Vendor, which we have for the P9)?

Have the feeling we're quite close to a solution... Please advise, thanks M.

-
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] :
Solved it was something from dev option anyway I have another problem I can t play any game bcs of thermal trottle idk why it trottle at 30c the phone it cold.but all games or apps become unusable no matter what rom I use if you have any info on how to disable it I know the risk I will be greatfull
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
New build with backported December '23 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_20231220_system.img.zip/download

Custom build release 2023-12-01

Mulch System Webview 120.0.6099.115

Happy flashing!

Regards, M.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] :
no los 17 neat future?
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
No - see OP.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] :
any change of costum rom for p40 lite ? this is my last question
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] lo_ol:
Thanks for keeping us updated!

However the link points to November build, just in case anyone else is wondering ;)

Yesterdays December release https://sourceforge.net/projects/li..._a_lineage16_20231220_system.img.zip/download
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Not from my end - I don't even have that device
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Thanks for the hint, I have edited my post with the proper URL
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] lo_ol:
Still not the proper link I'm afraid as it now points to your moto g build
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Ooops :ROFLMAO: - thanks, now it should really be ok
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
New build with backported January '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_20240112_system.img.zip/download

Custom build release 2024-01-01

Mulch System Webview 120.0.6099.210

Timezone DB 2023 updates

Happy flashing!

Regards, M.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] vvvbbbcz:
There is a bug on ADB.

When I enable ADB, a thread called ADB-JDWP will eat all CPU resource.

In the process list, you can see all apps eating CPU.

Here are screenshots.

View attachment 6065266

ADB disabled

View attachment 6065267

ADB enabled

My phone is running the latest version of this ROM (16.0-20240112-UNOFFICIAL-microG-signed-)

I disabled ADB, but it will restore after reboot, so I have to disable ADB manually after reboot every time.

I would appreciate it if you could fix this bug.

Thank you!
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
When I connect my own phone via ADB and 'adb shell' into it (root mode and also non-root mode), I only see the default adbd process when e.g. calling the top command, and it also does not really eat a lot of resources. A process called ADB-JDWP (capital letters) does not exist in my phone.

Searching the net reveals: "JDWP stands for Java Debug Wire Protocol. If an application running in its VM is debuggable, it exposes a unique port on which we can connect to it using JDB. This is possible in Dalvik Virtual Machines with the support of JDWP."

Are you maybe doing yourself any debugging to obtain the process list?
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
New build with backported February '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_20240215_system.img.zip/download

Custom build release 2024-02-01

Mulch System Webview 121.0.6167.178

Happy flashing!

Regards, M.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] vvvbbbcz:
ADB-JDWP isn't a process, it's a thread running with all apps when you enable ADB.

I didn't doing any debugging, I just obtain the thread list by using a analyzer software.

When I running top in the ADB shell, the result is:

View attachment 6072072

As the image shows, you can't see any process called JDWP because it's a thread, but you can see all apps eating CPU.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
New build with backported March '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_20240310_system.img.zip/download

Custom build release 2024-03-01

Important note about Webview update:

With the M122 release, webview again has significantly grown by ~30MB - this again exceeds the maximum /system partition size of the P9 device. Therefore, I have shipped again the previous version from the M121 release of last month.

Please update therefore the Webview to M122 using one of the two below listed methods:

a. If you have already manually added further repositories to the F-Droid app, please make sure to add the Divest-OS repository: "https://divestos.org/apks/official/fdroid/repo/ " - once added, it will offer you to update Mulch Webview

b. Option a always works. If you haven't yet added any additional repository to F-Droid, the following option may even be easier: Go to Settings - Apps, choose the F-Droid app and purge its used memory. When you start F-Droid, it will update its repository list and afterwards offer you to update Mulch Webview.

Happy flashing!

Regards, M.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
New build with backported April '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_20240409_system.img.zip/download

Custom build release 2024-04-01

Important note about Webview update:

With the M122 release, webview again has significantly grown by ~30MB - this again exceeds the maximum /system partition size of the P9 device. Therefore, I have shipped again the previous version from the M121 release of last month. Please update therefore the Webview to M123 as explained in my previous post.

Happy flashing!

Regards, M.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] AltairFR:
Perhaps you can join hisi-oss group to build LineageOS 20.0 or 21
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] AltairFR:
LineageOS on HiSilicon

hi6250 | hi3650 | hi3660 | kirin970. LineageOS on HiSilicon has 25 repositories available. Follow their code on GitHub.

github.com
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Thanks for the proposal, but due to the below listed three reasons, my answer can only be no :

The P9-EVA has got a 4.4 kernel, so there is no support for eBPF, which is a requirement for Android 12 and above, see e.g. here - yes, I know, there is an "ugly hack" patch to simply 'carve out' the entire packet filtering functionality and hence render the network manager void, but my build offers a firewall and Google/Facebook blocking or filtering functionality as a key feature - hence this is a solid KO criterion for me.

We could already stop at item 1, but here comes another road block: I have already now in Android 9 severe issues with the small system partition size of the P9, so people have to manually update the webview (which is then saved on the /data partition), because I can only ship M121 with my build. I seriously doubt, that even a "Vanilla" Android 13 GSI fits on the system partition. And the /product partition size on the P9 - apart from better

not

messing around with that in treble builds - really is a joke!

On top, and the P9 camera is also something VERY special which requires some extra attention - maybe for that piece there should somewhere be a solution, but not trivial.

Whilst #3 should be solvable, I consider #2 and #1 a really substancial obstacle for the P9-EVA to get Android 13.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] AltairFR:
The hisi-oss project provides a 4.4 kernel with a BPF upstream, I myself have a pra-lx1 under Android 13. Moreover, for the partition problem it is not a problem either because the oss replaces the vendor partitions , product, odm by only one partition dynamic (super.img)
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] DoSpamu:
Can this rom be use on the Mate 10 Lite?

Basically is on EMUI 8 but, who knows
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
First things first:

I don't know, as I don't own such a device

.

However - as it is a treble build, it should in general work - If you would like to give it a try, I suggest to simply try and report here about your experience. (You should however be experienced enough to know how to deal with it if something goes wrong).
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Thanks for your feedback - this could indeed be interesting. However - when looking at their sources, the P9 device config is not part of it and I am not at all good at "bringing up" a device - when I find some more time, I may contact them to find out, whether they would be willing to give me some hints...
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] rdy2fly:
Hey there,

first of all great work, found this device at home and thought I would use it for dev purposes, overall the rom is very smooth. However when I try to run scrcpy to screen mirror, the screen always freezes after couple of frames on pc side, while I can still control the phone itself with mouse. After some digging I found out its most likely issue with the rom, here is log from logcat when this happens:

04-16 17:37:54.809 1622 4469 E BufferQueueProducer: [GraphicBufferSource] dequeueBuffer: attempting to exceed the max dequeued buffer count (1)
04-16 17:37:54.809 1622 4469 E /vendor/bin/hw/android.hardware.media.omx@1.0-service: TWGraphicBufferProducer::dequeueBuffer - Invalid output fence

Seems to be related to the media encoder, switching encoding codecs in scrcpy didn't really solve the issue. Do you have any ide how I could approach it? It worked on the stock nougat rom, but I honestly have no idea how I could revert to stock rom anymore. I tried running the twrp script to flash the stock oreo rom as update but without success.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
The scrcpy issue was already reported here some time back - unfortunately, I do not really have a good solution for you - may very well be, that this ROM (or some hardening measures) are causing this.

The log indicates a buffering issue, but I have no idea how to increase the buffer.

Treble builds have in some areas certain shortcomings - especially when running an Android 9 system image on an Android 8 vendor partition with some tweaks...

In regards to going back to stock - I am not sure, whether you can easily return to Nougat Stock ROM, but the basic principle is e.g. described here.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] lo_ol:
There is a small patch in Iceows’ repo that apparently fixes the screen mirroring issue

aosp_patches_leaos/patches/phh/frameworks_av/0001-Fix-WiFi-Display-on-Huawei-devices-EMUI-8.0.patch at main · Iceows/aosp_patches_leaos

Patches for LeaOS version AOSP. Contribute to Iceows/aosp_patches_leaos development by creating an account on GitHub.

github.com
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] AltairFR:
You need more than one patch to fix screen mirroring, but you can peek all the patches in my repo
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] lo_ol:
Okay all of these then I guess in addition

Fix wifidisplay (MIRACAST) · Iceows/aosp_patches_leaos@51bc7ef

Fix wifidisplay (MIRACAST)

github.com

Well not just a small patch then😁
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] P9_User:
Hi. 3G will be turned off in next two month here in Austria. So there is GSM and LTE left for the P9 if I understand correctly.

Well, I am a bit in a worry that it will be really boring if LTE us not available only having GSM left for data and voice.

I relly like the P9 with its compact size and not beeing an expensive hardware. I never missedd anything with the monthly security patches etc...

Any suggestin for near future?

Greetings.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Hmm, honestly, I don't fully get your issue. Somehow you seem to assume that each 3G station is 1:1 replaced with 5G (so there will be 5G in all rural areas), so you think that you need a 5G phone to cover the 3G gap?

When 3G was switched off in Germany, I did not really feel too much of a gap with my 4G phones (OK may depend on region)

I may be wrong, but normally, the new technologies are implemented in cities first, so the 5G stations have already replaced 3G in big cities, where 4G is already in parallel deployed. 3G disappearing in rural areas is ****ty, but a 5G phone probably won't help in rural areas...? So with a 5G phone in a GSM only area is as useful as a 4G phone...?
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] P9_User:
Well, I spend a good part of my time in rural areas bear country boarder, the other time in big city. So both extremes.

But I think I understand you compareing with the situation of modern 5G phones...
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
New build with backported May '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_20240514_system.img.zip/download

Custom build release 2024-05-01

Regarding the previously mentioned screen-mirroring patches, I'll have a look at them soon, but they are not yet part of this build.

Happy flashing!

Regards, M.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] SideSkroll:
Hi, for "unexpected circunstances" I currently need to use my old ass p9 for a while. And as I was dusting it off I realized (and remembered) that when I used it last I was running an Omni rom on Android 9 but it had many (MANY) issues such as OBSCENELY low volume (to be honest, I cant remember if the phone had that volume issue on stock or not... I doubt it though cause its WAY TOO LOW) frequent hangs etc.

So Im honestly amazed that someone is still developing a "current rom" for this ancient artifact.

Anyway, first of all is the volume an issue with your rom?

If not, could you help me with how to get your rom in here? I mean do I still need to go back to stock (which one? Cause if I remember correctly I had to "fake" my phones model to a Korean version to update it fully? My phone is P9 EVA-L09 from factory but currently shows as EVA-L10. Is that ok?)

Do i need to go back to l09? And if so, how? Do I just flash the oem rom back? And lastly, do I flash the original recovery AFTER being back with the original ron or before? (Im thinking AFTER?)

Thanks for any pointers that you may give me to put me in the right path. Its been SO LONG since I last played with this phone. Close to a decade now! I dont even know where to start.

And thanks for taking the time to maintain a rom for such an old device. People in my current position truly appreciate it.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
The issues, which you describe, do not apply to my ROM.

It seems, that you have an old Openkirin Omni image on your P9, from what I have understood. If that is the case, you have already EMUI 8 on your device. Of course, you are the only person who knows, what has been done with your device, I can only try to understand, what you have outlined.

Please exactly check the model info: Does it say AL10 ?

If it says AL10, I see two options for you:

If my above assumption is correct AND if you have right now the EMUI recovery on your device AND you have not messed up with the /vendor partition before by flashing any "cool stuff" or manually editing files within there:

- Flash my system.img via fastboot as described

- Boot into recovery (via hardware keys) and do a wipe/factory reset and reboot

Advantage: Quick and easy (I would anyway start with that step, if I were you)

Potential disadvantages: Probably very old firmware, and if you have messed with /vendor partition etc. in the past, you may face issues

If you have your bootloader unlock key handy (you

need

that key, if you don't have it any more, get one with e.g. DC unlocker) - the OP contains a link to the "HWOTA" thread. Start with the step, where the device has been rebranded already to Chinese AL10 and has the Chinese EMUI5 / Android 7.0 Stock ROM, so the step would be to upgrade to EMUI 8. You will find the needed files on the respective links provided in my OP. Be warned: carefully read through the entire procedure at least once!

Disadvantage: This is some work and you really need to carefully read and follow the instructions and

think and understand, before doing anything

.

Advantage: You will have the most recent firmware and all will work properly (if you followed instructions properly)
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] SideSkroll:
Hello, thanks for replying.

Yes, I currently have an Openkirin Omni romon my phone. So yeah, I guess I must be on EMUI 8.

Yes, it does say EVA-AL10 (even though it is originally an EVA-L09).

Regarding the potential disadvantages, what do you mean by "messed up with the /vendor partition before by flashing any "cool stuff" or manually editing files within there". As one might expect I cant recall what I did or if I did anything with the vendor. But maybe if you could specify what "cool stuff" might mean I could recall something.... But Pretty sure I just unlocked it, did the whole "rebranding to chinese" procedure and went straight to the omni rom.

Also, I just checked and I'm APPARENTLY running the stock recovery (which is odd because I can clearly remember having TWRP installed in here). Is there a possibility that it somehow got overwritten or that it MIGHT be in there SOMEWHERE.... SOMEHOW? If not, then yes. I have the stock recovery.

I do have my unlock code still (pretty sure I backed it up somewhere) if needed.

So your "official recommendation" would be to just go ahead and flash your rom per your OP instructions? Anything else I might need to verify prior to doing it?

I would like to get to a point in which everything is as good as it could be. no "very old firmware", no need for custom recoveries, no need to rollback to previous roms (or OEMs) etc.

Thanks for your help thus far. I really appreciate it.

EDIT: Maybe I should "overwrite" the recovery with the EMUI one? Just to be sure? If so, how?