Home

Compatibility

Result:

• 👍: means it can successfully go into launcher, and has wifi, fingerprint, bluetooth, nfc, mobile
• 🤒: means it can successfully go into launcher, but some of the above components not work.

Tags:

• NO_LED: no LED indicator
• NFC_CRASH: nfc service constantly crash, settings panel no responding when switching
• CAMERA_OC: no problems when taking shots/videos with OpenCamera app
• CAMERA_GCAM: gcam 6.1 port HDR+ & NightSight works
• APTX: verified APTX works
• AAC: verified A2DP AAC works

Partitions: all other partitions except for /system, /vendor, /boot

---

Result	System	Vendor	Kernel	Partitions	TAGS
🤒	AOSP9 v110	593edf8	SS2/2080WW	SS2/135F	NFC_CRASH NO_LED
🤒	AOSP9 v110	593edf8	SS2/2080WW	SS2/2080WW	NFC_CRASH NO_LED
👍	AOSP81 v28	86f872b	SS2/2080WW	SS2/2080WW	CAMERA_OC NO_LED APTX
👍	AOSP9 v110	6f218b9	SS2/2080WW	SS2/2080WW	CAMERA_OC NO_LED APTX
👍	PE@190213	19176c7	SS2/2080WW	SS2/2080WW	CAMERA_OC NO_LED APTX
👍	AOSP81 v28	2.0/OREO	SS2/2080WW	SS2/2080WW	CAMERA_GCAM CAMERA_OC NO_LED APTX
👍	Stock 8.0	0.9/STOCK	SS2/2080WW	SS2/2080WW	CAMERA_GCAM CAMERA_OC AAC

• For smooth Google Camera, stick on stock 8.0.
• For A2DP aptX and Google Camera (kind of unstable), stick on AOSP 8.1.

---

Branches

• Branch adapt_for_stock80 is specifically to operate with stock 8.0 system image that contains some minor fixes.

• Branch master is the vendor base for the latest version of AOSP GSI.

• Branch adapt_for_aosp90 is based on master with 9.0-specific patches and precompiled_sepolicy.cil*.

• Branch adapt_for_aosp81 is based on master with 8.1-specific patches and precompiled_sepolicy.cil.

Help test

Note that till 2019-03-04, master has yet been merged into adapt_for_aosp90 because I have no time to test it. For whom want to help the test, should do the following:

1. git checkout adapt_for_aosp90
2. git merge master
3. cd vendor/etc/selinux
4. secilc -M true -G -o precompiled_sepolicy -c 30 ~/phh90/plat_sepolicy.cil ~/phh90/26.0.cil nonplat_sepolicy.cil (files can be found from phh AOSP 9.0 system image)
5. try to resolve some duplicate attributes in nonplat_sepolicy.cil
6. git add .; git commit -m "Update binary policy"

Google Camera

As of 2019-03-04, I'm sticking on phh's AOSP 8.1 with the vendor.img from 2.0/OREO for the GCAM port that it can simply work without pains.

For Tolyan's 1.4a (MGC_6.1.021_BSG_Arnova-based_v.1.4a_TlnNeun.apk):

• AOSP 8.1 + 2.0/OREO: HDR+ works, NightSight works but not stable, doesn't support notch overlay.

• Stock 8.0 + 0.9/STOCK: HDR+ works, NightSight works, response more quickly, support notch overlay (UI won't be shielded)

Google Camera & Android 9.0 PIE

As of writing, GCAM (Tolyan's 1.4a) in 9.0 PIE would simply crash. And from the error message I afraid that the current stock-based vendor image (comes with VNDK 26) may not be able to run GCam in 9.0 PIE.

It may require upgrade to newer VNDK, e.g. VNDK 27 from Nokia 6.1 or VNDK 28 from Nokia 7.1 plus, and even possibly a newer kernel to have it work.

Work with NOKIA PixelExperience P

As of the writing, I suggest to work with unofficial NOKIA PixelExperience P system image, as it is made for Nokia 7 Plus, which was cooked by the product team the same as as our SHARP AQOUS S2. Means that the software architecture and layout are nearly the same. Our vendor image can thus work more seamless without minor annoying issues.

Steps

1. Use 1.1 release vendor image.
2. Download unofficial NOKIA PixelExperience P system image.
3. Mount rw system image.
4. Run install_libnfc_nci_conf.sh to the mounted folder.
5. Run sharpize_nokia_pixelexperience_p.sh to the mounted folder (remember customize your needs inside).

Currently everything works well. It could be daily driven.

For GCAM 6.x port, it may need to set SELinux to permissive mode (which can be update in the boot.img, but not suggest to for a daily-use phone). I tried just a short period and found out it may need new polices to run without problems, not very sure.