[ROM] [S9/S9+] [UNOFFICIAL] [LineageOS 18.1] [Exynos] [Weekly]

[Speedmatze]

Just out of curiosity, before I dig into this further, have you tried using the MS Outlook app from the Aurora Store?

Yes, tried it and it is not great. More importantly though it is blocked as client from the Exchange server in question because of security issues. I could probably get around that by faking the client ID but that would not be worth the trouble for that app...

 

[Neurotical]

First of all: Congratulations to your new born! Best of all reasons to take a break and adjust to the new life.
Second: Still great to have you back.

Thank you for keeping our S9s alive with your continued ROM support.
I would just have one request:
I am using LOS with MicroG instead of Gapps and need MS Exchange connectivity to sync a calendar. Until LOS17.1 it was easy to get this to work with the standard Email app. Unfortunately that is no longer included in LOS18.
Would it be possible to include the old version into your ROM to get MS Exchange back (as described here )?

I tried checking out the link referenced: https://github.com/bananer/android_manifests/blob/master/apps_from_17.1.xml but it is no longer available. Is there another source for this manifest?

 

[Neurotical]

All trees are here https://github.com/ArrowOS-Devices
you can pick the commits to your tree or just use the same trees (common tree and kernel tree)

So if we sync the LOS 19.0 repo and use the following repos in our roomservice.xml:

https://github.com/ArrowOS-Devices/android_kernel_samsung_universal9810 (branch Arrow-12.0)
https://github.com/ArrowOS-Devices/android_device_samsung_universal9810-common (branch Arrow-12.0)
https://github.com/ArrowOS-Devices/android_device_samsung_starlte (branch Arrow-12.0)
https://github.com/LineageOS/android_hardware_samsung (branch lineage-19.0)

The compile will work? Are these only items you included in your roomservice.xml when compiling LOS 19.0 for starlte?

What about the proprietary_vendor_samsung repo? Would this one suffice?
https://github.com/Geoknyda/proprietary_vendor_samsung (branch lineage 18.1)

 

[CyderXDA]

So if we sync the LOS 19.0 repo and use the following repos in our roomservice.xml:

https://github.com/ArrowOS-Devices/android_kernel_samsung_universal9810 (branch Arrow-12.0)
https://github.com/ArrowOS-Devices/android_device_samsung_universal9810-common (branch Arrow-12.0)
https://github.com/ArrowOS-Devices/android_device_samsung_starlte (branch Arrow-12.0)
https://github.com/LineageOS/android_hardware_samsung (branch lineage-19.0)

The compile will work? Are these only items you included in your roomservice.xml when compiling LOS 19.0 for starlte?

What about the proprietary_vendor_samsung repo? Would this one suffice?
https://github.com/Geoknyda/proprietary_vendor_samsung (branch lineage 18.1)

you can. and you don't need the android_hardware_samsung I think. Just use kernel, common trees, devices trees and vendor from arrow and build, then it should build and boot.

 

[king1990]

So if we sync the LOS 19.0 repo and use the following repos in our roomservice.xml:

https://github.com/ArrowOS-Devices/android_kernel_samsung_universal9810 (branch Arrow-12.0)
https://github.com/ArrowOS-Devices/android_device_samsung_universal9810-common (branch Arrow-12.0)
https://github.com/ArrowOS-Devices/android_device_samsung_starlte (branch Arrow-12.0)
https://github.com/LineageOS/android_hardware_samsung (branch lineage-19.0)

The compile will work? Are these only items you included in your roomservice.xml when compiling LOS 19.0 for starlte?

What about the proprietary_vendor_samsung repo? Would this one suffice?
https://github.com/Geoknyda/proprietary_vendor_samsung (branch lineage 18.1)

hardware/samsung is not needed, we only uses livedisplay and touch hidl, I added livedisplay in this branch https://github.com/baddar90/android_device_samsung_universal9810-common/tree/aosp-livedisplay and will add touch hal later but to start up you can use the above repos until I make a clean los19 branch.
for vendor, use the one in arrowos devices will fix ok google.

The rom will compile and boot fine as tested before. Goodluck

 

[king1990]

GitHub - francoism90/android_device_samsung_starlte

