Develop Bugs

[KEXEC] [ARM64] Kexec-Hardboot Patch

Note:
Kernel Developers: I would like to ask you to merge this patch to your kernels, because it is essential part of MultiROM (MR) - it allows MR to boot any kernel without changing the boot partition. I realize that it is no small request, but the patch is not big, touches relatively stable parts of kernel and should not cause any problems outside its intended function.
The Patch:
You'll need to cherry pick a total of 5 commits (if anyone feels like squashing them to help me out, feel free to link me to it).
Cherry-pick against: http://github.com/multirom-nexus6p/android_kernel_huawei_angler.git on the branch 'mm2'.
Commit hashes in order:
2641ac7979c0b4ef7d8c33bae57404fea89ca0de
ff67f9fae243fea2b513b1721c8cff4584f229ba
58154995579253a2ee864b839aa4a9271afdb1c5
fb7e7c6212f59fce48f83235a99c244e2432b1f3
1fb02d265b4170e193018d513de11f9a47e5e775
Related defconfig options, and their explanations:
Code:
CONFIG_KEXEC=y # Enables the Kexec SysCall to allow loading the new 'secondary' kernel into memory
CONFIG_KEXEC_HARDBOOT=y # Enables the HardBoot flag, which allows 'cold-booting' a new kernel
# CONFIG_ATAGS_PROC is not set # Prevents potential atags related discrepancies, this must be either removed or commented out
CONFIG_PROC_DEVICETREE=y # Allows us to read out the kernel config, and tell that the kernel has all the necessary configs enabled (read out from /proc/config.gz)
User-space Kexec binary: here (you'll need to extract the zip, and it will be in 'multirom/kexec')
A quick guide to use Kexec: here
Authors:
- This patch was made by Mike Kasick for Samsung Epic 4G.
- Tassadar built on this patch, and partially rewrote it to support the Nexus 4, 5, and 6.
- Zhuowei Zhang rewrote the patch from scratch for arm64.
- Myself for maintaining MultiROM for the 6P, and managing the patch.
XDA:DevDB Information
[KEXEC] [ARM64] Kexec-Hardboot Patch, Kernel for the Huawei Nexus 6P
Contributors
npjohnson, 500 Internal Server Error
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: Version 1
Stable Release Date: 2016-06-11
Created 2016-06-12
Last Updated 2016-06-12

None of the above links working
The links of commits you have mentioned are not working.

shenoy13 said:
The links of commits you have mentioned are not working.
Click to expand...
Click to collapse
Been a long while, because the related MultiROM project is no longer maintained, but the links now work

[ROM][Z3/DUAL] LineageOS 14.1 [Updated 11/21][UN-OFFICIAL]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What it is
LineageOS 14.1 is built from official LineageOS sources devices trees and fresh caf 3.4 kernel port. This rom is worked to be as stable as possible to be used as a daily driver.​
Disclaimer
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Who can use it
It's only for Z3/DUAL users with UNLOCKED UPGRADED BOOTLOADER (Devices on 23.5.A.1.291 release)​
How to install
First time install:
Make sure your rom is on 23.5.A.1.291 (Marshmallow release)
Power of the device and go into fastboot mode (plug usb + vol down key = blue led)
Flash latest TWRP version | If you are a Dual user, flash zip below before installing Dual version. / Also, if you already have a working TWRP (kernel/adv kernel) you can use the flashable zips below instead.
Shutdown the device
Maintain volume down & power until you see twrp splash screen
Wipe system, dalvik/cache and data
Install rom zip (+ gapps if you need it)
Reboot
Rolling back to Stock
Flash stock rom with emma or flashtool
If you flash with flashtool remember to check wipe apps_log and userdata partitions to get a clean install
LATEST RELEASE
2017-11-21:
Xperia Z3/Dual
Download
Xperia Z3: TWRP 3.1.1 - 2017/08/25
Xperia Z3 Dual: TWRP 3.1.1 - 2017/08/25
Previous release: https://drive.google.com/file/d/0B5VgArZxRLnTWk50dVpqeFFENE0/view?usp=sharing
Code:
[INDENT]
[B]What's new[/B]:
- Fixed some RIL issues
- Hybrid builds (Z3 and Dual support in one package)
- November security updates
[/INDENT]
About TWRP
To access Recovery press Power On+Volume Down button with your phone off.
If it's your first time flashing it, unpack recovery.img and flash it via fastboot with the following command: fastboot flash FOTAKernel <filename>
Release Timeline
Code:
2017-10-21
- KRACK vulnerability fix
- Bluetooth CVE-2017-1000251
2017-10-10:
- Minor device init cleanup
- October security updates
- Updated Adreno RenderScript driver
2017-09-26:
- September security patch
- Blueborne vulnerability fix
- Default AVRCP to 1.4
- Native DC_HSPAP support
- Disabled VOIP Compress offload (use standard path instead)
- Updated netmgrd service
2017-08-25:
- Removed In-Device Diagnostics (not needed anymore)
- Removed old Google Widevine implementation
- Updated Sony specific binaries
- Updated configuration files for Radio/Data
- Updated Phone Vibrator settings
- Partially updated Sepolicy
- Added CPU configuration for TWRP
- Fixed TWRP usb mode for file transfer (when plugged in MTP mode is enabled)
- Fixed ADB support for TWRP (you can use "adb shell" command now)
2017-08-08:
- August security fixes
- Fixed daily reboot issue
- Fixed NFC Payments
- Fully updated blobs to Stock .291 (SHA1 sum verified)
- Fixed device build fingerprint (for upcoming builds with SafetyNet enabler mode)
- Cleaned a lot the device init files
2017-07-27:
- Fixed mac addresses
- Fixed device permissions
- Updated blobs
2017-07-22:
- Reworked init for MPdecision Android/TWRP
- Fixed audio crashes
- Updated mixer_paths
- Phone init cleanups
- Updated RIL
- Sepolicy denial fixes
- Final bluetooth audio calling fixes
2017-07-17:
- Added Sony device identifier for PlayStore (now you can download sony apps straight from playstore)
- Updated TWRP build.
- [URL="https://cve.lineageos.org/android_kernel_sony_msm8974"]Lots of kernel CVE fixes[/URL]
- Fresh .291 blobs
- Updated fstab
- Improved power config for os and recovery
- Added back 44100Hz audio output
- Bluetooth audio fixes
- AVRCP 1.5 enabled
2017-07-07:
- Official welcome back MPDecision!
- July 5 Security Patch
- Kernel patches
- Enabled AVRCP 1.5 Profile again
- Experimental 3AM reboot fix (Needs feedback)
2017-07-01:
- Updated Camera profiles
- Reworked Z3 Dual RIL (again)
- Stock led color pattern for battery charging
- Reworked thermanager
- Cleaned up init files
- More autobrightness tweaks
- Kernel security patches
- Added Hexagon DSP services
- Fixed init permissions
- Latest firmware for BCM4339 WiFi/BT/Radio chip
- Some minor audio changes to adress issues
- Changes to BT audio devices. (AVRCP-HFP)
Sources
Repository
Liking my work? A donation is always helpful to make up with real life expenses
XDA:DevDB Information
LineageOS, ROM for the Sony Xperia Z3
Contributors
xkeita
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2017-10-10
Created 2017-07-02
Last Updated 2017-11-25

What is not working
HW Encryption, --> 2017-04-16
60/120fps video recording
How to post
Reports without logs or step to reproduce are useless (read contribute).
Substratum is officially not supported into Lineage.
You are welcome to post your review: what is working, not working, etc... Check into know issues before.
You are welcome to report any typo, error, etc...
Try to keep thread clean as a dev reference. Thanks in advance.​
How to report problems
How to get logs
Here you have some info about how collecting log. It is always better to include reference to the Installed version. This guide is really detailed and explained everything about bug reports.​How to contribute
Code is like hieroglyphs for me:
No worries you can contribute anyway! Install the rom, do tests, read failure logs, look at internet for potential fix/similar users experience, is the biggest part of debugging. Then collect all of this and write your results here.
Code is like hieroglyphs for me and logs are worst:
No problem, collects logs the right way if you can, explain how you encounter the problem: detailed step to reproduce could be enough: explain exactly how you encounter the error/problem, it should produce each time someone repeat your steps. Then we will be able to fix it.

Credits : A big nyan to them!
Head developers
@xkeita
@tomascus
@nailyk
External contributors
@derf elot​
Testers
@tomgus1
@gr8st
@mcgi5sr2
@doriandiaconu
@Robot76
@panzerox123​

Downloading

Thanks for all your work, a years ago it was totally impossible tout imagine such a stable rom so thanks for all the team.
Will you add stock camera app to this rom ?
It may be a silly question but since Lineage OS add hardware fonctionnality that are device-specific, do you and LOS consider sony stock camera fonctionnality (and by extension app) as hardware fonctionnality that are sony-devices-specific ?
PS: sorry if there is any typo or mistakes, my french corrector just f*ck-up all my other-language-writed text x)
PPS: thanks to xda labs, that the fifth time I try to upload this message, I hope that you can read it entirely
PPPS: I gived-up with XDA Labs, This is send with my computer

