[ROM] LineageOS 17/18/19 UNOFFICIAL - (Update: 2023-06-17) - Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,

[ROM] LineageOS 17/18/19 UNOFFICIAL - (Update: 2023-06-17) - Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,

LineageOS 17/18/19 for Sony Xperia XZ1 Compact
{
"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"
}
RELEASE
This is an alternative ROM for the Sony Xperia XZ1 Compact.
Creating this to honor the great work of modpunk and derf elot from https://forum.xda-developers.com/t/rom-lineageos-18-1-unofficial-2-0-update-2021-01-20.4047763/ which seems to be discontinued. Posting an own thread to keep the latest versions visible, I'm NOT claiming authorship over the ROM.
I basically just build the ROM using the latest changes from upstream LineageOS/Google and kernel updates (usually incorporated by derf elot ) See my post.
FEATURES
Signed with dev keys
EAS kernel
Passes SafetyNet out of the box (thanks Rooted_Ansh, Havoc-OS Team and kdrag0n)
Seedvault (Video)
IMS support (thanks to Rooted_Ansh and also Shujath)
17.1 has stock Sony camera (not possible on 18+)
DOWNLOAD
You can download the latest release here.
HINT: Download both the ZIP and md5sum file so TWRP can check the consistency of the upload/download.
Make sure you download the right version, vanilla LineageOS is named lineage-*UNOFFICIAL-lilac.zip while the MicroG version is named lineage-*-MICROG--lilac.zip
REQUIRED FIRMWARE: 47.2.A.11.228
IMPORTANT: I only test the 17.1 releases myself. The 18.1/19.1 are build from mostly the same sources and hopefully work. I only test them roughly.
Backup download
INSTALLATION
IMPORTANT: Magisk seems to cause issues (bootloops) on update, so remove it first and reinstall if required. Note that Magisk is usually not required unless you want root.
Put the zip file of the ROM on your SD card or internal store and boot into recovery.
When coming from stock ROM, do a full wipe (i.e. factory reset) via "Wipe". You don't need to wipe system. When flashing the stock ROM you can select to not keep user data which is equivalent to this step.
Go to "Install", select the zip file and add optionally the gapps zip. Then flash it.
After updates you may now wipe cache&dalvik (option after install)
I suggest to use modpunks TWRP recovery. Again: Don't forget the md5sum file!
TWRP 3.3.1-0 by modpunk / derf elot
Or use the latest TWRP for 17.1/18.1 or TWRP for 19.1.
3.7.0 Seems to work well with latest updates (decryption working) but LineageOS 19.1 (Android 12) requires the ones with "_12" suffix, e.g. 3.6.2_12.
For ease of use I suggest to flash this recovery (only required once):
Boot in Fastboot mode: Hold "Volume Up" while connecting the USB cable to phone and PC
Flash TWRP by running this on the PC: fastboot flash recovery twrp-3.3.1-0-lilac-android10-1.img
(adjust the filename if necessary)
From now you can boot TWRP by turning on the phone with "Volume Down" + Power
I heavily recommend to make a full backup before any installation so you can go back in case of issues. Flashing an older ROM usually helps to recover bootloops etc.
Upgrades between versionsDirty-flashing (e.g. from 17.1 to 18.1) works well but you have to also flash a GApps version matching the Android version or the device will bootloop.
For the upgrade to 19.1 you may need to fully remove OpenGapps by wiping /system and install e.g. MindTheGapps.
SUPPORT
There is NONE. If you have any issues or question ask in the thread so maybe someone else knows the answer.
I'm just providing the ROM (Lineage 17.1 variant) I use myself for others to try to and just build the Lineage 18.1 ROM without much testing.
If you prefer to use a more well-tested Android 11 ROM, I suggest to look at Havoc-OS.
Contributions to the sources are welcome and likely get integrated into the next release.
Contributors
modpunk, derf elot, Rooted_Ansh, Flamefire, linckandrea
Source Code: https://github.com/Flamefire/android_device_sony_lilac, Original: https://github.com/whatawurst/
If you want to buy me a coffee/beer, I'll appreciate it but it is not necessary.
Also please consider donating to the original authors too or to local charities as requested by @modpunk
Special thanks to landsome for donating a test phone for bug hunting and development.
ROM OS Version: Android 10/11/12
ROM Kernel: Linux 4.4.x
Based On: LineageOS
GApps: None included, except for the MICROG builds. Recommended is OpenGApps for 17/18 and MindTheGapps for 19.

