I have few questions for you my friend:
1. Are you able to list one by one the issues that were present in the original Oreo firmware that you've resolved in the full version?
2. I noticed that the changes you made in the original firmware files were specific to 2015 models even for users using 2017 model. For example, in all your fixes / mods, you've replaced darcy with forster. Examples can be found in the framework-res.apk, build.prop, SystemUI.apk and few others. Is there any reason why the 2017 models should have foster(2015) instead of original darcy (2017)?
3. I saw the changes you made to framework.jar. To be specific, to AndroidKeyStoreKeyPairGeneratorSpi.smali and ViewRootImpl$EarlyPostImeInputStage.smali. Are these changes to fix the scrolling?
I only asked these questions for my own curiosity, hope you will find time to answer them. I use to develop in android and if you search for Phronesis rom you will find some of my work here:
https://www.google.co.uk/search?q=phron ... e&ie=UTF-8.
And hopefully, I can be of assistance to you in future if you ever need my help...
Exit touch mode on mouse/stylus click
https://android.googlesource.com/platfo ... ad01a4cc9/
https://android-review.googlesource.com ... e/+/551840
https://android-review.googlesource.com ... /+/469478/
I integrated Settings and SystemUI of Android 8.0 with the Nvidia framework.
Many others works on permissions, deodex, replace tv components with full android componetsand and resign
I made one firmware and all are named foster_e, but every device have his boot image
This is sufficient because SafetyNet read the value of a real certified firmware and foster_e is certified. ( his fingerprint is certified + magisk hide)
Anyway you can change when you want with darcy, foster_e_hdd but is not necessary.