Moiremoi said:
Thanks for all your work, a years ago it was totally impossible tout imagine such a stable rom so thanks for all the team.
Will you add stock camera app to this rom ?
It may be a silly question but since Lineage OS add hardware fonctionnality that are device-specific, do you and LOS consider sony stock camera fonctionnality (and by extension app) as hardware fonctionnality that are sony-devices-specific ?
PS: sorry if there is any typo or mistakes, my french corrector just f*ck-up all my other-language-writed text x)
PPS: thanks to xda labs, that the fifth time I try to upload this message, I hope that you can read it entirely
PPPS: I gived-up with XDA Labs, This is send with my computer
Click to expand...
Click to collapse
xkeita, nailyk and tomascus wanna go official first, so there is no need to think about porting some apps right now

sheng_zongxian said:
xkeita, nailyk and tomascus wanna go official first, so there is no need to think about porting some apps right now
Click to expand...
Click to collapse
It's not about porting ^^
In every LOS rom, there is some system apps that are device-specific (I think of the off-screen gesture in OnePlus device)
For our device I think about our DRM. It add a lot of optimization for image processing.
So I just ask the devs if they consider DRM and other image processing as equivalent thing to off-screen gesture

Moiremoi said:
It's not about porting ^^
In every LOS rom, there is some system apps that are device-specific (I think of the off-screen gesture in OnePlus device)
For our device I think about our DRM. It add a lot of optimization for image processing.
So I just ask the devs if they consider DRM and other image processing as equivalent thing to off-screen gesture
Click to expand...
Click to collapse
Install it

I've installed it, and it looks amazing as far as the smoothness and speed is concern though i have to check the battery usage and other apps.. will report later.

Hi rum thanks for being nice and stable for rum, but there is a brilliance error and over heating

Moiremoi said:
It's not about porting ^^
In every LOS rom, there is some system apps that are device-specific (I think of the off-screen gesture in OnePlus device)
For our device I think about our DRM. It add a lot of optimization for image processing.
So I just ask the devs if they consider DRM and other image processing as equivalent thing to off-screen gesture
Click to expand...
Click to collapse
you could ask them again later , when they have made this ROM OFFICIAL for us

report

nailyk said:
Install it
Click to expand...
Click to collapse
Already done
And for those who want it too, here is our framework.jar patched => here <=
(And here, the post where you can download the app)
DON'T FORGET TO WIPE DALVIK/CACHE

Is there a way to disable the orange theme for battery saving mode ? And completely disabling the rotation for the magnet charger?
Otherwise this ROM is super nice! Thanks for your great work!

Thanks for the update! Unfortunately, calls over BT are still not working on my end. (Build. 20170701 - D6603 - Sony SBH20)
This time I didn't pair my smartwatch just to see if that was the issue, doesn't seem like it.
Here's the full logcat and dmesg.
Logcat (Over 512kb so I had to upload it elsewhere)
Hopefully this info will help you guys out.
Cheers!

Canneloni said:
Is there a way to disable the orange theme for battery saving mode ? And completely disabling the rotation for the magnet charger?
Otherwise this ROM is super nice! Thanks for your great work!
Click to expand...
Click to collapse
LineageOS feature. You should be able to change the amount into settings.
On internet you probably can find some way to put that amount to 0.

There is any possibilities to upgrade this kernel (through modifications) into 3.10 or 3.18 keeping camera blobs? @xkeita @nailyk