CHANGELOG
2023-06-16
June security patches (backports from 18.1 to 17.1)
Kernel updates (CIP tag -st41)
Fix noise when calling with a headset
Configurable fingerprint sensor when screen is off (Settings->Lockscreen)
2023-05-19
Fix Play Integrity checks --> Google Wallet works
Minor improvements that were missed earlier
May security patches (backports from 18.1 to 17.1)
Kernel updates (CIP tag -st40)
2023-04-30
April security patches (backports from 18.1 to 17.1)
Kernel updates (CIP tag -st39)
2023-03-31
March security patches (backports from 18.1 to 17.1)
Kernel updates (CIP tag -st38)
Fix possible camera issues on 18.1
2023-02-25
February security patches
Kernel updates (e.g. CIP tag -st37, also add some missing patches to 19.1 kernel)
Use newer compiler (Clang 12.0.7) for kernel, possibly improving performance/battery life
Add "Re-apply Modem" setting to XperiaParts to help with connection/modem-crash issues
Clear some space on /system & /vendor partitions by removing files no longer needed
Attempt to fix Android Auto connection (untested)
2023-01-20
January security patches
Kernel updates
MicroG builds added (build date 31st Jan, but same sources)
2022-12-27
December security patches
AGPS fix (using Google servers)
Kernel updates (e.g. Wireguard v1.0.20220627, improved security against stack attacks)
2022-11-15
November security patches
WLAN driver update
Huge APN update
2022-10-13
October security patches
Kernel update
APN for DIGI HU
Option to switch temporarily to 2G on boot
2022-09-29
September security patches
Kernel update
APN update
2022-08-12
August security patches
Kernel update (CIP st20)
2022-07-25/28
July security patches
Kernel update
2022-06-30
June security patches
Kernel update
Backport fix for CVE-2021-39686
Workaround fixing bootloop with recent OpenGapps (20220503 tested)
2022-05-16
May security patches
Fix mic volume issue with wired headsets
Known issue: OpenGapps after 15/2 result in bootloop
2022-05-03
April security patches
Kernel update (CIP st5-tag)
Removed LineageOS updater (unused application here)
Added Sony identification packages (Compatibility for some Sony apps from other sources)
2022-03-20
March security patches
Updated some carrier configs (mostly Indian&Chinese) for IMS (VoLTE...)
Better support for flip covers
Allow disabling battery optimizations for the SMS app
2022-02-20
February security patches
Kernel 4.4.302 (final LTS kernel)
Re-enable VoLTE toggle switch (there were reports of modem crashes when VoLTE is disabled, can't reproduce this, hence added the setting back)
2022-01-23
January security patches
Kernel 4.4.299
Wireguard v1.0.20211208
Enhanced display brightness range
Experimental Ultra-Dim mode
2021-12-19
December security patches
Kernel 4.4.295
QCom driver updates
Fix some permission issues
Reset phone ID to XZ1C
2021-11-29
November security patches
Kernel 4.4.291
Fix IMS on 17.1
Fix/enhance Wifi-Display
Fix some power hints
Update APNs
2021-10-19
October security patches
Kernel 4.4.288
2021-09-18
September security patches
Include some more security patches from AOSP
Clang 11 for LOS 17.1 version (same as 18.1, improved optimizations)
Misc bugfixes backported from Android 11 to Android 10
Kernel 4.4.283
2021-08-11
August security patches
Fix bug with switch 3G->4G in XperiaParts not working on slow boot
Include some more security patches from AOSP
Kernel 4.4.279
2021-07-20
July security patches
Kernel 4.4.275
2021-07-03
June security patches
Update to Linux Kernel 4.4.272
Updated APNs

reserved2

Thank you for keeping this rom up to date for this small but loyal userbase! A miracle come true for me cause I can't build roms on my own.

Thank you so much!! Can anyone report to me if flashing the new 18.1 directly over the previous version of 18.1 works?
I would test myself, but right now I cant afford to need to totally reset my phone if it doesn't work.

Dean F said:
Thank you so much!! Can anyone report to me if flashing the new 18.1 directly over the previous version of 18.1 works?
I would test myself, but right now I cant afford to need to totally reset my phone if it doesn't work.
Click to expand...
Click to collapse
All I can say dirty flashing works well over the latest/previous 17.1 by Flamefire, which in turn works well over the latest modpunk (1.7). So it's worth a try.
More generally, although these ROMs are hardly as well tested as HavocOS, there are satisfied reports over on the original LOS17.1/18.1 thread.

Dean F said:
Thank you so much!! Can anyone report to me if flashing the new 18.1 directly over the previous version of 18.1 works?
I would test myself, but right now I cant afford to need to totally reset my phone if it doesn't work.
Click to expand...
Click to collapse
Dirty flash from 17.1 to 18.1 and all work fine!

rez78 said:
Dirty flash from 17.1 to 18.1 and all work fine!
Click to expand...
Click to collapse
Exactly. Just not the other way around.

Updated with the July security patches.
Note: AndroidFileHost was quite quirky today, so use the md5sum files to verify the integrity of the files

Dirty flash. Work perfect!

Flamefire said:
Updated with the July security patches.
Note: AndroidFileHost was quite quirky today, so use the md5sum files to verify the integrity of the files
Click to expand...
Click to collapse
Thanks. Tried it for a couple of hours - dirty flashed over the 0702 version - and it works just as well so far.
I had one brief moment of panic: upon first boot the phone was stuck right on hitting the desktop for some 10 seconds (did not happen on the many previous dirty flashes); but then everything proceeded well.
Again, great work.

@Flamefire Regarding the information to TWRP: There is an official TWRP version (maintained by @modpunk & @derf elot ): https://twrp.me/sony/sonyxperiaxz1compact.html
Maybe you can update the information in your header.

banana(x) said:
@Flamefire Regarding the information to TWRP: There is an official TWRP version (maintained by @modpunk & @derf elot ): https://twrp.me/sony/sonyxperiaxz1compact.html
Maybe you can update the information in your header.
Click to expand...
Click to collapse
Your suggestion would be valuable if you share your experience:
- encrypted partition mount and decryption compatibility with LineageOS 17.1/18.1
- partition backup / restore - single / batch - with / without password protection
- other version differential bug report

Im running 18.1 ROM now and its working great. It works so much better than the previous January release, because the network connects properly now after restarting. There is no need to fiddle in the settings to switch to 3G, then switch back to 4G.
I really like it.

Ok, I was bored and I made a mess, I could use some help.
I was on the latest and last 17.1 by modpunk. I updated TWRP to the latest official one. I tried to flash the latest 18.1 by Flamefire (I had to disable zip signature verification. I know ). Upon reboot it spends about a minute on the LOS animated logo then reboots to TWRP. I then downgraded TWRP to the latest by modpunk and flashed his latest 18.1 from January. This bootloops to recovery without ever reaching the LOS logo.
I know this is my fault. This said, what's my best chance (if any) not to have to wipe everything? I read in a post above that downgrading from 18.1 to 17.1 won't work, otherwise that would be my next idea.
Thanks in advance to anyone replying!
EDIT: Silly me. I had just forgotten to flash 11.0 gApps. All is well with the dirtiest flash ever.

It was not possible to boot LOS 17.1 with TWRP version from first post. (fresh flash, etc... ) However when using latest official twrp https://twrp.me/sony/sonyxperiaxz1compact.html everything works well.

OUTSTANDING!
Thanks for bringing life to this amazing work, you are the best!
Much appreciated.

@Flamefire
Im confused so u continue with updating the security patches every month correct ?
Im confused about the 18.1 u also only update it with securitypatches or also other stuf like making stable and fixing problems orwhatnot ?
Thank you for keeping our trusty xz1 compact alive a little longer.

megaice said:
It was not possible to boot LOS 17.1 with TWRP version from first post. (fresh flash, etc... ) However when using latest official twrp https://twrp.me/sony/sonyxperiaxz1compact.html everything works well.
Click to expand...
Click to collapse
Does it respond to volume up button presses and in special system restart recovery mode? Prompts for a pin/pattern during login and successfully mount and decrypt the partition? So far no one else has reported using it and so far we knew 17.1 / 18.1 requires a different version. Your experience will help us a lot please share as much experience as possible about the new twrp.

7alvoo said:
Does it respond to volume up button presses and in special system restart recovery mode? Prompts for a pin/pattern during login and successfully mount and decrypt the partition? So far no one else has reported using it and so far we knew 17.1 / 18.1 requires a different version. Your experience will help us a lot please share as much experience as possible about the new twrp.
Click to expand...
Click to collapse
i forgot to mention - i'm using lineage-17.1-20210702-UNOFFICIAL-lilac.zip build (not the latest ..20210720..)
TWRP version 3.5.2_9.0
Magisk 20.4 -> 23
Entering recovery works well, pwr+vol down, vol up after pwr, or when set in Developer submenu - advanced reboot. I have active pin and fingerprint. When entering recovery, twrp asks for password for user 0, using my pin works and twrp decrypts FBE. i can mount and read user data by File Manager in twrp.

Related

[DEV][ROM][UNOFFICIAL] LineageOS 14.1 (Android 7.1.2) for Raspberry Pi 3 B

Here’s my build of LineageOS 14.1 for Raspberry Pi 3 Model B. It is unofficial and unsupported by the LineageOS team. It’s for advanced users only.
{
"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"
}
https://konstakang.com/devices/rpi3/CM14.1/
lineage-14.1-20180817-UNOFFICIAL-KonstaKANG-rpi3.zip
https://www.androidfilehost.com/?fid=1322778262903982504
md5:affa35dd70b51e4b70c9acb996f7304b
Sources:
lineage-rpi
Thanks:
peyo-hd and everyone who’s contributed to android-rpi
LineageOS team & everyone who’s been working on CM14.1

How to install:
Follow the official Raspberry Pi instructions for writing the image to the SD card (Linux, Mac, Windows).
FAQ:
Q: I can’t find developer options, why?
A: Settings -> About phone -> Click ‘Build number’ several times
Q: I don’t have reboot options in power menu, why?
A: Settings -> Developer options -> Advanced restart
Q: I have no root, why? What is that hashtag on my status bar?
A: You need enable root access under Settings -> Developer options -> Root access. Root management is now integrated as part of LineageOS’ Privacy Guard and you can manage per app permissions under Settings -> Developer options -> Manage root access. You’ll have a persistent notification in the status bar when you’re running an app that uses root permissions.
Q: I have official 7” LCD display and touchscreen. What should I do?
A: Execute following commands in ‘adb shell’/serial console/terminal (you can enable built-in terminal app from Settings -> Developer options -> Local terminal) and reboot your device:
Code:
su
rpi3-display.sh
Q: Settings -> Storage shows xx GB used by system. There’s unallocated space on my sdcard. What should I do?
A: This is a 4 GB image, remaining space on your sdcard will remain unallocated. Settings app shows unallocated space as used by system which in reality it is not. You can use e.g. GParted and extend /data partition (/dev/block/mmcblk0p3) to cover the unallocated space. Resizing the partition manually will break support for encrypting /data. Format /data in TWRP recovery (Wipe->Format data) after resizing to leave required space for crypto footer.
Q: Raspberry Pi doesn’t have power button, how do I power off/reboot my device?
A: Following keyboard keys work as Android buttons: F1 = Home, F2 = Back, F3 = Multi-tasking, F4 = Menu, F5 = Power, F11 = Volume down, and F12 = Volume up. You can also use one of many third party reboot applications.
Q: How to boot to TWRP recovery?
A: There’s currently no proper way to boot between Android and TWRP, but this can achieved by renaming the ramdisk you want to boot. Execute following commands in ‘adb shell’/serial console/terminal (you can enable built-in terminal app from Settings -> Developer options -> Local terminal) and reboot your device:
Code:
su
rpi3-recovery.sh
If mouse cursor doesn’t appear, try replugging your mouse.
Q: How to boot out of TWRP recovery?
A: Flash my recovery2boot zip in TWRP.
Q: How to install Google apps?
Download open_gapps-arm-7.1-pico-xxxxxxxx.zip and save it to your device’s internal storage or use an external USB drive
Boot to TWRP recovery (see FAQ)
Install open_gapps-arm-7.1-pico-xxxxxxxx.zip from your selected storage
Wipe->Factory reset!
Boot out of recovery (see FAQ)

Merged commits not mentioned in the changelog.
17.8. changelog:
include TWRP 3.2.3-0 custom recovery (see FAQ how to boot)
fix Gallery app crashing (and likely various third party apps as well)
add support for encrypting the device
merge AOSP kernel/common android-4.4-n branch to have proper Android Nougat kernel
update to Linux 4.4.148 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 August 2018 (merged)
15.6. changelog:
add support for USB webcams (UVC) with third party USB webcam apps
default to noop I/O scheduler
update to Linux 4.4.137 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 June 2018 (merged)
15.4. changelog:
update audio HAL (fix USB microphone, etc)
add support for external USB GPS dongles (1546:01a7 U-Blox AG, etc - GPS dongle must be plugged-in while booting the device)
update to Linux 4.4.127 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 April 2018 (merged)
18.1. 2018 changelog:
add support for I2C devices
enable Android low-RAM configuration
add lights HAL to control display brightness from Android on offical RPI display (version 1.1)
update to Linux 4.4.112 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 January 2018 (merged)
17.11. changelog:
fix wifi reconnect on boot (thanks to Google)
update to Linux 4.4.97 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
patch recently disclosed BlueBorne and KRACK vulnerabilities (merged)
Android security patch level: 5 October 2017 (merged)
10.8. changelog:
update to Linux 4.4.80 kernel
merge AOSP kernel/common android-4.4 branch to have proper Android kernel
enable sdcardfs
add BFQ i/o scheduler and enable it by default
Jelly browser (merged)
Android security patch level: 5 August 2017 (merged)
16.4. changelog:
add support for wifi tethering
add support for Widevine DRM
improve Play Store compatibility
Android 7.1.2 (merged)
Android security patch level: 5 April 2017 (merged)
11.4. changelog:
initial relase
Previous builds:
AndroidFileHost

I cannot boot out of recovery after installing Gapps in TWRP. When I run rpi3-recovery.sh boot I got Segmentation Fault error. Please help. Thanks

Project999 said:
I cannot boot out of recovery after installing Gapps in TWRP. When I run rpi3-recovery.sh boot I got Segmentation Fault error. Please help. Thanks
Click to expand...
Click to collapse
Please read the FAQ! It doesn't say to run the same script, it says to flash recovery2boot zip in TWRP.
I'm aware of the segfault.

Ok, I was doing both ans will only flash the zip file next try.

Yes. It worked this time after only flashing the recovery2boot zip file. Thank you.

Its possible to update ROM via recovery?

laharl_22 said:
Its possible to update ROM via recovery?
Click to expand...
Click to collapse
No, not currently. Partition structure (especially boot partition) on this device is different than on Android devices usually (well, as Raspberry is not an Android device to begin with). It would require some quite significant modifications to LineageOS build system to build recovery flashable ROM zips for this device (it's all open source so you're welcome to have a crack at it). There's also no proper way to cold boot (from power off) to recovery which makes it less useful than on other devices. I only included TWRP recently and it's currently mostly just used for installing gapps.

KonstaT said:
No, not currently. Partition structure (especially boot partition) on this device is different than on Android devices usually (well, as Raspberry is not an Android device to begin with). It would require some quite significant modifications to LineageOS build system to build recovery flashable ROM zips for this device (it's all open source so you're welcome to have a crack at it). There's also no proper way to cold boot (from power off) to recovery which makes it less useful than on other devices. I only included TWRP recently and it's currently mostly just used for installing gapps.
Click to expand...
Click to collapse
So no way for updating ROM without loose data?

laharl_22 said:
So no way for updating ROM without loose data?
Click to expand...
Click to collapse
No, not currently and who said there was going to be any updates.
Well, you can actually restore your previous /data partition in TWRP after you've installed a new image.

Sorry, double post.

Hi.
Is there a GPIO support? Everything is working great, but I build it into my car, and I have some pushbuttons connected. I would like to use it for opening apps or shutdown etc. Any ideas? couldn't find anything on google? Thanks

ulfdogg said:
Hi.
Is there a GPIO support? Everything is working great, but I build it into my car, and I have some pushbuttons connected. I would like to use it for opening apps or shutdown etc. Any ideas? couldn't find anything on google? Thanks
Click to expand...
Click to collapse
Yes, that should be possible but you need to do a little work for that.
4.4 kernel used in LineageOS 14.1 doesn't have gpio-key overlay (https://github.com/raspberrypi/linux/commit/7bc9c88a0eb043c5387a23d4ade23359749398e0) but I have already enabled KEYBOARD_GPIO that is also needed for this. So you need to build that overlay, copy it to device, and configure it in config.txt depending on what GPIO pins you're using. There's also another similar approach (different overlay) that's been reported working. https://stackoverflow.com/questions/50224010/using-gpio-keys-interrupt-to-wake-up-screen-on-rpi3

Does this build support 3b+?If not,how to ?

zhengyw said:
Does this build support 3b+?If not,how to ?
Click to expand...
Click to collapse
No, you can use LineageOS 15.1 build instead.
This build uses Linux 4.4 kernel and Broadcom added support for 3B+ only on later kernel versions (4.9 and 4.14). 4.4 is actually the newest that Android Nougat supports (https://android.googlesource.com/kernel/common/) and there's some network issues using newer ones. 4.9 is the newest for Oreo and 4.14 for Pie. So the Linux kernel in LineageOS 15.1 is actually too new for the Android version. There's no major changes between Oreo and Pie kernels, though.
Android kernel versions lag behind mainline because chipset manufacturers (Qualcomm, etc) need to make significant modifications to support their hardware. Android devices usually stay with the Linux kernel version they initially shipped with so there also needs to be quite long support time (4.4 is still supported with Pie).

KonstaT said:
No, you can use LineageOS 15.1 build instead.
This build uses Linux 4.4 kernel and Broadcom added support for 3B+ only on later kernel versions (4.9 and 4.14). 4.4 is actually the newest that Android Nougat supports (https://android.googlesource.com/kernel/common/) and there's some network issues using newer ones. 4.9 is the newest for Oreo and 4.14 for Pie. So the Linux kernel in LineageOS 15.1 is actually too new for the Android version. There's no major changes between Oreo and Pie kernels, though.
Android kernel versions lag behind mainline because chipset manufacturers (Qualcomm, etc) need to make significant modifications to support their hardware. Android devices usually stay with the Linux kernel version they initially shipped with so there also needs to be quite long support time (4.4 is still supported with Pie).
Click to expand...
Click to collapse
Thank you..So I have to wait till los 15.1 go stable

Hi, thanks for this build, I might have done something wrong as I can't past the setup wizard, after security setup it comes back to lineageOS startup screen and the begin button to start again the setup wizard

s1lex said:
Hi, thanks for this build, I might have done something wrong as I can't past the setup wizard, after security setup it comes back to lineageOS startup screen and the begin button to start again the setup wizard
Click to expand...
Click to collapse
I've heard about this but can't reproduce it myself and I haven't seen any logs (logcat). You could try using another faster sdcard. Some people have also removed the SetupWizard apk from the image manually.

Hi there,
Thanks for amazing work!
The only issue I'm experiencing is some flickering in graphic heavy and full screen apps. Am I doing something wrong or it's a known issue?
I just noticed that it's happening more when I use: "dtoverlay=vc4-fkms-v3d,cma-256"
But with dtoverlay=vc4-kms-v3d,cma-256 composite video output is not there. Any solutions?

[ROM] [9.0.0] LineageOS 16.0 [walleye] [unofficial]

Thanks:
 @AlaskaLinuxUser
 @jorgen2009
LineageOS Team

Reserved2

Thank you for your effort. Will there ever be an official release? If not, why do they not release even a 8.1 official?
I find it strange that LineageOS has still official nightly builds for even the very old nexus, but for the pixel2 there is nothing official.

RobertQc said:
Thank you for your effort. Will there ever be an official release? If not, why do they not release even a 8.1 official?
I find it strange that LineageOS has still official nightly builds for even the very old nexus, but for the pixel2 there is nothing official.
Click to expand...
Click to collapse
Thanks for your interest.
There will be an official release if a maintainer submits a request for an unofficial build to become official and gets accepted by LineageOS. Maintainers are people like me, who do this as a hobby, not the LineageOS team. So at some point my builds could become official, if I submit a request for review and my request gets accepted. In order to pass the review, the items on the quality control checklist need to be met. You can read more about the process on the LineageOS Website. This could be a starting point:
https://wiki.lineageos.org/device_requests.html
These are the device support requirements:
https://github.com/LineageOS/charter/blob/master/device-support-requirements.md
If you are interested in getting the Pixel 2 on the list of officially supported devices, then assisting me with the quality assurance is a great way to contribute.. Thus, I am grateful for everyone, who flashes my builds and posts feedback in this thread.

great stuff.
personally i dont understand why people want official builds of roms, unofficial are just as good as official. they may not pass the official standards or requirements but as long as everything is working it should not be a problem.
official is just a stamp these days, people need to understand that. the code base is same for official or unofficial. Plus, official means a responsibility on people who do it for fun and for free.
heck even devices with official los members working on them (moto x4, poco f1) dont have official los builds.

Does this come with gapps? If so, would it be possible to get a build without? Also thanks for the release!

Shmi117 said:
Does this come with gapps? If so, would it be possible to get a build without? Also thanks for the release!
Click to expand...
Click to collapse
This build is without gapps.

leqacy said:
The ROM has been stable for me for the short time I've been running it. However, if you encounter any instabilities or bugs, please post in this thread.
Click to expand...
Click to collapse
Well done! Great work! :highfive:

I'll keep looking for any bugs
Substratum and Bluetooth working!
The only problem I have had is with data transfer tool.

Any possibility that you could please compile 15.1 as well? Xposed isn't supported on Pie, and there's a PNG vulnerability looming around.

Lineage OS 15.1
YandereSan said:
Any possibility that you could please compile 15.1 as well? Xposed isn't supported on Pie, and there's a PNG vulnerability looming around.
Click to expand...
Click to collapse
Here is an unofficial build of lineage OS 15.1 for walleye. (Not by this compiler). If they decide not to support 15.1 then this build is relatively stable.
https://forum.xda-developers.com/pixel-2/development/rom-lineageos-15-1-t3781015

YandereSan said:
Any possibility that you could please compile 15.1 as well? Xposed isn't supported on Pie, and there's a PNG vulnerability looming around.
Click to expand...
Click to collapse
Regarding PNG vulnerabilities: These vulnerabilities exist(ed) in both LineageOS 16 and 15.1. They were patched with the February 2019 security patch. This patch is contained in my build, which is linked in the first post.
You can check for the patch level in Settings->About phone->Android version. The current status in my build is: February 5, 2019. The link directs you to the list of monthly updates. If you select February 2019 in the list, you will see the 3 PNG vulnerabilities you are referring to are already patched.
Framework
The most severe vulnerability in this section could enable a remote attacker using a specially crafted PNG file to execute arbitrary code within the context of a privileged process.
CVE References Type Severity Updated AOSP versions
CVE-2019-1986 A-117838472 [2] RCE Critical 9
CVE-2019-1987 A-118143775 [2] RCE Critical 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9
CVE-2019-1988 A-118372692 RCE Critical 8.0, 8.1, 9
Click to expand...
Click to collapse
I hope that addresses your security concern with the LineageOS 16.0 build.
Adamzapple_ said:
Substratum and Bluetooth working!
The only problem I have had is with data transfer tool.
Click to expand...
Click to collapse
Thank you for testing. I just tested with the data transfer tool on macOS. I was able to transfer files to and from the device without any problems, after setting USB Preferences to "File Transfer".
What problems were you having exactly and on which OS?
I'll address other points in later posts.

leqacy said:
Thank you for testing. I just tested with the data transfer tool on macOS. I was able to transfer files to and from the device without any problems, after setting USB Preferences to "File Transfer".
What problems were you having exactly and on which OS?
I'll address other points in later posts.
Click to expand...
Click to collapse
The transfer tool refused to respond. However I just tried it again and it worked just fine. Don't know what was happening yesterday but it refused to work at all. If I have the problem again I will provide a logcat.

First of all i'd like to thank you for your efforts in building this ROM and sharing your work with the community! It's really cool to have recent updates of LineageOS for the Pixel 2.
You have picked up the great work from Jorgen2009 as it seems but unlike the original thread you do not provide any details on wether if and how this ROM is dependend on a specific(?) version of the vendor partition. I assume that one has to flash Google Factory Image from february in order to use this ROM?
Furtheremore i'd like to know about what Jorgen2009 has called "the Pixel specific bits for unlimited photo upload for instance". Unsure what this means in technical detail but it's definatly something i would want to preseve when moving to this ROM. For example, the ability to install original Google Camera from PlayStore and use all of its Pixel related features seems somewhat tricky to achive. Is this solely related to GApps or is there some relation to the ROM itself? And if so, is that included here?
Last but not least about GApps itself. As i have understood from the former maintainer getting them work with this ROM was also some kind of a challenge. I'm going to install MindTheGApps on top of this so any hints are highly appreciated.
I guess i'll create some backups now and then just give it a try to migrate my device from Jorgen2009's november release to this ROM.

Wow, that was easy! I've successfully migrated my existing installation (almost) without loosing any data.
So here's what i did:
1. Install february factory image walleye-pq2a.190205.002-factory-781881b5.zip without wiping data
2. Boot into twrp 3.2.2-1 via fastboot
3. Flash lineage-16.0-20190210-UNOFFICIAL-walleye.zip without wiping cache nor data
4. Flash twrp-pixel2-installer-walleye-3.2.3-1.zip
5. Flash Magisk-v18.1.zip
6. Flash MindTheGapps-9.0.0-arm64-20190122_071653.zip (official MindTheGapps-9.0.0-arm64-20190203_191233.zip did not work for me probably because of this)
7. Reboot
Only a few Google apps kept force closing such as Maps, Google Camera and YouTube (i dont use any other Google Apps) but PlayStore worked right away so i simply reinstalled them. :victory:

YandereSan said:
Any possibility that you could please compile 15.1 as well?
Click to expand...
Click to collapse
At the moment my focus is on 16.0. If there is more demand for 15.1 I may consider running a build.
bleh815 said:
First of all i'd like to thank you for your efforts in building this ROM and sharing your work with the community! It's really cool to have recent updates of LineageOS for the Pixel 2.
You have picked up the great work from Jorgen2009 as it seems but unlike the original thread you do not provide any details on wether if and how this ROM is dependend on a specific(?) version of the vendor partition. I assume that one has to flash Google Factory Image from february in order to use this ROM?
Click to expand...
Click to collapse
Thank you for your feedback! This is an important point and I edited the installation instructions to include this. I had February 2019 stock installed before flashing my LineageOS build, so I did not encounter any problems with regards to the vendor image, but if you have an older vendor image on your phone you may have problems, since there were some API changes lately.
bleh815 said:
Furtheremore i'd like to know about what Jorgen2009 has called "the Pixel specific bits for unlimited photo upload for instance". Unsure what this means in technical detail but it's definatly something i would want to preseve when moving to this ROM. For example, the ability to install original Google Camera from PlayStore and use all of its Pixel related features seems somewhat tricky to achive. Is this solely related to GApps or is there some relation to the ROM itself? And if so, is that included here?
Click to expand...
Click to collapse
So far my build does not contain the modifications from jorgen2009. I started my build on a clean plate, so in terms of modifications my build does not have a lot in common with jorgen, the LineageOS and device tree is in common, of course. My build does not contain Pixel specific modifications at the moment.
bleh815 said:
Last but not least about GApps itself. As i have understood from the former maintainer getting them work with this ROM was also some kind of a challenge. I'm going to install MindTheGApps on top of this so any hints are highly appreciated.
Click to expand...
Click to collapse
I went down the microG path and got GmsCore working.

Does this contain the squeeze for assistant functionality?
I doubt it but honestly, this is the one feature that's keeping me from switching to a custom rom
Additionally what else would I lose in terms of base features or is it everything?
(Sorry I have a decent amount of experience with Lineage and Custom Roms but this is the first time I have ever been able to get a phone with an unlocked bootloader)

OrangeFlare said:
Does this contain the squeeze for assistant functionality?
I doubt it but honestly, this is the one feature that's keeping me from switching to a custom rom
Additionally what else would I lose in terms of base features or is it everything?
(Sorry I have a decent amount of experience with Lineage and Custom Roms but this is the first time I have ever been able to get a phone with an unlocked bootloader)
Click to expand...
Click to collapse
No custom ROMS support the squeeze feature. I agree with you, I can't give it up. It's too handy! :highfive:

nolimit78 said:
No custom ROMS support the squeeze feature. I agree with you, I can't give it up. It's too handy! :highfive:
Click to expand...
Click to collapse
https://www.xda-developers.com/google-pixel-active-edge-squeeze-feature-custom-roms/
:fingers-crossed:
I may start messing around with this and see if I can get a build of LineageOS 16.0 to work with this

[ROM][13.0][Daredevil] LineageOS 20.0 [UNOFFICIAL]

Note - please take your data backup and do clean flash as per the instructions linked in the main thread. On top of it, my builds will boot on any stock firmware as base. So there is no special recommendation towards which stock rom you need to be on.
Changelog - Sun Jan 22 19:01:23 UTC 2023
============================
• Initial Android 13 build
• Based on android-13.0.0_r20
• Improved system stability
• User interface enhancements
• Google security patch 2023-01
• Selinux enforced
• Vendor built from Source
• Imported CTS profile patches
• Safety net pass by default & no need zygisk
• Updated build fingerprint from Pixel 7 Pro (cheetah)
Reminder - for reporting bugs please mention the issue and attach the logcat.
Thank you!

Awesome..!

Any chance it would run on Nokia 8.1 after unlocking/rooting with Hikari files ?
I'm mean ... someday / when updates are over .

Changelog Sat Apr 3 08:41:31 UTC 2020
===================================
1. Initial stable build
2. March security patch
3. Comes with stock kernel
4. Linux version 4.4.194
5. Vendor image from 2250
6. System blobs from 2250
7. Ota support available
Note- Installation process changed so please go ahead and follow the instructions as I mentioned in installation section

I tested now and I found Google Services - are GApps included? I installed lineageos in this build to AVOID this. Or did I make something wrong?

overclockA said:
I tested now and I found Google Services - are GApps included? I installed lineageos in this build to AVOID this. Or did I make something wrong?
Click to expand...
Click to collapse
Thanks, saved me some time. Defeats the entire purpose for me.

xe500linux said:
Thanks, saved me some time. Defeats the entire purpose for me.
Click to expand...
Click to collapse
I wrote to Raghu varma for the same question.
Technically it seems to not be that simple - if lineage 17.1 has been compiled without gapps and the build process was done by using private keys, flashing gapps would brick the device or the lineageos installation.
So Raghu varma compiled the version with gapps included to avoid this.
So I took his scripts from github and I built lineageos 17.1 on my own (with private keys and without gapps as I don't think about flashing them afterwards) - this worked fine.
Now I couldn't find his scripts for Daredevil on his github profile anymore - maybe they will come back for the 7.2 build process.

overclockA said:
I wrote to Raghu varma for the same question.
Technically it seems to not be that simple - if lineage 17.1 has been compiled without gapps and the build process was done by using private keys, flashing gapps would brick the device or the lineageos installation.
So Raghu varma compiled the version with gapps included to avoid this.
So I took his scripts from github and I built lineageos 17.1 on my own (with private keys and without gapps as I don't think about flashing them afterwards) - this worked fine.
Now I couldn't find his scripts for Daredevil on his github profile anymore - maybe they will come back for the 7.2 build process.
Click to expand...
Click to collapse
Ah I see. Any chance you still have a copy of your non-g build?

xe500linux said:
Ah I see. Any chance you still have a copy of your non-g build?
Click to expand...
Click to collapse
This should be OK. I'll upload a copy and send a link.
Be aware that the security patch level is dated on march 2020 and doesn't include the latest Google security patches from june.

overclockA said:
This should be OK. I'll upload a copy and send a link.
Be aware that the security patch level is dated on march 2020 and doesn't include the latest Google security patches from june.
Click to expand...
Click to collapse
Much appreciated!!

i posted already in the twrp thread of my problem "touch not working with twrp", that's still persisting.
so i got another idea. i used adb commands to control twrp. like you know, adb shell twrp sideload and then do the adb sideload commands for installing lineageos 17.1.
what did i do so far is:
*flash twrp 3.4.0
*boot up to twrp 3.4.0
*use adb shell twrp remountrw
*use adb to sideload lineageos 17.1 zipfile with commands (adb shell twrp sideload and then adb sideload lineageos.zip) - but the progress bar only goes to 47% and say like it would have "finished" - i dont believe in it
*use adb to sideload vendor zipfile zipfile with commands (adb shell twrp sideload and then adb sideload vendor.zip) - that one works normally
*changed slot from B (i was on before) to A on fastboot and flashed the vbmeta to current slot (A)
*reboot without wiping system partition and installing lineageos only brings up normal stock rom
*even wiped system partition one time (or should i say system_root?) - and installed lineageOS via adb sideload. but nothing was in the system_root folder as i mounted it back again
*wiping system partition and reboot only brings up android one loading screen endlessly
so basically, the installer says it has installed the rom, but in reality it didnt seem to touch the system partition at all. am i doing something wrong or may it be that because i dont have touch access i miss to move some unlock slider which is not implemented via adb shell twrp? i think something along these lines might be the case but.. i was able to adb shell twrp wipe system. so basically it should not be a big deal to write to system partition or system_root in general.
oh and of accusation that the adb sideload probably doesnt send data correctly (from which i heard lots of stories of the past), i even pushed the zip file via adb push to / and installed it with adb shell twrp install /lineageos.zip. same result.
what i would really like to see is an debug log of the installer zip. you only see "part 1 and part 2" installing and percentage, but no informations what the installer is doing currently. this would help a lot if there would be a switch for the installer like "verbose information"
edit again.
I finally managed to do the install. You know what? it is possible without the touch gui. what i did was:
*reflashed via fastboot the stock rom
*booted normally, installed the latest upgrade (Stock ROM OTA - took a long while) - (may be obsolete)
*booted to fastboot, flashed newest twrp to boot
*booted to recovery
*adb shell twrp remountrw
*adb shell twrp remountrw (the /tmp/recovery.log showed interestingly at first remountrw the page set of readonly, at second time not - why?)
*adb shell
*entered in adb shell mount /system
*adb shell twrp wipe data
*adb push lineageos.zip /data/
*adb shell twrp install /data/lineageos.zip
*adb push ddv.zip /data/
*adb shell twrp install /data/ddv.zip
*adb shell getprop ro.boot.slot_suffix (to get the actual boot slot)
*adb reboot bootloader
*fastboot --set-active=_a (for me i was on b before, so i needed to go to a)
*fastboot flash vbmeta_a --disable-verity --disable-verification vbmeta.img
*fastboot reboot
*then the phone - now on lineage - asked me to factory reset, i did
*booted finally successfully up to lineage 17.1 - wlan, mobile network working just fine
if you want gapps on it, install them ideally direct after your custom rom is able to boot. in my case gps didnt worked with gapps and other apps till i did another factory reset. and the original launcher that comes with the cust-rom doesnt work anymore after installing the gapps. use the pixel launcher instead. after that, it works like a charme
in conclusion: a bit odd how the install not works as in the description was told. maybe the TA-1196 is just a bit different.

Hello Together,
i've installed LineageOs yesterday and i realy like it . I just can't find an camera App that supports the wideAngle Camera at the back.
Open Camera only recognizes 2 Cameras, and GCam 7.0 Nokia 7.2 Mod can't seem to access it either.
Is there a solution to this?
Best regards
Alex

Changelog Fri Nov 13 23:24:47 IST 2020
==============================
- based on latest lineage sources
- November 2020 security patch
- fixed bluetooth audio
- fixed mic
- fixed RIL
- fixed headset
- based on android 10 prebuilt vendor for now ( DDV2.340 )
- Comes with stock kernel
- linux version 4.4.192
- compiled using gcc
- fixed battery drain
- fixed styles and wallpapers
- selinux enforced
- banking apps working
- use NikGapps

Got brand new nokia 7.2 yesterday, developer loaded old android build 1_130 and unlocked bootloader, didnt recommend twrp as this wol break wi-fi. Can I flash this OS on my phone directly without twrp ? will wifi and camera work as it should? Sorry for the questions I am new here and just started reading this Thank you

Nokia is nowadays very slow in giving security patch updates to its devices. Its a high time we switch to custom rom..?
I'm waiting for my phone's warranty to get over. Anyways, do anyone have any eta on when this rom will get official?

I have managed finally to install it, but sorry, nothing mentioned work: no double tapp sleep or wake up, no fingerprint, no slinux enforced, camera is not worth to mention at all and i still didnt test bluetooth or microphones yet. ..

dariuslapsys said:
I have managed finally to install it, but sorry, nothing mentioned work: no double tapp sleep or wake up, no fingerprint, no slinux enforced, camera is not worth to mention at all and i still didnt test bluetooth or microphones yet. ..
Click to expand...
Click to collapse
I agree for tapp to wake up and selinux.
Nevertheless, bluetooth and microphones and fingerprint sensors are working like a charm.
NFC is not mentioned anywhere, but I don't need this function at all.
I installed the build from 14/11.
@Raghu varma: Can we help you out sending logfiles for some issues? Do you need testers?

Raghu varma said:
Note - Iam Not Responsible for bricked devices
About LineageOS
LineageOS is a free and open-source operating system for set-top boxes, smartphones and tablet computers, based on the Android mobile platform. It is the successor to the custom ROM CyanogenMod, from which it was forked in December 2016 when Cyanogen Inc. announced it was discontinuing development and shut down the infrastructure behind the project. Since Cyanogen Inc. retained the rights to the Cyanogen name, the project rebranded its fork as LineageOS.
LineageOS was officially launched on December 24, 2016, with the source code available on GitHub. Since that time, LineageOS development builds now cover more than 185 phone models with over 1.9 million active installs,having doubled its user base in the month February–March 2017 And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Installation procedure
Note - I don't recommend you people to flash any other custom kernels on this ROM untill Nokia release kernel sources. Because this ROM supports only stock kernel .
1. Download Rom.zip , twrp.img & vbmeta.img
2. power off your phone boot in to bootloader mode and flash twrp
3. Boot in to Twrp
4. Format data by typing yes
5. Wipe everything
6. Flash rom.zip & vendor.zip
7. Now tap on reboot and check your current active slot.
Example - if twrp shows current active slot A change to B if B change to A
8. Tap on reboot and tap on bootloader ( this will reboots your phone to bootloder mode )
9. Now open cmd in pc flash vbmeta using this command
for slot-a > fastboot flash vbmeta_a --disable-verity --disable-verification vbmeta.img
for slot-b> fastboot flash vbmeta_b --disable-verity --disable-verification vbmeta.img
( thanks to @singhnsk for this step )
10. now type fastboot reboot
and wait for 3 min rom will boot up
Credits
* LineageOS & CO (For Source Code)
* All the authors in my git sources
* Nokia For Prebuilt Vendor & Kernel Source
* Moderators (For Giving Freedom To Post Threads)
* My entire Nokia 7.2 community Thank you all for your massive support Again
Join Nokia 7.2 Community

Download Rom
Download Vendor
Download vbmeta
Download GApps
Download Official Twrp
Android OS version: 11.0.0_r17
Security patch level: November 2020
Build author: Raghu varma
My build script: https://github.com/RaghuVarma331/scripts
Kernel Source code: https://github.com/RaghuVarma331/android_kernel_nokia_sdm660
Source code: https://github.com/LineageOS
Click to expand...
Click to collapse
When i install this rom volte function not proper working outgoing not work incoming volte works reply what is this

When i install this rom volte function not proper working outgoing not work incoming volte works reply what is this

[ROM][dragon][UNOFFICIAL][crDroidAndroid-13.0][v9.4]

RESERVED

The last crDroid build for the next time ..
It's based on Lineage-17.1 - we use the same device/kernel/vendor sources for dragon.
Including March security updates and DragonParts app for WiFi country code.
Moved to androidfilehost.com now ..
crDroidAndroid-10.0-20200308-dragon-v6.4.zip
There will be no regular updates .. just some builds from time to time !
Cheers

followmsi said:
The last crDroid build for the next time ..
Click to expand...
Click to collapse
First of all, thank you so much for all your work man, I just saw that you not only maintain official LOS for dragon and this crDroid port but also commit to official TWRP. I don't know how you do all this, but I admire and applaud it.
Two quick questions:
1. GApps are optional, right?
2. Do I flash Magisk after first boot (as described in OP under "Pre-Installation") or right after ROM (as described in OP under "First time installation")?
Edit:
Ok, I just couldn't wait and flashed it. To answer my own questions:
GApps are indeed optional and I flashed Magisk only after booting crDroid for the first time.
@ followmsi
So far I encountered the following problems:
1. A lot of artifacts/flickering/flashing of the UI, looks like refreshes/repaints that get stuck half-way. Sometimes it is impossible to e.g. use the keyboard because of this. If you want I can provide photos, but it should be pretty easy and obvious to reproduce this unless there is something seriously wrong with my installation.
2. Booting into crDroid only works every other time or so, it often freezes on the large Google logo screen. Holding the power button until it shuts off mostly fixes the problem and it boots successfully on the next try, but sometimes even a third try is needed.
Apart from these problems, first impression is very good. Nice to see Android 10 with lots of customization on the good old dragon
Thanks again and let me know if I can be of assistance.

One more build ..
crDroidAndroid-10.0-20200424-dragon-v6.5.zip
Changes:
- Google security updates -> April 2020 (android-10.0.0_r33)
- Turned off SoftAP MAC randomization
- Reverted Kernel MAC address hack -> to prevent boot problems.
- Changed kernel config for USB tethering
- Kernel: Added "fix cpu frequency limitation"
- Latest crDroid changes for Android 10
Enjoy

When using Colour calibration in LiveDisplay, the screen will flicker abnormally

followmsi said:
One more build ..
crDroidAndroid-10.0-20200424-dragon-v6.5.zip
Changes:
- Google security updates -> April 2020 (android-10.0.0_r33)
- Turned off SoftAP MAC randomization
- Reverted Kernel MAC address hack -> to prevent boot problems.
- Changed kernel config for USB tethering
- Kernel: Added "fix cpu frequency limitation"
- Latest crDroid changes for Android 10
Enjoy
Click to expand...
Click to collapse
I've been using this since your first test build. One of the better roms out there.
Considering your lack of time with your busy schedule, I really appreciate it!
Thanks! ??

122877087 said:
When using Colour calibration in LiveDisplay, the screen will flicker abnormally
Click to expand...
Click to collapse
Works normally for me.

A few months later ..
crDroidAndroid-10.0-20200811-dragon-v6.9.zip
Changes:
- Google security updates -> August 2020 (android-10.0.0_r41)
- Latest device and kernel changes for dragon.
- Latest crDroid changes for Android 10
Enjoy

followmsi said:
A few months later ..
crDroidAndroid-10.0-20200811-dragon-v6.9.zip
Changes:
- Google security updates -> August 2020 (android-10.0.0_r41)
- Latest device and kernel changes for dragon.
- Latest crDroid changes for Android 10
Enjoy
Click to expand...
Click to collapse
I know you're quite busy and I expect nothing, so I really appreciate this!
Thank you! ??
Edit: Just an FYi, a dirty flash from CR 6.5 to 6.9 was buggy. Might need a clean flash.
Also, Magisk Canary didn't want to flash. Tried multiple methods. Not a big deal because Magisk betta worked just fine.
Everything is running well,
Thanks!

Let's move to Android 11 ..
crDroidAndroid-11.0-20201219-dragon-v7.1.zip
Changes:
- Initial Android 11 build for dragon device
- Google security updates -> December 2020
- Latest device changes for dragon
- Latest crDroid sources
Enjoy

Awesome, Thanks. Just upgraded from Dirty Unicorns. Flashed with Nik Gapps, no problem except prior mentions in the LOS thread. Thank you a gain and have a great holiday!

First of all, thank you for all your work . I have flashed crDroidAndroid-11.0-20201219-dragon-v7.1.zip and Nik gapps. After the display has switched itself off, it switches on again automatically after 5 seconds and so on. If I turn the display off using the button, it won't turn on again. Do I have any setting that causes this?

It's time for a new build ..
crDroidAndroid-11.0-20210414-dragon-v7.5.zip
Changes:
- Google Security updates -> April 2021
- Latest device and kernel changes for dragon
- Backport of Wifi-Display (Miracast) for Android 11
- Latest crDroid changes for Android 11
Enjoy

Thank you @followmsi for your support of this ROM, as I much prefer it with all it's customization over basic LineageOS. It seems to run much better now than before as well. I think there were some RAM-related issues.
But I have run into a grave problem, as I have accidentally turned off WiFi and now the tablet has become unresponsive, as the UI seems to crash repeatedly. Only the status bar and lock screen symbol pop in and out. I tried to turn on WiFi by booting into TWRP and changing "wifi_on" to 1 in "/data/system/users/0/settings_global.xml" but it didn't work. The tablet runs warm and safe mode doesn't work either btw. Any idea?
Edit: I decided to perform a clean install, since it's been a while anyway and we've skipped a couple versions as well. Anyway, I initially tested to turn WiFi off and it worked fine, no crash. I proceed to set up my device somewhat, enable dark mode, change icon shape, go through all crDroid settings etc.; I turn off WiFi once more, from the quick-settings, and it happened again. I'm not sure what setting or customization exactly leads to this, but I guess I'll have to be very careful not to turn it off for now. If I can help troubleshoot this issue, let me know.
Edit2: I think I figured out what it is: Data usage (daily/monthly) in the quick settings. Gotta keep that turned off.

followmsi said:
It's time for a new build ..
crDroidAndroid-11.0-20210414-dragon-v7.5.zip
Changes:
- Google Security updates -> April 2021
- Latest device and kernel changes for dragon
- Backport of Wifi-Display (Miracast) for Android 11
- Latest crDroid changes for Android 11
Enjoy
Click to expand...
Click to collapse
Finally got around to flashing my beloved dragon again today, looking really good! No bugs or glitches so far, just a lot of customizable awesomeness
Once again thank you so much for your ongoing support for this ageing tablet, I would love to send the equivalent of a few coffees or beers yours way if you tell me how.

It's time for a new build ..
crDroidAndroid-11.0-20210810-dragon-v7.9.zip
Changes:
- Google Security updates -> August 2021
- Latest device and kernel changes for dragon
- Backport of Wifi-Display (Miracast) for Android 11
- Latest crDroid changes for Android 11
Enjoy

Maybe it is good chosen one

followmsi said:
It's time for a new build ..
crDroidAndroid-11.0-20210810-dragon-v7.9.zip
Changes:
- Google Security updates -> August 2021
- Latest device and kernel changes for dragon
- Backport of Wifi-Display (Miracast) for Android 11
- Latest crDroid changes for Android 11
Enjoy
Click to expand...
Click to collapse
As always, thank you so much for your ongoing support for the good old dragon!
Just a note in case anyone else stumbles upon this: I could not get this build to boot with OpenGapps and a clean install, tried three times including format data and everything. Then tried NikGapps and it worked like a charm.
ROM itself is awesome, no problems so far, reasonably fast considering the hardware and a lot of cool features.

This is my last crDroid build for Android 11 .. the next build will be based on 12.
crDroidAndroid-11.0-20211214-dragon-v7.13.zip
Changes:
- Google Security updates -> December 2021
- Latest device and kernel changes for dragon
- Latest crDroid changes for Android 11
Enjoy

[ROM][Signature Spoofing]LineageOS 18.1 for S10E/S10/S10+ Exynos

{
"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"
}
LineageOS 18.1 for Galaxy S10 Series
Code:
/*
* Your warranty is now void.
*
* I am 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.
*/
Working:
- Wifi
- Sound
- mali drivers
- USB tethering
- Video Playback
- Fingerprint Sensor
- Ril (Mobile data,calls, sms and stuff)
- Sensors
- Bluetooth
- Wifi HotSpot
- MTP
- 2D and 3D gpu acceleration
- HW encoding/decoding
- GPS
- Cameras (All of them)
- HWcomposer (HWC)
- Signal indicator
- Double tap to wake
- Wireless PowerShare
Not Working
- VoLTE and VoWiFi will not be implemented (for now) as they heavily depand on samsungs framework
To properly report a bug (Please dont report things already on the Not Working list)
a) Logcat
b) /proc/last_kmsg (or /proc/kmsg)
c) /data/tombstones
d) dmesg
Please do not report bugs if you have performed any system modifications excluding gapps installation
Installation instructions
Make sure you are on Q stock firmware (All of the Q firmwares are tested and confirmed to be working, This should be the case with new fws too as long as Samsung doesnt significantly change bootloader trustzone bits)
Download Q twrp from this thread
flash twrp as per given instructions
if you are coming from stock and have encryption enabled format data (Note i said format, Wiping it in twrp is not the same as formating it)
wipe cache, dalvik cache and system
flash LineageOS
If you want to have gapps flash them right after flashing the rom before first booting
Reboot the device
Downloads:
Google Drive
Mega.nz
(Select build coresponding to your devices codename, S10e = beyond0lte | s10 = beyond1lte | s10+ = beyond2lte)
sha256 checksums
Code:
c8b961734a7972e9db9110785ba622d48c65a3c8ada9c611165864b0411f6699 lineage-18.1-20211111-UNOFFICIAL-beyond2lte.zip
fea1d76cb049cf3d83b9863da19dd0c46b70f91cec7c2a820915adb8943a671c lineage-18.1-20211111-UNOFFICIAL-beyond1lte.zip
540c111583147e94076959fdf3ff51c3f8fc2f29ec98949c6a105d936882f8ce lineage-18.1-20211111-UNOFFICIAL-beyond0lte.zip
If you need general help or questions feel free to join Telegram group
READ BEFORE INSTALLING MAGISK
Gapps
I do this in my free time so bear that in mind when you notice I didn't fix known bug in next available build, Currently i work on this alone and i am not one of those kangers that just copy source and claim it as their own work,
if you want to support the project feel free to buy me some coffee paypal.me/ivanmeler
Due to requests from some users I added signature spoofing support to the rom which allows usage of MicroG
you can simply install MinMicroG and grant it needed permissions for signature spoofing to make it work as intended
Based On Android R
Changelog
12.11.2021.
- Merged November 2021. security update
- Further Improved bluetooth in call handling
- Added more advanced burn in protection
- Misc performance and stability improvements
- Synced with LOS source
06.10.2021.
- Merged October 2021. security update
- Improved bluetooth in call handling
- Synced with LOS source
10.09.2021.
- Merged September 2021. Security update
- Synced with LOS source
06.08.2021.
- Merged August 2021. Security update
- Synced with LOS source
10.07.2021.
- Merged July 2021. Security update
- Performance and stability improvements
- Changed sensors handling in doze mode to prevent battery drain
- Synced with LOS source
10.06.2021.
- Merged June 2021. Security update
- Synced with LOS source
06.05.2021.
- Added wifi and portable hotspot overlays
- Merged May 2021. Security update
- Synced with LOS source
08.04.2021.
- Fixed USB C audio input/output
- Fixed charging with device powered off (It also has nice new animation now)
- Merged April 2021. Security update
- Misc performance and stability improvements
- Synced with LOS source
08.03.2021.
- Added signature spoofing support
- Synced with LOS source
05.03.2021.
- Merged March 2021. Security update
- Performance and stability improvements
- Synced with LOS source
06.02.2021.
- Merged February 2021. Security update
- Misc performance and stability improvements
- Modernized AdvancedDisplay app codebase
- Cleaned up the source
- Updated magisk boot images
- Synced with LOS source
06.01.2021.
- Merged January 2021. Security update
- Fixed OpenGapps installation from lineage recovery
- Fixed features that broke with initial 18.1 merge
- Misc performance and stability improvements
- Synced with LOS source
09.12.2020.
- Merged December 2020. security update
- Merged December 2020 feature drop
- Merged S9DTK9 vendor blobs
- Switched to full vndk30 vendor
- Fixed ADB inside of lineage recovery
- Improved brightness handling even more
- Performance and stability improvements
- Updated recovery images provided in 3rd post
- Synced with LOS source
10.11.2020.
- Further improved auto brightness handling
- Merged November 2020. security update
- Performance and stability improvements
- Updated recovery images provided in 3rd post
- Synced with LOS source
03.11.2020.
- Fixed issues with overlays and s10 camera cutout
- Enabled access to fingerprint for apps that were looking for secure biometics device (e.g. paypal)
- Improved automatic brightness handling (Switched to calibrated sensor virtual device which calculates brightness more precisely)
- Pinned SystsemUI and SurfaceFlinger to ram to imrpove responsivness
- Added blur to dropdrown notifications panel
- Enabled device controls from power menu
- Synced with LOS source
- Misc performance improvements
22.10.2020.
- Merged october security update
- Added back mDNIe display tuning options
- Added back a lot of previously non working los features
- Misc performance and stability improvements
- Synced with los source
07.10.2020.
- Initial public release
XDA:DevDB Information
[ROM] LineageOS 18.0 for S10E/S10/S10+ Exynos , ROM for the Samsung Galaxy S10
Contributors
Ivan_Meler
Source Code: https://github.com/ivanmeler/android_kernel_samsung_beyondlte/tree/lineage-18.0
ROM OS Version: 11.0
Version Information
Status: Stable
Created 2020-10-07

Reserved

Magisk
Magisk boot images are provided in this google drive folder named beyond*lte-boot-magisk.img you can flash them on boot slot and install magisk manager, No need to worry about rebooting to recovery or not having TWRP and magisk at the same time, Just make sure you dont try to boot to system with magisk patched TWRP as that might cause issues but as long as you have stock twrp and have flashed beyond*lte-boot-magisk.img image to boot slot you are fine, Source for given kernel is available at GitHub if you want to compile kernel yourself just run source build.sh devicename e.g. source build.sh beyond2lte, It will produce new boot image in build/ folder, To update magisk you can follow instructions given at this commit enjoy
Do note that you will have to reflash magisk boot image when updating rom

Wow ! Man, very nice job !
So, you stop release for Lineage 17 ?

troufiniou said:
Wow ! Man, very nice job !
So, you stop release for Lineage 17 ?
Click to expand...
Click to collapse
Nah will update that too, Just felt like releasing this because i had some time to sort out issues with it

The version of gapps doesnt matter even if this is android R right?
I can still flash android 10.0 gapps right?

Eidluci said:
The version of gapps doesnt matter even if this is android R right?
I can still flash android 10.0 gapps right?
Click to expand...
Click to collapse
there is link for android 11 gapps in first post under download section

Ivan_Meler said:
there is link for android 11 gapps in first post under download section
Click to expand...
Click to collapse
Oh thank you, my bad

Hi @Ivan_Meler i'm looking to change rom (i'm on hades rom but this one is not support anymore). And i just want to know if i need a custom kernel to improve battery life on LoS rom (this one or 17.1)?
Thanks for your precisions and your work to maintain on devices uptodate !