Contribute to francoism90/android_device_samsung_starlte development by creating an account on GitHub.

github.com

GitHub - francoism90/android_device_samsung_exynos9810-common

Contribute to francoism90/android_device_samsung_exynos9810-common development by creating an account on GitHub.

github.com

GitHub - francoism90/android_kernel_samsung_exynos9810

Contribute to francoism90/android_kernel_samsung_exynos9810 development by creating an account on GitHub.

github.com

I tried building LOS 19, but I get a lot of SELinux errors everytime I compile it and it ends up in a bootloop when I want to use it.

the common tree does not look good at all , I don't think it will work like that. use my branch for livedisplay and all other repos from arrowos devices (don't use hardware/samsung).

 

[Speedmatze]

I tried checking out the link referenced: https://github.com/bananer/android_manifests/blob/master/apps_from_17.1.xml but it is no longer available. Is there another source for this manifest?

Here are the contents of the xml file:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
   <!-- commented out in https://github.com/LineageOS/android/blob/lineage-18.1/snippets/lineage.xml -->
   <project path="packages/apps/Email" name="LineageOS/android_packages_apps_Email" revision="lineage-17.1" />
   <project path="packages/apps/Exchange" name="LineageOS/android_packages_apps_Exchange" revision="lineage-17.1" />
   <project path="packages/apps/UnifiedEmail" name="LineageOS/android_packages_apps_UnifiedEmail" revision="lineage-17.1" />
</manifest>

 

[francoism90]

the common tree does not look good at all , I don't think it will work like that. use my branch for livedisplay and all other repos from arrowos devices (don't use hardware/samsung).

Thanks for your honest feedback.
I'll checkout livedisplay and others in hidl.

Just one question, should we also use vibrator and power? It seems to work fine using the ones seen in 9820.

Also about SELinux rules, I notice this is missing, why?

PS. I'm just trying to learn, just asking for feedback.

 

[king1990]

Thanks for your honest feedback.
I'll checkout livedisplay and others in hidl.

Just one question, should we also use vibrator and power? It seems to work fine using the ones seen in 9820.

Also about SELinux rules, I notice this is missing, why?

PS. I'm just trying to learn, just asking for feedback.

The vibrator and power hal are already precompiled and used in the tree. Selinux is not missing. Trees are enforcing, only encryption is the major bug.

First boot your build then you can modify the tree as you like using this tree as a base.

Also try to keep authorship , your commits in the kernel tree are without any authorship which is not encouragd in open source work.

 

[francoism90]

The vibrator and power hal are already precompiled and used in the tree. Selinux is not missing. Trees are enforcing, only encryption is the major bug.

First boot your build then you can modify the tree as you like using this tree as a base.

Also try to keep authorship , your commits in the kernel tree are without any authorship which is not encouragd in open source work.

This is what I'm asking about SELinux (most of the things I'm comparing against 9820 sources):

BOARD_SEPOLICY_TEE_FLAVOR := mobicore
include device/lineage/sepolicy/exynos/sepolicy.mk
include device/samsung_slsi/sepolicy/sepolicy.mk

Also why is it pointing to private and not vendor? Aren't the policies 'vendor' related?

Thanks!

 

[king1990]

This is what I'm asking about SELinux (most of the things I'm comparing against 9820 sources):

BOARD_SEPOLICY_TEE_FLAVOR := mobicore
include device/lineage/sepolicy/exynos/sepolicy.mk
include device/samsung_slsi/sepolicy/sepolicy.mk

Also why is it pointing to private and not vendor? Aren't the policies 'vendor' related?

Thanks!

You don't need to modify anything if your aim to boot los19. Use arrow trees and you will be fine. However I can't help you with your trees specially when there are two devs working on completely new trees. I would suggest to use the available trees which are perfectly fine or wait till new trees are made public.

 

[Neurotical]

FYI weekly update includes:

• Security patch updated to January 5, 2022.
• MS Exchange feature added.
• Legacy LOS 17.1 e-mail app added.

Now available via OTA or OP.

Have a nice day

 

[jer194]

Thanks for maintaining this ROM!