Ahh .. paused charging is back . It's not bad stuff anyway , just in my country where is hot throughout the year is a lil bit annoying when ur battery low and u can't charge the phone because it's hot .

Canneloni said:
And completely disabling the rotation for the magnet charger
Click to expand...
Click to collapse
+1 for this. The device enters Desk Dock mode when a magnetic charger is used, which is really annoying, as it also interrupts Car Dock mode.
@nailyk: What about the Disable Desk Dock sources that I pointed you to?

I noticed a small amount of lag in the camera of the new build (lineage-14.1-20170701-xkeita-z3dual). Previously, I used the version (lineage-14.1-20170629-nailyk-z3dual). Nothing that harms me much. I just came to ask if the other members had the same problem, so I could know how to act.

[NEW][Kernel] Entangled Kernel V1.0 [Alpha][X3][SscSPs]

Hey people,
I am glad to introduce my new Kernel to you guys,
Entangled Kernel​
Currently, I have not added any extra feature, except that you can use your phone as a USB keyboard and mouse on your PC,
for that you need to have an app that can work with it.(check out this Github Repo for more info: https://github.com/pelya/android-keyboard-gadget)
I have enabled F2FS on this kernel as well,
Currently, I need people to test out its battery backup and provide feedback about performance and bugs
Currently Known Bugs:
None
You tell me of you find any!
Instruction are just as usual, if you need help, head to the "Post #3" of this Thread.
Update Logs are available in "Post #2" of this Thread.
Download Links are over at Android File Host!
Feature requests are welcome, you can post your feature requests here, or head over to github and open a new issue for bug report and/or feature requests.
XDA:DevDB Information
Entangled Kernel, Kernel for the LeEco Le 1S
Contributors
sscsps
Source Code: https://github.com/Le1s/android_kernel_leeco_x3
Kernel Special Features: Fully upstreamed with Google's updates
Version Information
Status: Alpha
Created 2018-01-07
Last Updated 2018-01-07

LineageOS 15.1 | 09.03.2020 | Shield blobs

LineageOS 15.1​
FOR ROMS RELEASED BEFORE NOVEMBER 2018
Requirements:
1) active system1
2) merged system partition
Instruction
1) flash BootBlobs-SHIELD-mocha.zip
2) reboot to recovery
3) install this recovery
4) reboot to recovery
5) install the ROM
FOR ROMS RELEASED AFTER NOVEMBER 2018
Requirements:
1) active system1
2) merged system partition
3) BRAIN, READING SKILL and presence of basic knowledge about firmware (in the absence need learn to independently)
Instruction
1) download TosForPSCI-0.1.zip
2) unzip TosForPSCI-0.1.zip
3) download recovery-03.11.2018
4) go to fastboot mode
5) execute command: fastboot flash tos your path to tos.img
6) execute command: fastboot flash recovery your path to recovery-03.11.2018.img
7) reboot to new recovery(u can execute fastboot reboot holding vol+ button)
8) if you are on previous LineageOS 15.1 build then you may install the ROM without wipes. If you're not, make full wipes then
9) install current LineageOS 15.1 build
10) reboot to the system
Sources
Device
Kernel
Vendor
Changelogs
09.03.2020
system:
- the latest security patch
- audio HAL from miui(It may solve a couple of problems with sound, but it can break something else)
13.02.2020
system:
- the latest security patch
- fixed OMX(video playback hardware acceleration now works)
28.12.2018
system:
- the latest security patch
kernel:
- a little bit updated sdcardfs
- fixes of defects after switching to the new Synaptics touchscreen driver
12.11.2018
System:
- source code was updated
- added tile for activatingdeactivating battery charging
- free form window mode
kernel:
- PSCI downgraded to version 0.1
10.10.2018
System:
- source code was updated
kernel:
- new Synaptics touchscreen driver(possibly less lags)
- a little bit updated sdcardfs
- fixed a couple of security issues when using root
11.09.2018
System:
- source code was updated
kernel:
- reworked binder driver(the system should be more stable)
11.08.2018
system:
- source code was updated
kernel:
- dvfs driver was heavily updated(better power consumption)
- binder was updated
- therm_est thermal sensor was fixed
15.07.2018
system:
- source code was updated
- changes for devices with 3Gb RAM
kernel:
- added new driver(written by me) for reducing cpu power consumption in suspend mode.
- panel driver was changed for reducing power consumption in suspend mode
- palmas gpio driver was changed for reducing power consumption in suspend mode
18.06.2018
system:
- source code was updated
kernel:
- spectre patch by nvidia
- other small changes
15.05.2018
system:
- source code was updated
- software video playback in some apps was fixed
- usb internet sharing was fixed
- other small changes
kernel:
- sdcardfs was updated to the 3.18 kernel level.
- ability to change display colors was added
06.04.2018
system:
- sdfat was added(instead of vfat and exfat)
- microphone was fixed(broken in the 31.03 build)
- a lot of fixes in the device tree
kernel:
- sdcardfs was updated to the 3.18 kernel level.
- cpustats was updated
- sdfat was added
- fixed loading address of the kexec-hardboot
- ambient capabilities was added
30.03.2018
New:
- gyroscope
- 64-bit binder
- adjustable buttons backlight brightness
23.03.2018
The second public build
22.03.2018
The first public build
Broken:​- Cameras
- Video playback hardware acceleration
Download:​Touchscreen hotfix for ROM released at 29.12.2018
ROM folder
Last build
XDA:DevDB Information
LineageOS 15.1, ROM for the Xiaomi Mi Pad
Contributors
Artemka2008
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Created 2018-10-07
Last Updated 2020-03-09

09.03.2020
system:
- the latest security patch
- audio HAL from miui(It may solve a couple of problems with sound, but it can break something else)
What is "tile for activating\deactivating battery charging"?
- this is system icon(like performance profiles) which permits\prohibits the supply of current to the battery at the time when the charger is connected.
Why do we need that tile?
- if you play, watch a movie or perform another costly action, then activating this mode will save the battery from unnecessary wear because energy will go directly from the charger. But you need a fairly powerful charger, if the power of the charger is not enough, then partially the consumption will be compensated by the battery.
What happens if you do not install TosForPSCI-0.1?
- at best, only one CPU core will be active. At worst, the recovery will not be started (if it has not been updated too) and the system too.
How to roll back on the firmware version, which came out before November?
- download TosForPSCI-0.2 and recovery. You'll be able to flash older ROMs after installing them
Why do I need to lower the PSCI version from 0.2 to 0.1?
- Using version 0.1 fixes a problem with shutting down a device.