[Legenda] said:
Hi @Ivan_Meler i'm looking to change rom (i'm on hades rom but this one is not support anymore). And i just want to know if i need a custom kernel to improve battery life on LoS rom (this one or 17.1)?
Thanks for your precisions and your work to maintain on devices uptodate !
Click to expand...
Click to collapse
Battery life should be fine with stock kernel too as most of things are improved power hal side of things

Ivan_Meler said:
Battery life should be fine with stock kernel too as most of things are improved power hal side of things
Click to expand...
Click to collapse
Great. Thanks. I'll go on 17.1 LoS for awhile and will install this one when it will be more "polish".

Hi I don't know why but on previous lineage os ROMs, when I use TWRP and boot.img it would always boot back to recovery everytime I flashed a ROM.

Can you use lineage recovery to flash ROMs?

Ivan_Meler said:
If you want to root build you will have to use Magisk Canary from here, Once in app download Lineage Recovery for your device from Google Drive or Mega Patch image within manager and flash patched image to recovery partition, When booting hold recovery key combination till you get to first warning screen after that release keys and let system continue booting normally
Magisk curently has some issues properly detecting 2si devices so thats why we cant use boot.img without need for key combo for magisk right now, I will look into that in coming days but till then this is viable solution
Click to expand...
Click to collapse
Tried but says magisk still isn't installed please help.