For those who want to use microg instead of Google Apps,
would you mind to add Signature Spoofing Support from here:

docker-lineage-cicd/android_frameworks_base-R.patch at master · lineageos4microg/docker-lineage-cicd

Docker microservice for LineageOS Continuous Integration and Continous Deployment - docker-lineage-cicd/android_frameworks_base-R.patch at master · lineageos4microg/docker-lineage-cicd

github.com

lineageos4microg so far does not seem to provide ROMs for starlte
(probably because there is no official LOS 18.1).

 

[Neurotical]

Thanks for maintaining this ROM!

For those who want to use microg instead of Google Apps,
would you mind to add Signature Spoofing Support from here:

docker-lineage-cicd/android_frameworks_base-R.patch at master · lineageos4microg/docker-lineage-cicd

Docker microservice for LineageOS Continuous Integration and Continous Deployment - docker-lineage-cicd/android_frameworks_base-R.patch at master · lineageos4microg/docker-lineage-cicd

github.com

ineageos4microg so far does not seem to provide ROMs for starlte
(probably because there is no official LOS 18.1).

mkdir ~/spoofpatch && cd ~/spoofpatch && wget https://github.com/lineageos4microg/docker-lineage-cicd/blob/master/src/signature_spoofing_patches/android_frameworks_base-R.patch && wget https://github.com/lineageos4microg/docker-lineage-cicd/blob/master/src/signature_spoofing_patches/packages_apps_PermissionController-R.patch && wget https://github.com/lineageos4microg/docker-lineage-cicd/blob/master/src/signature_spoofing_patches/frameworks_base_config.xml


mkdir -p ~/android/lineage/vendor/lineage/overlay/microg/frameworks/base/core/res/res/values && cp ~/spoofpatch/frameworks_base_config.xml ~/android/lineage/vendor/lineage/overlay/microg/frameworks/base/core/res/res/values/config.xml
cd ~/android/lineage/frameworks/base && patch -p1 -i ~/spoofpatch/android_frameworks_base-R.patch
cd ~/android/lineage/packages/apps/PermissionController && patch -p1 -i ~/spoofpatch/packages_apps_PermissionController-R.patch

With this custom script I was able to successfully add in signature spoofing support

I will be releasing a ROM update OTA in the next few hours

 

[Neurotical]

FYI new update includes:

• Signature spoofing support.

Available via OTA or OP.

Have a great evening

 

[jer194]

Cool, thanks a lot!

It also enables the 'google-less' exposure notification framework,
for the Corona Warn App eg.

 

[leap_ahead]

Any info how to flash lineage recovery from stock ?

 

[Neurotical]

Any info how to flash lineage recovery from stock ?

Samsung Galaxy S9+ (star2lte) - LineageOS ROMs

LineageOS ROM Samsung Galaxy S9+ (star2lte)

lineageosroms.com

This official Lineage guide for the Starlte explains how to upload the custom recovery. It explains how to use heimdall to flash a recovery file using the following command:

heimdall flash --RECOVERY <recovery_filename>.img --no-reboot

 

[HQwarp]

Thank you @Neurotical for your effort on the building the ROM, for a moment I thought I needed to get back to the not so great Arrow OS. Congratulations on the newborn!

I see that there are attempts to use Arrow OS sources. Let me add two other features to the not working well list on Arrow OS and more reasons to use Lineage sources.

First, the build-in keyboard Arrow OS has doesn't support dictionaries and spell check for many languages that are supported build-in by LOS. Besides English, Spanish, and maybe another language, other languages have very basic or non at all support. It is important for people that love their privacy, especially now with your help with adding spoofing to the ROM.

Second, Arrow OS has a battery optimizer feature that has too many bugs, even if the feature is not enabled. In my setup, I needed to reformat my phone, because, of a bug that appears from time to time that prevents charging the battery. This is hugely inconvenient especially when this feature is disabled all the time and I never use it.

 

[Speedmatze]

FYI new update includes:

• Signature spoofing support.

Available via OTA or OP.

Have a great evening

Just installed the new version. Exchange integration and signature spoofing are working nicely!
These additions of the last two build have just made (installation and update) life much easier for non-google users.

Thank you!