does this have any bugs?

What is this? Felt like new tablet.

I flashed the latest ROM 10.10.2018 yesterday. The Wi-Fi is unusable - after the tablet goes into sleep for some time, when you wake it up, the Wi-Fi connection is gone (meaning it doesn't see any SSID at all). Turn off/on the Wi-Fi does not help. Only way is to reboot the tablet. Any suggestions?

staying on 14.1 due to only video hardware acceleration

Is it possible to flash LOS 15.1 without the shield blobs?
Is it possible to fix the camera by changing the permission of the build .prop file?

Great Build!! Keep it up!

There is one issue in display. The screen flickers some times while using the device.

StarkAhmed said:
Is it possible to flash LOS 15.1 without the shield blobs?
Is it possible to fix the camera by changing the permission of the build .prop file?
Click to expand...
Click to collapse
Lol. No, it's not

Artemka2008 said:
Lol. No, it's not
Click to expand...
Click to collapse
By the way what are shield blobs and what happens to my mi pad when I flash LOS without the blob?

I cant install it. Error 7 in flashing. Any idea how can i fix it?

Guys, install shield blobs properly before installing this. Read the main post carefully.

Requirements:
1) active system1
2) merged system partition - how i can marege partiton?
---------- Post added at 04:25 PM ---------- Previous post was at 03:40 PM ----------
I try everything but don't work on my mi pad....

"I flashed the latest ROM 10.10.2018 yesterday. The Wi-Fi is unusable - after the tablet goes into sleep for some time, when you wake it up, the Wi-Fi connection is gone (meaning it doesn't see any SSID at all). Turn off/on the Wi-Fi does not help. Only way is to reboot the tablet. Any suggestions?"
Hi, I also experienced the same problem. Turning airplane mode on then off solved the problem, wireless networks showed up and mipad connected automatically.

@Artemka2008 I am upgrading from October build to November. Should i remain in shield blobs or go back to mocha blobs? I can see from your instructions that for ROMs from November, flashing shield blobs is not necessary.

Can't get the lastest rom to boot. Reverted back to Tos 0.2 and used the recovery before November, still not booting, stuck on MI logo.
Never experienced any problems before. Any suggestions are welcome

Same with me. Stock with mi logo. But other roms work.

Identity77 said:
Same with me. Stock with mi logo. But other roms work.
Click to expand...
Click to collapse
Which roms are working? And are you on the PSCI-0.1?

Palm Trees said:
Which roms are working? And are you on the PSCI-0.1?
Click to expand...
Click to collapse
Im on psci0.1 now and aospextended 8.1. touch to wake dont work in this november roms. Only lineageOS doesnt work for me. Its stock in mi logo

[ROM][EXYNOS] LineageOS 18.1 for S10e|S10|S10+ - v2.2 (UPDATE: 2021-07-23)

- - - - - -
This project provides LineageOS with SELinux for the Samsung Galaxy S10e (SM-G970F, beyond0lte), S10 (SM-G973F, beyond1lte) and S10+ (SM-G975F, beyond2lte).
- - - - - -
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FEATURES
We provide a secure and up to date ROM, check the Lineage Trust status of your phone!
Secure ROM
Fine-grained SELinux policy
Latest 4.14 Linux Kernel release
Improved performance
Wireguard support
USB restrictions
AES-256-XTS File Based Encryption (FBE)
Signed with developer keys
Nice features
FDroid and AuroraStore preinstalled
Bluetooth phone calls
KNOWN ISSUES
Don't be scared by the "BETA" label. Our ROMs are always rock solid.
Some audio effects are missing
Miracast not working
Wideband SCO
IMS not working (No AOSP solution yet)
Some minor issues are described in the FAQ below.
DOWNLOAD
You can download the latest version under the following links:
S10e
S10
S10+
INSTALLATION
Put the zip file of the ROM on your external SD card boot into recovery. If you use our TWRP recovery, you should use that one to flash the ROM.
Make sure you select: Zip signature verification.
This will verify that the signature of the ROM will match the one in TWRP recovery. A more detailed step by step description is in the FAQ below.
SECURITY ADVICE
Don't flash Magisk modules or anything else which sets SELinux to permissive or you open your device for malware!
Do not flash Multi Disabler on this ROM!
What a Wurst!
This ROM is developed by derf elot, linux4 and modpunk
Contributors
modpunk, derf elot, linux4
Source Code: https://github.com/whatawurst
ROM OS Version: Android 11
ROM Kernel: Linux 4.14.236
ROM Firmware Required: XXSBFUF3
Based On: LineageOS