Il be installing it soon to test it, very hype for android 11

FreeRunner2017 said:
Tried but says magisk still isn't installed please help.
Click to expand...
Click to collapse
make sure you followed instructions closely
1. Download recovery image
2. Download magisk canary app and patch recovery image
3. Flash magisk patched recovwry image (lineage recovery) to recovery partition
4. reboot and hold key combination for recovery until first warning screen shows up, after that release key combo
5. you should be in system with root
if you need further assistance im sure someone from telegram group can help you a bit more

Ivan_Meler said:
make sure you followed instructions closely
1. Download recovery image
2. Download magisk canary app and patch recovery image
3. Flash magisk patched recovwry image (lineage recovery) to recovery partition
4. reboot and hold key combination for recovery until first warning screen shows up, after that release key combo
5. you should be in system with root
if you need further assistance im sure someone from telegram group can help you a bit more
Click to expand...
Click to collapse
I did that but I still have no magisk

SD cards on the s10e just dont work, they keep saying its corrupted even after you format them in android itself ive also tried formatting in windows and twrp but same problem.
network traffic indicator can be turned on but never actualy shows up.
after installing magisk it takes apps 20 seconds to open.
if you need logs i will be happy to do so (if i can remember how to do so)

Wow, already an android 11 ROM ? Nice !
Is there the same issues as on L17 regarding bluetooth and front camera ?

Hi Ivan
Thanks for the great work! Awesome to have Android R available so early. Rom is solid.
On S10e i can confirm, it does not read MMC, i also tried formatting etc, not a biggy
On Bluetooth i can confirm that devices working, headphone sound, speakers etc. But on call when phoning, the sound does not come over to the headset.
HDMI Out is glitchy, creates flickering on secondary display, but is random....
Other than that, the rom is smooth and fast. Still checking battery...
Looking forward to developments...

Develop Bugs

welcome