[ROM][Treble][microG]LineageOS 16.0 for HUAWEI P9

[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

 

[MSe1969]

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

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.

 

[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.

 

[md sabuj]

Can I flash this rom via TWRP?

 

[MSe1969]

Can I flash this rom via TWRP?

No.
TWRP can't decrypt the /data partition. You need the original Huawei recovery and fastboot is the only option.

 

[md sabuj]

No.
TWRP can't decrypt the /data partition. You need the original Huawei recovery and fastboot is the only option.

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.

 

[MSe1969]

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.

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.

 

[md sabuj]

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.

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?

 

[MSe1969]

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?

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"

 

[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.

 

[md sabuj]

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.

Does Eco Kernel support fast charging?

 

[MSe1969]

Does Eco Kernel support fast charging?

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://forum.xda-developers.com/p9...arter-v0-1-t3857029/post77962037#post77962037
https://forum.xda-developers.com/p9...arter-v0-1-t3857029/post78627442#post78627442

 

[mqb61a]

To your 1st question: What would be the benefit of doing so? In the Openkirin TG support channel, one of the issues is that the Huawei Cam, which is an Oreo system app, tries to access the external SD the "Oreo-way", which does not work any longer in Pie for example.
To your 2nd point: Is there any way to explicitly reproduce the lag or can you produce a log?

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.

 

[MSe1969]

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.

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?

 

[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!
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.

 

[plarfman]

Hey there, since its a treble build, could it be installed onto hi6250 devices (pralx1)

 

[MSe1969]

Hey there, since its a treble build, could it be installed onto hi6250 devices (pralx1)

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.

 

[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.

 

[Magdy Doze]

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.

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?

 

[MSe1969]

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?

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)