REQUIRED FIRMWARE: XXSBFUF3
CHANGELOG
2021-07-23 | 2.2
Update to Linux 4.14.239
2021-06-23 | 2.1
Update to Linux 4.14.236
Fixed GPS
Improved autobrightness (Thanks to linux4)
2021-06-07 | 2.0
Added support to disable fast charging
Kernel fix to disable the touchscreen during handheld phone calls
Improved auto-brightness
2020-12-17 | 1.4
Add support for glove mode
2020-10-26 | 1.3
Update to Linux 4.14.206
2020-10-26 | 1.2
Update to Linux 4.14.202
Added Seedvault (Video)
Fixed bluetooth regression
Fixed NFC service registration (SELinux denials)
Fixed camera issues
Fixed LineageOS recovery
2020-09-11 | 1.1
Update to Linux 4.14.196
Added Kernel changes from CTG4 (fixes usb audio issues)
Improved DT2W support (thanks linux4)
Fixed camera access to some sensors
2020-08-08 | 1.0
Update to Linux 4.14.192
Performance improvements
New thermal HAL for better overheating protection
Fixed light sensor auto-brightness
Fixed extended-length NFC (required for ePerso App)
2020-07-13 | RC2
Update to Linux 4.14.188
Fixed reboot issue with new Power HAL
Fixed crash issue with power HAL
Update to latest Security release
Removed su for adb root
2020-07-06 | RC1
Update to Linux 4.14.187
Performance improvements (new power HAL)
2020-06-17 | BETA3
Update to Linux 4.14.184
Update to Wireguard 1.0.20200520
Fixed HDR support
Upstreamed vibrator service implementations
2020-05-20 | BETA2
Update to Linux 4.14.177
Added Wireguard support
Added support for L1 widevine security level (Netflix etc.)
Added in-screen fingerprint support for S10(+)
Added "Wireless Powershare" support
Get the full list of sensors working, including tilt, rotation_vector, game_rotation_vector and pick_up_gesture
Fixed USB tethering
Fixed wifi hotspot
Fixed proximity sensor
Fixed phone calls over bluetooth
Fixed phone off charger with nice animation now
2020-04-14 | BETA1
Update to Linux 4.14.175
Added magisk building support
Added USB Trust HAL
Added "Always On Display" quick setting tile (merged upstream)
Fixed performance issues
Fixed video calls (e.g. in Signal)
Fixed proximity sensor
Fixed significant motion sensor
2020-04-05 | BETA0.1
Fixed Play Store
Fixed permission list
Added missing vendor properties
Fixed product definitions
2020-04-03 | BETA0
Initial release
OUR UPSTREAM EFFORTS
Common SELinux policy for Samsung devices
AOD Quick Setting Tile
In-screen fingerprint HAL for LineageOS
Powershare support for LineageOS
Common timed_out vibrator service for Samsung devices

Features + Known Bugs Summary:
This ROM does already support most features of the hardware. If you need specific features, please check the list below. Each feature was manually tested, so it is possible that it does not match your experience with the ROM. In this case please tell us, see the "Getting Help" section at the end of this post.
Ratings Description
++ perfect (in depth tested, performs like stock or better)
+ good (lighly tested only or has minor flaws but is good enough for normal use)
o ok (can be used with some limitations)
- broken (doesn't work at all)
x not supported (unlikely to be implemented, relies on samsungs closed source code)
? can't test, please give feedback
Performance
++ geekbench 5 score: 2267 (gsmarena stock: 2141)
++ antutu v8.4.1 score: 403909 (gsmarena stock: 389694)
Speed (values in MB/s, sr =seq. read, sw = seq. write, rr = random read, rw = random write)
++ internal SD 128GB
AndroBench5: sr 815.0, sw 193.1, rr 138.7, rw 24.7 (= notebookcheck stock)
CPDT 1GB: sr 735.3, sw 139.2, rr 19.2, rw 4.52
++ external SD, 128GB Samsung Evo Plus
Androbench5: sr 68.2, sw 34.5, rr 5.75, rw 2.56
CPDT 1GB: sr: 75.2, sw: 29.5, rr: 4.08, rw: 1.71
++ USB 3.0 MTP, sw 105MB/s (PC CrystalDiskMark -> mtpdrive -> internal SD)
++ USB 3.0 OTG, sw 105MB/s (Sandisk Extreme 64GB -> internal SD, 10.8GB file, 102s)
+ bluetooth file transfer, 0.1MB/s (29MB; from other phone 4m42s, from PC 5m24s) (theoretical max. is 0.3 for BLE4.0, 0.8 for BLE4.2 and 1.4 for BLE5.0)
Connectivity
++ phone calls, 3G, LTE; also with dual sim
++ wifi (delivers 50Mb/s, the maximum my provider supports)
++ bluetooth (file transfer to phone & pc; headphons incl. mic; speakers; keyboard incl. special keys)
++ NFC (only card read tested)
x VoLTE
Screen
+ 10 finger multitouch, "high touch sensitivity" mode not available
++ full brighness range available
++ double tap to wake
+ AOD works, but might be dimmer than stock and brightness cant be changed. While active the proximity sensor is used an its LED blinks dimly next to the camera
Sound
++ dual laudspeaker for media, quality as expected, high volume selectable
+ earpiece (no in depth test)
+ headphones (3.5mm jack) have clean audio, high volume selectable, limited to 16bit/48kHz (instead of 24bit/192kHz) possibly by ROM
+ build-in mic, limited to 16bit/48kHz (instead of 24bit/192kHz), volume should be normal (test)
+ headphone mic, limited to 16bit/48kHz (instead of 24bit/192kHz)
+ some external DACs supported, limited to 24bit/48kHz; (reported by @El Dun)
Camera (with opencamera + camera API v2)
++ wide, ultrawide, front, front-crop
++ PDAF autofocus, face tracking optional (main + front camera, ultrawide is always fixed focus)
++ manual setting for exposure/ ISO/ shutter/ focus
++ raw files option (main camera)
++ optional HDR
+ dual apperature (main camera), only manual switch (default f1.5)
+ video up to 2160p/30fps, 1080p/30fps (all cameras should support 60fps, but OpenCamera only produces 30fps files)
+ 1080p/240fps (main)/ 1080p/120fps (front) high speed/ slow-mo works in stock cam + GCam
x no 720p/960fps super slo-mo
x no supersteady
- S10, S10+: no telephoto camera (details + help wanted)
x S10+: no front depth camera
Sensors
++ gps, quick fix with A-GPS data
+ fingerprint (all variants), can glitch during setup (see bug list)
++ accelerometer, gyroscope, magnetometer, pressure, light (front) (all values are within tolerance)
+ light sensor, but only the front/ under-screen sensor, not the rear sensor
++ IR/RGB sensor outputs values for IR/Red/Green/Blue/Clear (test) (COM.SAMSUNG.SENSOR.LIGHT_IR)
++ grip sensor
+ front proximity (makes only one measurement per second, if you put it quickly to your ear it may touch the screen before it's turned off; reported by @Lav64)
++ software sensors: step counter, rotation vector, gravity, linear acceleration, compass
++ S10/S10+ heart rate/ SpO2 (confirmed by @Ned)
o several software sensors don't produce data, but don't do it on stock either. Affected are the IDs: PICK_UP_GESTURE, COM.SAMSUNG.SENSOR.PROXIMITY_POCKET, COM.SAMSUNG.SENSOR.HALLIC, COM.SAMSUNG.SENSOR.BIO_IR (proof thanks @Brembo109, more info from modpunk)
Charging & Battery
++ 15W quick charge
++ 4.75W reverse charge (with USB OTG adapter)
+ 7.5W+ qi-wireless charge (limited by my charger)
+ 2.5W+ reverse qi-wireless charge (limited by the receiver IC BQ51013)
+ low 40mW idle power consumption (details)
+ ACCA (advance charging controller app) works with limited settings
Misc
++ all buttons, bixby can be reprogrammed (workaround for other functions)
++ wired headphone buttons (pause/play, vol+, vol-)
+ flashlight has only one brighness option (instead of 5 on stock)
- S10e: no fingerprint swipe up/down geture, not even with 3rd party app "Quick Fingerprint Geture"
Known bugs:
when phone is shut down, it reboots instead (fixed in RC2)
reboot to recovery boots directly into system (fixed in RC2)
reboot takes long, about 30s (fixed in RC2, now it only takes a few seconds)
double tap to wake not always working (should be fixed in RC2)
holding fingerprint too long during setup can cause problems details
in full screen apps there may be a black bar to hide the camera cutout which can not be disabled (details, workaround)
high sensitivity touch screen / "glove mode" not available (details)
bixby-button hold-shortcut does not work (details)
google backup does not work with 4x4 or 5x5 pattern. This is an LineageOS issue, but important enough to deserve a note here. (details (thanks @Ivo_Todorov)
Installation:
How do I install this ROM on my phone for the first time?
Below you find a brief checklist of the required installation steps. Installation is more complicated than other ROMs because we take device security very seriously. If you are unfamiliar with installing custom roms , please click the links and read the additional details there.
Confirm the firmware version
Check the top of the ChangeLog which firmware version is required for the ROM release to work well
Go to settings/software-update and update only if the new version matches the requirement!
Alternative: flash with odin/heimdall (details see below)
Unlock your device
Backup all data, unlocking will factory reset your phone
Enable developer mode to and enable the OEM-unlock switch there
Turn off device and boot to bootloader (hold VolumeDown + Bixby, then connect USB cable)
Follow instructions on-screen
Finish the initial setup after unlock. You must connect to WiFi, but can skip everything else. Do not specify a pin/pattern during setup afterwards, otherwise TWRP may cause the "try again after 86400 seconds" issue (see below)
Confirm in the settings that the bootloader is actually unlocked. (greyed out, telling you its unlocked)
Install our TWRP (official thread) | more details (thanks @AndrOdin)
Download our TWRP recovery and the vbmeta-disabled.img file
Unpack the .xz file with 7zip
Check integrity of TWRP (optional, but important for security)
Rename files to recovery.img and vbmeta.img; then pack both files together in a .tar archive with 7zip
Install Samsung USB drivers and odin, (direct link)
Start odin as admin, disable "Auto Reboot" and click "AP "to select the .tar archive
Turn off device, boot to bootloader and, once odin detects it, click "Start"
When the screen turns off, immediately hold (and keep holding) VolumeUp + Bixby + Power to enter recovery mode
When the secondary warning appears, release everything but VolumeUp
Swipe slider to allow for modification
Install LinageOS
copy the ROM ZIP file an external SD card
Boot into the recovery
Wipe cache + dalvik (wipe->advanced and select cache + dalvik)
Format data (wipe->format data, use the dedicated button, wipe->advanced does not work)
Flash the ROM (install -> select storage -> micro SD card and select the .zip file)
Optional: Flash GAPPS (e.g. OpenGAPPS)
Reboot to system
How do I update LineageOS?
Updating LinageOS is a lot less work and you can keep all user data. The process is similar to the last part of the installation:
Backup all important files optional, but very helpful if something goes wrong)
Remove any pin/password/pattern to prevent "retry after 86400 seconds"
Copy the ROM ZIP file an external SD card or internal storage; download the new firmware files to PC (if needed)
Boot into the recovery, do not reboot until you've installed the new ROM and firmware
Flash the ROM (install -> select storage -> micro SD card and select the .zip file)
(Optional: Update GAPPS to the latest version)
Wipe dalvik and cache
Reboot to download
Flash new firmware with instructions below
(Optional: if you use Magisk, flash the new BOOT file. You can also do this in previous step instead of using Stef4n82's "BL.tar" file.)
Reboot to system
How do I update the firmware?
On the stock ROM you can update from the settings menu. You can't do this on lineageOS (yet), so ypu need to use use Odin or Heimdall instead.
How do I update the firmware manually?
Thanks to @Stef4n82's new instructions and repacked firmware files installation is easier than ever. Below you find a copy of his post:
If you use Heimdall:
Download the latest firmwarepackge for your device: "G97?F_Firmwareupdate_Heimdall_????.tar.gz"
Extract the package
Flash the firmware files with this command:
Code:
heimdall flash \
--BOOTLOADER sboot.bin \
--PARAM param.bin \
--UP_PARAM up_param.bin \
--CM cm.bin \
--KEYSTORAGE keystorage.bin \
--UH uh.bin \
--DTB dt.img \
--RADIO modem.bin \
--CP_DEBUG modem_debug.bin
If you use Odin:
Download the latest firmwarepackge for your device: "G97?F_Firmwareupdate_Odin_????.zip"
Extract the package and you will get an AP.tar, a BL.tar and a CP...tar.md5
Flash the 3 files with Odin (tested with latest Odin 3.14.x)
You can download the repacked firmware from the links below.
S10
S10e
S10+
If you don't want this repacked firmware packages and want to download the whole firmware by your own. Make sure if you flash it via Odin that you use this files:
From AP_G97?FXX*.tar.md5 take the dt.img and create a new AP.tar
CP_G97?FXX*.tar.md5
Extract BL_G97?FXX*.tar.md5 and create a new BL.tar without the vbmeta.img.lz4
Try again after 86400 seconds?
With newer version of the Samsung blobs, if you unlock the storage (/data) with TWRP (ie. you enter your pin/password/pattern in TWRP), the trustzone thinks it is a failed attempt and will lock the storage unlocking for 1 day (86400 seconds). To prevent this do not enter your pin (press cancel) and you can still flash an update. If you tripped the trustzone you can either wayt for 1 day to unlock your device (do not power it off) or try rebooting the phone a few times (thanks @Stef4n82), or this slightly more detailed guide (thanks @Exilion90)
You can prevent this completely by removing any pin/password/pattern before entering recovery. This does remove all stored fingerprints, so you'll have to set the up again after the update.
3rd Party Software:
How do I install Google apps?
You can download and install the Google Apps from Open Gapps Project. You need ARM64 and 10.x. We suggest to always use the pico package. If you need additional apps you find them in the Play Store.
Put the Open Gapps ZIP file on your SD card and flash it directly after you flashed LineageOS and before the first boot!
Can I use GPay? What about other banking apps
GPay as well as some other banking apps check if the device passes safetynet and will not start if it doesn't. Safetynet fails when the bootloader is unlocked and therefore this ROM will not run GPay and other applications that need it. This official LineageOS statement explains why safetynett will never by bypassed (by default).
Safetynet used to be easy to bypass with Magisk, but since an Update eralier this year Google uses the TPM module and that can't be circumvented easily. However there might be a workaround with "MagiskHide Props Config", please check out this post and this one. (thanks @Stef4n82) Please note that this has not yet been tested and we can not provide any support. If you got it working on your device, please share how you've done it so we can add it here!
How do I get MicroG with this ROM?
MicroG is an open source alternative to GAPPS. , but unfortunately not recently updated and therefore not recommended.
If you want to install it anyway, read this guide by @JoeRifle and this post (appendum) by @ned14 . Update: It has been reported that the new MicroG version works without issues. (thanks @ichmyselfandi)
Does this ROM have root?
Not by default. If you need root (eg. for AFWall) you can get it through Magisk.
How do I install Magisk?
Important security Advice: Don't flash Magisk modules or anything else which sets SELinux to permissive or you open your device for malware!
Option 1 (recommended):
Download the boot image for Magisk: S10e -- S10 -- S10+
Verify the integrity of the file -> See INTEGRITY
Unzip the boot image using xz or p7zip
(Needed for Odin) Rename the file to boot.img and use 7zip to pack it into a .tar file
Flash the boot image to the BOOT partition using Odin, Heimdall or TWRP
Install https://******************/
Option 2:
Patch TWRP
Which camera app do you suggest?
OpenCamera:
Great open source app that supports a lot of the camera's features with the camera API v2 (select this option in the settings):
All cameras supported (except telephoto, this is a issue with the ROM)
Manual change of exposure, aperture, shutter speed, ISO
The (main) developer uses an S10e himself so you can expect good HW support
You can get it from F-Droid or Play Store
GCam Variants:
There is no "official" GCam for this ROM, but there are some that work. Please read this excelent post by @ned14 for more details. The current recommendation is "GCam_5.1.018.177470874.41362666_IDan_N6_3.5_fix.apk" from (IDan). You need GAPPS, microG (post) or the Google Service Framework(post).
In comparison to OpenCamera it sacrifices manual controls + extra lenses for:
simpler user interface
better single-shot HDR
better panoramas + photospheres
SlowMo video (1080p @120/240fps)
I've also written a more detailed comparison. You can have both camera apps installed at the same time, so you can always choose the better one depending on the scenario.
Getting Help:
General:
Before you post, please check this FAQ, use the search function and skim the few last pages of this thread. We want LinageOS to work on your device, that's the whole point of this thread, but this way you can get the fastest help. If you did not find an answer, feel free to ask here We do this in out free time and it may take us some time to answer, so please be patient.
How to report a bug?
To fix any bug we first have to be able to reproduce it. Please include all relevant information:
device (S10e/S10/S10+)
ROM version
is gapps/ microg/ magisk installed?
steps to reproduce the issue
When in doubt it's better to include to 0much information than too little. A good example is @Sheffield Steve's bug report. Check out Simon's "How to Report Bugs Effectively" to write even better reports (and thus get better help).
How to create a logfile?
To get an even better insight into your issue, a logfile can help us a lot. On Android this is called "logcat". Short logcats are best. They contain less fluff which makes finding the issue easier. Here are the steps how to create a log with adb:
install adb drivers
open cmd and navigate to the adb file eg. cd C:\Users\<user>\Desktop\platform-tools
Connect your phone via USB
Select "Allow USB Debugging" on the popup on the phone (see below how to activate it)
Clear the log using: adb logcat -c
Start loggingwith: adb logcat | tee beyond.log
Reproduce the issue
Stop logging by pressing CTRL+c
Send us the log (in a PM)
How do I enable USB Debugging?
To enable USB Debugging you need to do the following steps:
Go to Settings -> About Phone
Look for Build number
Tap on Build Number several times till you get the message that Developer Options have been enabled
Go to Settings -> System -> Advanced -> Developer Options
Enable USB Debugging
About this FAQ:
This FAQ is originally written by modpunk and partly maintained by me (ctrej) to reduce modpunk's workload. We try to keep the FAQ as up-to-date as possible, but it may lag a few days behind. Please read the last posts in this thread for latest information.
Changelog:
20200813 (v1.0)
update: this changelog, now with ROM version at time of posting and a hide section for older changelogs
update: firmware update section (thanks @Stef4n82!)
update: ROM update section
update: getting help section, rewritten for clarity
update: proximity sensor, slow sample rate (thanks @Lav64)
update: audio section with my test and @El Dun's report
add: gpay/safetynet explanation
change: link formating to stay under the 30k character limit
20200809 (RC2)
update: audio output with limited frequency range, limited DAC support (thanks @El Dun)
update: double tap to wake works well, used it for a few weeks now without issues
update: "86400 seconds" section (thanks @Exilion90)
add: links to each version of this FAQ, just click one of the datecodes
add: ACCA to feature list
add: ADO works kinda
add: dual sim to feature list (thanks @Exilion90)
20200802 (RC2)
update: microG section (thanks @ichmyselfandi)
update: unlock instructions, setup with wifi required (thanks @Lunat1c)
update: "86400 seconds" section (thanks @Lunat1c & @Stef4n82)
add: gapps/ microg/ google framework requirement for the GCAM (thanks @KanyT & @ned14)
add: bug google backup pattern with 4x4 or 5x5 pattern (thanks @Ivo_Todorov)
fix: twrp "more details" link (thanks @Lunat1c)
20200719 (RC2)
update: rgb light sensor, all channels working
update: software sensors don't output values on stock either (thanks @Brembo109)
add: gcam information (thanks @ned14)
add: grip sensor
add: microg appendum (thanks @ned14)
add: workaround for black status bar in fullscreen
add: bug no glove mode (thanks @raggatip)
add: bug bixby button hold shortcut (thanks @Lav64)
20200713
update: feature/ bug list (previously called working/ not working) with fixed from RC2
update: instructions for microG (thanks @ned14)
update: magisk install instructions
update: wireless power share works fine, the phone just didn't like the synthetic load I used for testing
add: black bar on camera cutout in fullscreen apps (thanks @Sradgads)
20200707 (RC1)
update: section "get help" with copy & paste template
update: font for cmd to Courier New
confirm: removing pin/password/pattern solves the 86400 second wait delay (thanks @fishnetfancy)
add: working/not working section
add: this changelog
add: telephoto lens not working (thanks @Ned)
add: several RC1 issues (thanks @angela5246)
add: vbmeta_disabled note to firmware instructions (thanks @okloloi)
add: reminder to update Magisk alongside lineage (thanks @fishnetfancy)
20200705 (Beta3)
first FAQ update by me (ctrej)
change: order to the "natural" installation flow
change: install section into a more detailed checklist (thanks @AndrOdin)
add: sub-sections (install/ 3rd party/ support)

What is difference between this and Ivan's lineage os?

BratoMo225 said:
What is difference between this and Ivan's lineage os?
Click to expand...
Click to collapse
The most obvious one is that we provide SELinux enforcing and care about security and privacy. For the rest I can't give you an answer as Ivan doesn't want to release the source of his device tree. It would be great if Ivan would join our effort and contribute.

Great news, thanks a lot. Your work is much appreciated.
I run LOS from 31.03. from Ivan now. Can I easily flash yours now? As I see Ivan includes vendor files in his release. Is this something I need to consider before flashing your version? And last but not least - I would like to build from your sources. Mainly because I dont want to have Aurora and Fdroid included. Is there a recipe ready for building from scratch?
Again, thank you very much for your effort.

angela5246 said:
Great news, thanks a lot. Your work is much appreciated.
I run LOS from 31.03. from Ivan now. Can I easily flash yours now? As I see Ivan includes vendor files in his release. Is this something I need to consider before flashing your version? And last but not least - I would like to build from your sources. Mainly because I dont want to have Aurora and Fdroid included. Is there a recipe ready for building from scratch?
Again, thank you very much for your effort.
Click to expand...
Click to collapse
If you switch, you have to format /data I'm sorry. We decided to go with AES-256-XTS encryption for this ROM and also the code is signed with my developer keys! There are package signature checks in place for apps which would prevent you to use the ROM.
If you want to build it yourself, instructions are in the beyond0lte README.
However you can just go to Settings -> Apps and disable FDroid and AuroraStore.
Also I've added and AOD (Always On Display) Quicksetting Tile, but this hasn't been merged upstream yet. You might want to pick those changes.

I cant flash it. Im using latest twrp 103

BratoMo225 said:
I cant flash it. Im using latest twrp 103
Click to expand...
Click to collapse
Which TWRP are you using? Do you use the one we built?

No. The one i downloaded from ianmcd thread.
---------- Post added at 09:26 AM ---------- Previous post was at 09:06 AM ----------
Well now after flashing your twrp, and restarting into recovery mode, my phone wont turn on. It says Could not do normal boot invalid kernel length. When i connect my phone to pc, it just loop restarts. now what

can i flash magisk via twrp or are there any extra steps i need to do before it will work?

BratoMo225 said:
No. The one i downloaded from ianmcd thread.
---------- Post added at 09:26 AM ---------- Previous post was at 09:06 AM ----------
Well now after flashing your twrp, and restarting into recovery mode, my phone wont turn on. It says Could not do normal boot invalid kernel length. When i connect my phone to pc, it just loop restarts. now what
Click to expand...
Click to collapse
Did you also flash a vbmeta image which disables vbmeta checking?

catormeme said:
can i flash magisk via twrp or are there any extra steps i need to do before it will work?
Click to expand...
Click to collapse
I'll upload a boot.img which is pre-patched for Magisk 20.4. You can flash this via twrp and Magisk should work, just need to install the Magisk Manager.
edit: Here it is https://www.androidfilehost.com/?fid=4349826312261761185 Unzip the file. If you wish, you can verify it using gpg, then flash the boot.img via TWRP.

modpunk said:
Did you also flash a vbmeta image which disables vbmeta checking?
Click to expand...
Click to collapse
nope. nothing. I will fix my phone with odin right now and then ill try those steps

BratoMo225 said:
nope. nothing. I will fix my phone with odin right now and then ill try those steps
Click to expand...
Click to collapse
I've flashed twrp + vbmeta-disalbed img, then put the zip and gapps on the sdcard and flashed them, formated data and wiped cache and dalvik.

modpunk said:
I've flashed twrp + vbmeta-disalbed img, then put the zip and gapps on the sdcard and flashed them, formated data and wiped cache and dalvik.
Click to expand...
Click to collapse
Your img is "twrp-3.3.1-0-android-10.0-beyond0lte-3.img.xz" ending at .xz sir. I should rename it and only keep .img at ending ?

BratoMo225 said:
Your img is "twrp-3.3.1-0-android-10.0-beyond0lte-3.img.xz" ending at .xz sir. I should rename it and only keep .img at ending ?
Click to expand...
Click to collapse
You need to unpack it.

What about Live display settings in this build? Does it have different color profiles (sRGB for example as it was on S9 series LOS 15.1/16/17.1) or not? Ivan's ROM has only standard "vivid" gamma and white balance correction....

vomad said:
What about Live display settings in this build? Does it have different color profiles (sRGB for example as it was on S9 series LOS 15.1/16/17.1) or not? Ivan's ROM has only standard "vivid" gamma and white balance correction....
Click to expand...
Click to collapse
Live display is fully working. derf elot fixed the last bit yesterday iirc. The manifest entry was wrong for one part of livedisplay.

modpunk said:
Live display is fully working. derf elot fixed the last bit yesterday iirc. The manifest entry was wrong for one part of livedisplay.
Click to expand...
Click to collapse
"Good news everyone!" So I'll be waiting for the S10/S10+ release and immediatly will flash this rom (and magisk boot image I hope)