Database Info

[MODULE] Detach3 - Detach Market Links

Detach3
Introduction
This Magisk module is for detaching apps from the Google Play Store.
It removes your defined packages from the 'Manage apps and device" section and disables them from auto-updates.
Installation
Flash module in Magisk Manager only.
Not necessary to reboot after flashing this module.
This module is designed to flash as many times as you like.
It is configured with a *configuration file. You can create one before flashing this module to define your package(s) or the default one will be used instead, which detaches YouTube by default.
Add your package name(s) you would like to detach to the configuration file, with each package name on a new line.
You can add more package names to your configuration file or the default one at any time, then simply just flash module again to apply it. Again, no need to reboot or any other user interaction needed.
Read the log that Magisk Manager displays when flashing the module, it displays the detached package(s) for confirmation.
*Configuration file: /storage/emulated/0/Android/detach.cfg
Reattach
https://forum.xda-developers.com/t/module-detach3-detach-market-links.3447494/post-84951411
Scheduler
https://forum.xda-developers.com/t/module-detach3-detach-market-links.3447494/post-84981039
Uninstallation
Uninstall with Magisk and reboot.
Troubleshooting
Follow uninstallation method. After reboot open playstore, navigate to the 'Manage apps and device' section so it can populate and then re-flash the module.
Still have an issue? Post your problem in detail and upload your Magisk installer log, found in your Download directory after saving it ( Shown here ).
Changelog
Spoiler: Click to expand
v3.00
- Initial release
v3.01
- Disabled Fallback broadcast
v3.02
- Disable auto-update for detached apps
- Disable playstore running in background
- Added uninstall script to revert changes
v3.03
- Updated sqlite3 binary
- Added support for x86 and x64
v3.04
- Added package check for configuration file
- Minor alterations
v3.05
- Recompiled sqlite3 binaries
- Improved device platform check
- Added database check
- Added the default detach.cfg file
- Minor alterations
v3.06
- Improved installer checks
- Fixed inflating uninstall script error
- Tidied installer script
- Added reattach feature*
* Comment out package name(s) in detach.cfg to reattach.
v3.07
- Fixed minor install.sh error on Android 11
- Improved some installer logic
- Added scheduler feature*
*Termux and Termux:API apks need to be installed beforehand for scheduler
v3.08
- Fixed playstore update log error on some devices
- Fixed script not applying package names with the same string of characters
- Fixed minor installer check for checking packages
- Fixed termux-api binary check
- Disabled package checks on some devices
- Added option to open playstore with scheduler notification
- Added option to open configuration file with scheduler notification
- Added option to flash module with scheduler notification
v3.10 - Note: Disable scheduler and uninstall previous version before installing this version.
- Removed package check (Some users have had issues, reboots etc.)
- Removed scheduler (Not needed for now)
- Removed unnecessary coding
- Added new method to prevent detached apps repopulating
- Added disabling of Play store trackers
- Other minor alterations in installer script
- Cleaned up installer script for new method
v3.11
- Added ignore GET_USAGE_STATS in AppOps
v3.12
- Updated sqlite binaries
- Removed disabling of fallback receiver
- Added disabling of alarm manager background service
v3.13
- Updated sqlite binaries
- Added ignore RUN_ANY_IN_BACKGROUND in AppOps
- Added ignore RUN_IN_BACKGROUND in AppOps
- Disabled App Discovery Service
Frequenly Asked Questions
Spoiler: Click to expand
Q. Can I use the old detach.txt?
A. No, I decided to ditch it. It now uses a new method explained in the installation section.
Q. Where is the boot script installed?
A. No boot script is needed for detaching, everything is done while flashing the module.
Q. Does this break safetynet?
A. No, it doesn't conflict with safetynet at all.
Q. Why shouldn't I re-enable Play Protect?
A. It will interfere with the module's purpose.
Q. Will having Play Protect disabled, open me up to vulnerabilities?
A. No, the playstore scans their market apk's after developers upload them.
Q. I usually install after-market apks (modified ones) and I think play protects me from this?
A. You should scan your unknown apk with Total Virus.
Q. How do you find a package name?
A. Magisk Manager lists your apps with the package name underneath each one, in the Magisk Hide list.
Q. What Magisk version is needed?
A. The module template is designed for Magisk v20.4+
Q. Do I need to uninstall previous version before updating?
A. No, unless stated. Just flash updated version.
Q. Do auto-updates still work for all my other apps that aren't detached?
A. Yes, auto-update and other notifications etc still work.
Download
See attached below -- detach-3.xx.zip
Previous versions
Detach Market Links for Theme Ready Apps *
Introduction
This Mod is for detaching apps from the Google Play Store that are included in the Theme Ready Apps zip and/or aroma installer from Team Black Out for CMTE and Substratum theme engines.
*Now also includes majority of all themed apps by Team Black Out by using an optional txt file.
The purpose is that updates will not show in your update list and also in update notifications from the Google Play Store.
This allows you to auto-update or the ability to use the update all button without the worry of updating Theme Ready Apps which will break your themes for those apps updated.
The Google apps that are detached if you're not using the optional txt file are Gmail, Google App, Google Plus, Hangouts, YouTube and Gboard (Google Keyboard).
Installation
Flash Mod in recovery, no need to wipe anything but if using SuperSU systemless mode or Magisk, flash this mod afterwards.
No need to flash again in-between ROM updates if using SuperSU systemless mode or Magisk or if your ROM supports addon.d scripts.
To detach more themed apps, place the detach.txt file either on root of your sdcard or internal storage and remove the comment from the apps you wish to detach and then flash Detach.zip
You can also use the optional detach.txt file to just selectively detach Theme Ready Apps.
If you don't use the supplied detach.txt file, only Theme Ready Apps will be detached.
To add your own custom packages (apps), read here > https://forum.xda-developers.com/showpost.php?p=72194332&postcount=147
Uninstallation
Rename detach.txt on sdcard to detach.remove, flash Detach.zip again and reboot.
This will remove all files related to installation, including the txt and custom file and restores all market links.
Note
If not using SuperSU or Magisk, you need to have init.d support.
The configured script doesn't execute until after 60 seconds when boot has completed, this also includes the remove script too.
This Mod has been tested by myself on Android 6 and 7.
You still have the ability to update your Theme Ready Apps via Google Play Store but you'll need to use the search function instead.
Changelog
v1.0
- Initial release
v1.1
- Changed detach method
v1.2
- Disabled service for database
v1.3
- Bug fixes
v1.4
- Added static sqlite binary
v2.0
- Added themed apps to detach with configuration txt file (optional)
v2.1
- Cleaned up installation script
- Added mod removal option
v2.2
- Magisk compatible (systemless installation)
- SuperSU systemless mode compatible (systemless installation)
- Fixed init.d detection
- Fixed market links reappearing
- Updated detach.txt (added Wallpapers, Pixel Launcher, Capture (GoPro))
v2.3
- Updated script and detach.txt (added Gboard, Clock, Camera, Google Connectivity Services, Google VR Services, Google Play Services)
v2.4
- Updated script and detach.txt (added Google Carrier Services and the ability to add custom packages)
v2.5
- Fixed market links reappearing
v2.6
- Main script updated for removal process
- Disabled code for a playstore service that no longer needs to be disabled
- Removed Contacts, Phone and Photos from default install

Thanks @hinxnz, I'll try the newest one.
Report 1.3: My theme ready gapps were detached except Google Calendar. I installed Black Google Calendar from TBO. Is there something I can do for this?

sunanulh said:
Thanks @hinxnz, I'll try the newest one.
Report 1.3: My theme ready gapps were detached except Google Calendar. I installed Black Google Calendar from TBO. Is there something I can do for this?
Click to expand...
Click to collapse
I was thinking about adding more themed apps to detach but would have to either use a config file on sdcard for example or probably better to make an aroma version but I would need all the package names first.

hinxnz said:
I was thinking about adding more themed apps to detach but would have to either use a config file on sdcard for example or probably better to make an aroma version but I would need all the package names first.
Click to expand...
Click to collapse
I think a "fulfilled" config file is simpler. So the users have just to add/remove '#' symbol.
For the name of the apps, maybe you can ask to TBO.
Cheers

hinxnz said:
I updated mod, see if it works for you now & I made a thread for it too > http://forum.xda-developers.com/and...detach-market-links-theme-ready-apps-t3447494
Click to expand...
Click to collapse
It's still not working on Stock rooted N. Thanks for trying.

Glad I saw your post that you put this thread up!
I downloaded 1.3 and flashed it and rebooted and waited for two minutes, but YouTube is still showing an update.

cmo220 said:
It's still not working on Stock rooted N. Thanks for trying.
Click to expand...
Click to collapse
Could you call script manually with Terminal Emulator and post output
RED ZMAN said:
Glad I saw your post that you put this thread up!
I downloaded 1.3 and flashed it and rebooted and waited for two minutes, but YouTube is still showing an update.
Click to expand...
Click to collapse
But the first version still works for you?
YouTube hasn't been updated for awhile AFAIK, what version is showing an update?
Are the other theme ready apps showing in your 'My apps & games' list?
Do you have any apps in your 'Wishlist', found in side menu?

hinxnz said:
Could you call script manually with Terminal Emulator and post output
But the first version still works for you?
YouTube hasn't been updated for awhile AFAIK, what version is showing an update?
Are the other theme ready apps showing in your 'My apps & games' list?
Do you have any apps in your 'Wishlist', found in side menu?
Click to expand...
Click to collapse
I couldn't get a /su.d folder so I put it in /system/su.d, which was already there and working. Here is the output.
angler:/ $ su
angler:/ # /su.d/99-detach.sh
sush: /su.d/99-detach.sh: not found
127|angler:/ # /system/su.d/99-detach.sh
angler:/ # Component {com.android.vending/com.google.android.finsky.services.DailyHygiene$DailyHygieneService} new state: disabled
CANNOT LINK EXECUTABLE "sqlite3": cannot locate symbol "u_setDataDirectory_55" referenced by "/system/xbin/sqlite3"...
Aborted
CANNOT LINK EXECUTABLE "sqlite3": cannot locate symbol "u_setDataDirectory_55" referenced by "/system/xbin/sqlite3"...
Aborted
And a bunch more of the same error.

The first version? I've deleted the previous versions .zips.
I've installed 1.0, 1.2, and 1.3.
Youtube has been showing this way for about a week, even after reboots.
11.32.53 is what's showing on Google Play, I've got 11.29.55 installed from TBO Theme Ready Apps v 21.
com.google.android.youtube
Showing up in the My apps & games list as installed...
Gmail
Google App
Google+
Google Photos
Hangouts
Wishlist, yes, I've got several.

RED ZMAN said:
The first version? I've deleted the previous versions .zips.
I've installed 1.0, 1.2, and 1.3.
Youtube has been showing this way for about a week, even after reboots.
11.32.53 is what's showing on Google Play, I've got 11.29.55 installed from TBO Theme Ready Apps v 21.
com.google.android.youtube
Showing up in the My apps & games list as installed...
Gmail
Google App
Google+
Google Photos
Hangouts
Wishlist, yes, I've got several.
Click to expand...
Click to collapse
Could you call script in Terminal Emulator and post output too.
For example:
Code:
su
/system/su.d/99-detach.sh

I don't think I've used terminal emulator except for twice since the G1, so I'm not sure if I did this right.
[email protected]:/ $
[email protected]:/ $ su
system/su.d/99-detach.sh <
sush: /system/su.d/99-detach.sh: not found127|[email protected]:/ #

hinxnz said:
Could you call script in Terminal Emulator and post output too.
For example:
Code:
su
/system/su.d/99-detach.sh
Click to expand...
Click to collapse
Is there any reason you are using a dynamically linked sqlite in your zip? the error the user is getting is because of that I believe. Idk I would try to use a static sqlite binary. Ill attach one so you/someone can have, but in case anyone is curious how to quickly compile sqlite3 statically ill post it in the spoiler tags below.
oh and just to note, I forgot to rename it from sqlite3 to sqlite before uploading
Im not going to explain the lines though, pretty straight forward imho
/opt/androideabi is my ndk toolchain prefix
Code:
mkdir sqlite3-static
cd sqlite3-static
wget https://sqlite.org/2016/sqlite-amalgamation-3140100.zip
unzip sqlite-amalgamation-3140100
cd sqlite-amalgamation-3140100
export PATH=$PATH:/opt/androideabi/bin
cp $(ANDROID_BUILD_TOP)/bionic/libdl/libdl.c .
cp /opt/androideabi/sysroot/usr/include/android/dlext.h .
cp /opt/androideabi/sysroot/usr/include/dlfcn.h .
arm-linux-androideabi-gcc -static -I./ -L./ -ldl *.c -o ../sqlite3
cd ../
file ./sqlite3

Surge1223 said:
Is there any reason you are using a dynamically linked sqlite in your zip? the error the user is getting is because of that I believe. Idk I would try to use a static sqlite binary. Ill attach one so you/someone can have, but in case anyone is curious how to quickly compile sqlite3 statically ill post it in the spoiler tags below.
oh and just to note, I forgot to rename it from sqlite3 to sqlite before uploading
Im not going to explain the lines though, pretty straight forward imho
/opt/androideabi is my ndk toolchain prefix
Code:
mkdir sqlite3-static
cd sqlite3-static
wget https://sqlite.org/2016/sqlite-amalgamation-3140100.zip
unzip sqlite-amalgamation-3140100
cd sqlite-amalgamation-3140100
export PATH=$PATH:/opt/androideabi/bin
cp $(ANDROID_BUILD_TOP)/bionic/libdl/libdl.c .
cp /opt/androideabi/sysroot/usr/include/android/dlext.h .
cp /opt/androideabi/sysroot/usr/include/dlfcn.h .
arm-linux-androideabi-gcc -static -I./ -L./ -ldl *.c -o ../sqlite3
cd ../
file ./sqlite3
Click to expand...
Click to collapse
Thank you Surge! :highfive:

Surge1223 said:
Is there any reason you are using a dynamically linked sqlite in your zip? the error the user is getting is because of that I believe. Idk I would try to use a static sqlite binary. Ill attach one so you/someone can have, but in case anyone is curious how to quickly compile sqlite3 statically ill post it in the spoiler tags below.
oh and just to note, I forgot to rename it from sqlite3 to sqlite before uploading
Im not going to explain the lines though, pretty straight forward imho
/opt/androideabi is my ndk toolchain prefix
Code:
mkdir sqlite3-static
cd sqlite3-static
wget https://sqlite.org/2016/sqlite-amalgamation-3140100.zip
unzip sqlite-amalgamation-3140100
cd sqlite-amalgamation-3140100
export PATH=$PATH:/opt/androideabi/bin
cp $(ANDROID_BUILD_TOP)/bionic/libdl/libdl.c .
cp /opt/androideabi/sysroot/usr/include/android/dlext.h .
cp /opt/androideabi/sysroot/usr/include/dlfcn.h .
arm-linux-androideabi-gcc -static -I./ -L./ -ldl *.c -o ../sqlite3
cd ../
file ./sqlite3
Click to expand...
Click to collapse
Cheers, thanks and yeah that's definitely the reason

Super idea, this would of been good a few months ago when google pushed their framework update and it broke some apps that i kept from updating,,, @Shaftamle google keyboard is the main on one, thank you
3GotoM ym morf tneS

Version 1.4 works for me now on 7.0. Thanks everyone!

Installed version 2.0 earlier today and seems to be working perfectly. Nothing showing needing updated.
Thanks!

How to add Black Google Calendar and Black Keep in the list?

sunanulh said:
How to add Black Google Calendar and Black Keep in the list?
Click to expand...
Click to collapse
Just remove the comments from those two as well as the other theme apps you flash.
Here's an example, theme ready apps, calendar and keep will be detached.
Code:
Contacts
Gmail
Google App
Google Plus
Hangouts
Phone
Photos
YouTube
#Inbox
#Duo
#Dropbox
#PushBullet
Calendar
Keep
#Telegram
#Swiftkey
#Translate

I have tried installing your script... And no matter how I go about... I cannot get the script to populate the su.d directory like it should...
And... Since I don't understand your flashable... I can't pull what I want out of it...
Could you explain how to install said script without recovery?
Thanks

[TOOLKIT][OnePlus 3, 3T and 5]Root, Recovery, Drivers, Bootloader, DM_VERITY

Proudly presenting to you
neisor's TOOLKIT for the OnePlus 3, the OnePlus 3T and the OnePlus 5.
ALL-IN-ONE TOOLKIT
32-bit & 64-bit versions available!​
HTML:
/*
* 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 the features included in this toolkit
* before you use it! You are choosing to make the modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* USE WITH CAUTION AT YOUR OWN RISK!
*/
With this TOOLKIT you will be able to:
- Install the official OnePlus USB Drivers for Windows
- Check your Bootloader status
- Unlock and Lock the Bootloader (will wipe your data)
- Enable and Disable DM_VERITY
- Choose if you want to use the 32bit binaries for the fastboot and adb or the 64bit binaries (both working correctly)
- Flash TWRP recovery
- Flash stock recovery
- Disable encryption (will wipe your data)
- Wipe cache
- Push the SuperSU.zip or the Magisk.zip files in order to acquire ROOT (SuperSU v2.82, Magisk v13.3)
- Show official User Manuals for the respective device
- Check the fastboot and adb connectivity of your phone​
You can choose between the 32-bit or the 64-bit binaries of fastboot and adb. I recommend using the 32-bit for the normal user. Use the 64-bit binaries only if you want to use the fastboot and adb with very large files which are not included in this toolkit.
EVERYTHING NEEDED IS PROVIDED, THERE'S NO NEED TO DOWNLOAD ANYTHING ELSE!
DOWNLOAD ONCE AND USE WITH ALL OF THE SUPPORTED DEVICES EVEN WITHOUT THE INTERNET CONNECTION!​
Supported devices:
- OnePlus 3
- OnePlus 3T
- OnePlus 5
Instructions:
- Download the toolkit zip file
- Extract the toolkit zip file
- Enable USB Debugging and OEM Unlock option in the Developer Settings
- Connect your phone to your PC via USB cable
- Run the toolkit bat file (the file is named "RunMe_xxxxxxxxxxx.bat")
- Install the USB Driver which is included in the toolkit
- Perform any other operation you want with the toolkit
DOWNLOAD MIRRORS:
(If you do NOT know which variant to download, just download the first one (32-bit).)
1.) For a normal and average user (32-bit variant):
Mega | Google Drive
2.) For an expert user or developer (64-bit variant):
Mega | Google Drive
Credits:
- TWRP.me
- OnePlus
- Google
- @Chainfire
- @topjohnwu
XDAevDB Information
[TOOLKIT][OnePlus 3, 3T and 5][EASY-TO-USE]Root, Recovery, Drivers, Bootloader, 32&64
Contributors
neisor
Version Information
Status: STABLE
Current Version: v1.3
Stable Release Date: 2017-08-04
Beta Release Date: 2017-08-03
Created: 2017-08-03
Last Updated: 2017-08-05

Changelog:
v1.3
- Fixed bugs
v1.2
- Added dm_verity options (disable/enable)
- Added the option to show the toolkit's XDA thread
v1.1
- Initial Stable release
- Updated Magisk to v13.3 and added the Magisk Manager apk file
v1.0
- Initial Beta release

Reserved
***

First!!!
Sent from my ONEPLUS A3000 using Tapatalk

What make the 64bit a developer version? I mean when was the last CPU which had only 32bit ? 10 years ago maybe. This keeps people confusing when someone tries to say that 32bit is standard and 64bit ist advanced and not for normal users. I mean how is even possible that Microsoft releases windows 10 also in 32bit? Nothing makes sense ..
I mean I don't say anything about your tool. I just want to point at this confusing dilemma that we still have 32bit programs, and some even say that this is the recommended version.. in 2017...
sorry bro, this need to be said
still good luck with your tool

Thanks for the support,
Why Magisk v12 and not v13?

dr_root said:
What make the 64bit a developer version? I mean when was the last CPU which had only 32bit ? 10 years ago maybe. This keeps people confusing when someone tries to say that 32bit is standard and 64bit ist advanced and not for normal users. I mean how is even possible that Microsoft releases windows 10 also in 32bit? Nothing makes sense ..
I mean I don't say anything about your tool. I just want to point at this confusing dilemma that we still have 32bit programs, and some even say that this is the recommended version.. in 2017...
sorry bro, this need to be said
still good luck with your tool
Click to expand...
Click to collapse
Thank you for your feedback.
Just to clarify:
I made the 64-bit version in case that someone would need to use the included fastboot and adb binaries for a full stock ROM installation via adb. I once ran into this issue where the 32-bit (most common) variant just would not load the big zip file (over 1GB in size). Therefore I thought it would be nice to have the 64-bit variant available if someone needed it and wanted to use it with their own files of choice.
The 32-bit version will work awesome with the entire toolkit. The 64-bit one is for the users who want to experiment or use the fastboot and adb binaries with other files than provided in the toolkit.
Note: On 64-bit systems you will have no problem to run the 32-bit variant because the 64-bit systems have the support libraries for the 32-bit applications. But not vice-versa.
Kind regards,
neisor

Midomad said:
Thanks for the support,
Why Magisk v12 and not v13?
Click to expand...
Click to collapse
Thank you for the hint!
I will include the v13 in the next version of the toolkit.
Best regards,
neisor

New release has been uploaded!
Changelog:
v1.1
- Initial Stable release
- Updated Magisk to v13.3 and added the Magisk Manager apk file

New version is up!
Changelog:
v1.2
- Added dm_verity options (disable/enable)
- Added the option to show the toolkit's XDA thread

Will dm_verity disable work with latest openbeta firmware?

tashimotor said:
Will dm_verity disable work with latest openbeta firmware?
Click to expand...
Click to collapse
I think it would not have any impact on the ROM as-is, only with the dm_verity disabled you will not see the annoying message during the start-up of your phone. In any case, please do some research on dm_verity if you are not sure what it does or how it works.
Kind regards,
neisor

neisor said:
I think it would not have any impact on the ROM as-is, only with the dm_verity disabled you will not see the annoying message during the start-up of your phone. In any case, please do some research on dm_verity if you are not sure what it does or how it works.
Kind regards,
neisor
Click to expand...
Click to collapse
I just dont want to see this message.

tashimotor said:
I just dont want to see this message.
Click to expand...
Click to collapse
These might be of help to you regarding dm_verity:
https://source.android.com/security/verifiedboot/
and
https://source.android.com/security/verifiedboot/dm-verity
You can get a pretty decent idea of how it works and what it actually is out of those articles.
Kind regards,
neisor

Haven't gotten my hands on a OnePlus 5 yet but thanks for bringing another great tool to the forums

blanco613 said:
Haven't gotten my hands on a OnePlus 5 yet but thanks for bringing another great tool to the forums
Click to expand...
Click to collapse
Hello,
Thank you for the support!
This tool is compatible with the OnePlus 3, 3T and 5. So, you'll be good to go with any of those devices using this toolkit.
Best regards,
neisor

neisor said:
Hello,
Thank you for the support!
This tool is compatible with the OnePlus 3, 3T and 5. So, you'll be good to go with any of those devices using this toolkit.
Best regards,
neisor
Click to expand...
Click to collapse
Yeah I'm still rocking the OP3 but I'm already good as far as rooting and such goes. I just appreciate devs and their contributions

New version is up!
Changelog:
v1.3
- Fixed bugs

Nice work man thanks a lot can you also include in some future update decrypt/encrypt option?

Great work @neisor. BIG thanks:good:

[ROM][UNOFFICIAL]LineageOS15.1+MICROG

UNOFFICIAL LineageOS fork with built-in microG gapps implementation.​LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
While the core operating system is still released as part of the Android Open Source Project, the majority of core apps are not. It gets worse: More and more libraries and APIs are only available on phones that run various Google apps pre-installed, effectively locking third-party apps to the Google ecosystem. Several popular open-source applications already require some of Google’s proprietary libraries to be installed. Increasing demand in the free software community in addition to severe problems in Google’s proprietary software discovered by the Android modding community, have led to the development of a free software clone of Google’s proprietary core libraries and applications - the microG Project was born.
This image uses the restricted microG patch meaning only system packages embedded in the build can use FAKE_SIGNATURE permission.
I have also replaced the default chromium system webview with the bromite system webview (20190519 build) which includes extra ad-blocking and privacy patches on top of chromium.
Code:
DISCLAIMER: THERE IS NO WARRANTY OF ANY KIND APPLICABLE TO THE CONTENT BELOW
What's working:
Boots
Wifi
NFC
Bluetooth
Camera
Video Playback
Audio
Sensors
GPS
SafetyNet Check passes both Basic Integrity and CTS profile match!
Known Bugs:
Phone is not detected by adb while booted in recovery mode (TWRP). I don't know if that's a bug in TWRP or on my laptop's USB drivers. If the phone has an OS installed (checked on various ROM's) (ie booted in system mode) it is detected, but not when in it is booted in recovery mode and running the latest TWRP. Place the image in an sdcard, put it in the phone and install it from there as a workaround. (Adb sideload can also work.)
Battery consumption appears to have improved on later builds, probably because of this change.
Instructions:
Download and install the latest twrp - dl-link (Steps on how to do it not covered here.)
Reboot to recovery
Wipe Data+Cache+Dalvik+System
Install ZIP file.
Reboot
Downloads:
Latest Build: lineage-15.1-20190519-CUSTOM_LINEAGE_MICROG-s5neolte.zip - lineage-15.1-20190519-CUSTOM_LINEAGE_MICROG-s5neolte.zip.md5sum
20190319 Build: lineage-15.1-20190319-CUSTOM_LINEAGE_MICROG-s5neoltexx.zip - lineage-15.1-20190319-CUSTOM_LINEAGE_MICROG-s5neoltexx.zip.md5sum
Reporting Bugs:
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Notes:
Many thanks to Stricted for pointing me out to the patch needed to fix a phone reboot whenever the phone connected to Wi-Fi
This is an amateur hobby project. I recommend against using this image as a daily driver, and I am quite likely to be unable to help you with any problems you experience (because I don't know enough about building a ROM).
Source Code:
Complete instructions on how to build this image on your own here !
Team Exynos7580 sources
LineageOS4microG CI/CD docker image code
FAQ:
Q: What is microG?
A: The projects webpage will do a better job than me.
TLDR version: A free software implementation of some proprietary Google Play services API's.
XDA:DevDB Information
LineageOS4microG, ROM for the Samsung Galaxy S5 Neo
Contributors
Iolaum, Stricted
Source Code: https://github.com/Iolaum/s5neoltexx-lineageos-microg
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: TWRP
Based On: LineageOS
Version Information
Status: Testing
Created 2018-11-18
Last Updated 2018-11-19

It seems interesting the ROM who has installed the details please as it runs the ROM

Rovar22 said:
It seems interesting the ROM who has installed the details please as it runs the ROM
Click to expand...
Click to collapse
Hello, I am not sure what you ask. Can you please elaborate?

Iolaum said:
Hello, I am not sure what you ask. Can you please elaborate?
Click to expand...
Click to collapse
Hey there, I'm guessing that he wants a log of someone who has already installed the system, to find out whether he wants to install it or not.
I'm going to flash it today and maybe post a log from a clean install, if it is helpful to anyone.
Btw thank you lolalum for the build and the instructions!
It's awesome that there's still someone left, who's trying to save us from google

Thank you for your answers, the installation is very good, what I need is the installation of "play store". Thanks for the Rom.

Sure, no problem.
Ok, now I understand: I guess you didn't know that you can't install the Playstore with microG.
The reason is, that it has been replaced by the "Fakestore" (you can find it in Settings>Apps*show system processes) It is just a fake or a placeholder to make apps "think" there is an official Playstore, when there really isn't one. So even if you tried to install it, (through Xda Labs for example) it would only be seen as an update of the Fakestore, and wouldn't work.
You can still get every app in the Playstore though, with "Aurora Store" or "Yalp Store". They both allow you to log in to your Google account and to buy apps and items. If that isn't needed "apkmirror.com" works as well.

Thank you

Rovar22 said:
Thank you
Click to expand...
Click to collapse
Glad I could help, but there is a "thank you button" for this

I've been using this rom for the past 2 days, and it worked ok, but I had issues with some calls with root and vibration settings and pretty much every time I tried to reboot to recovery the phone didn't respond at all until I removed the battery. (going to switch over to AospExtended rom now, because it supports microg as well.)

New build
New Build:
lineage-15.1-20190204-CUSTOM_LINEAGE_MICROG-s5neoltexx.zip - lineage-15.1-20190204-CUSTOM_LINEAGE_MICROG-s5neoltexx.zip.md5sum
Changelog:
Added custom microG apks built with PRs that allow to pass SafetyNet check.
Added Gsam Battery monitor and Matlog libre as system apps. They require permissions that need to be given by adb or root, it's easier to use their functionality if they are built in.

New Build:
lineage-15.1-20190214-CUSTOM_LINEAGE_MICROG-s5neoltexx.zip - lineage-15.1-20190214-CUSTOM_LINEAGE_MICROG-s5neoltexx.zip.md5sum
Changelog:
Updated microg apk from Nanodroid. (If Nandodroid releases newer versions before I release a new image you can download them from his repository and install them since I am using the pre-built apks signed by him instead of building them from source.)
Rebuilt so soon to include the lastest 5 Feb 2019 security update that patches a critical security vulnerability in Framework that could allow a remote attacker using a specially crafted PNG file to execute arbitrary code within the context of a privileged process.

New build
New Build:
lineage-15.1-20190319-CUSTOM_LINEAGE_MICROG-s5neoltexx.zip - lineage-15.1-20190319-CUSTOM_LINEAGE_MICROG-s5neoltexx.zip.md5sum
Changelog:
Updated microg gmscore apk from Nanodroid. (If Nanodroid releases newer versions before I release a new image you can download them from his repository and install them since I am using the pre-built apks signed by him instead of building them from source.)
Rebuild includes android security patch level march 2019. (Vendor security patch level is still March 2017 as in all earlier builds.
I installed this ROM on top of the previous one with no problems. Process is:
Reboot into recovery
Wipe Cache, Dalvik/ART Cache and System
Install new system image (zip file) and reboot.

New build features
New Build
lineage-15.1-20190519-CUSTOM_LINEAGE_MICROG-s5neolte.zip - lineage-15.1-20190519-CUSTOM_LINEAGE_MICROG-s5neolte.zip.md5sum
Changelog:
Moved to new Team Exynos7580 sources.
Updated microg gmscore apk from Nanodroid. (If Nanodroid releases newer versions before I release a new image you can download them from his repository and install them since I am using the pre-built apks signed by him instead of building them from source.)
Rebuild includes android security patch level May 2019. (Vendor security patch level is still March 2017 as in all earlier builds.
Replaced android's chromium system webview with the bromite system webview. Bromite is Chromium plus ad blocking and privacy enhancements.
Installation Instructions:
Because this build is built from a slightly different source than the previous ones and the default system webview was changed, I suggest a clean install wiping data, cache, dalvik and system.
Known Issues
- Nanolx and Bromite repositories are not added in Fdroid repositories by default as intended. They need to be added manually after installation. After you do so, ignoring updates for the Play store package is recommended if you don't plan to use it. The fakestore package included by default is only intended to be there for apps that want it to be there in order to function. Nanolx's playstore app allows in-app purchaces and other functionality which may or may not work properly - I 've never tested it not intend to do so.
Source code if you want to build it yourselves.

[MODS][SCRIPTS] Zackptg5's Misc Projects

Many of you already know that I have them all of my projects listed with their respective xda threads and download links on my website, but not all of them had an xda thread. So rather than cluttering xda with a new thread for each individual mod I make, I decided to put the smaller ones here :victory:
Binaries
Cross Compiled Binaries For Android Build Script
The new home for my binary build script. Combines what was formerly GNU and Misc build scripts into one. It contains a good number of useful binaries such as aria2, bash, coreutils (with advanced cp/mv - adds progress bar functionality), curl, gawk (GNU awk), sed, vim, zsh, and more. Check it out to see the expanding list
Keycheck
Finally tracked down the source code for this. This will compile the keycheck binary so you can use vol key selections and what not. Uses a modified build script by @osms0sis. Instructions on the repo
Zip for Android
This builds the zip binary, prepared for android by cloudchou @github in addition to a build script by @osm0sis that I modified for this. Just clone the repo, cd to jni, chmod the build script, and run it
Mods
Cross Compiled Binaries For Android
This zip contains a term script which can install any number of the growing list of binaries I've managed to cross compile for android. Here's the repo where they're all stored
Codec Power Gating Disabler [Deprecated]
Another straightforward one. Disables codec power gating. It's needed for some audio mods like @chdloc's Biquads
Kernel Sepolicy Patcher [Deprecated]
Unlike most sepolicy mods out there, this one changes sepolicy at the kernel level - meaning no boot script crap so it'll work regardless of other mods/root solutions (or lack there of). You can choose between enforcing or permissive while flashing it - you can use this to switch at will to test stuff out or whatever
Module Manager [Deprecated - not needed with magisk v24]
Magisk Canary v23.x got rid of the magisk-modules-repo from the app. This term script replaces that temporarily until an in-app solution is implemented. Allows you to update and install mods with ease.
Overlay Mount Fix [Deprecated]
Fix for overlay mount related issues with magisk - often seen in oneplus devices with /product
Misc
Searx Instance
Searx is a metasearch engine with a focus on privacy. It allows you to search many search engines at once without being tracked by them - I use it to remain private while using google and to for scientific journal article searching (science tab). I have more details on what it is/setup here on my website
More will be added when I come out with them. For a complete list of all of the stuff I work on, check out my website linked at the top of this post
Audio Mod Troubleshooting Guide
XDA:DevDB Information
Zackptg5's Misc Projects, Tool/Utility for all devices (see above for details)
Contributors
Zackptg5

Earlier this week I got Android Auto in my car. I never considered that Viper4Android wouldn't work with it. I was hoping the USB Policy Patcher would fix that but it didn't. It looks like this is a problem for most, if not all people.
Has anyone found a way to use V4A while connected to Android Auto through a USB cable? If so, please explain what you had to do. Thanks.

Updated mods for new unity 2.2
Also added option to notification_helper remover to remove libvolumelistener.so

@Zackptg5
If i want to use your Bash for android in a kitkat stockrom.. then the following zip is fine?..
I extracted the main files from your zip and made a simple zip...
since in Magisk Manager ..description about your bash for android says it needs 5.0+.....
Thanks

HemanthJabalpuri said:
@Zackptg5
If i want to use your Bash for android in a kitkat stockrom.. then the following zip is fine?..
I extracted the main files from your zip and made a simple zip...
since in Magisk Manager ..description about your bash for android says it needs 5.0+.....
Thanks
Click to expand...
Click to collapse
The compiled zip is for lollipop+. If you want it for older, go to the bash build script link in the OP and compile arm binary for Api 19 (or older)

Zackptg5 said:
The compiled zip is for lollipop+. If you want it for older, go to the bash build script link in the OP and compile arm binary for Api 19 (or older)
Click to expand...
Click to collapse
Thanks for quick reply...
But I dont have a pc sir...

HemanthJabalpuri said:
Thanks for quick reply...
But I dont have a pc sir...
Click to expand...
Click to collapse
Build script is for Linux. I'll try building later today

HemanthJabalpuri said:
Thanks for quick reply...
But I dont have a pc sir...
Click to expand...
Click to collapse
Here you go, latest bash stable compiled for kitkat (API=19) (and newer) arm devices

Zackptg5 said:
Here you go, latest bash stable compiled for kitkat (API=19) (and newer) arm devices
Click to expand...
Click to collapse
Thanks a lot for your time..
and Happy New Year...
but I just place in xbin without any other files?
i.e., /system/etc/bash/bashrc
/system/etc/bash.bash_logout
/system/etc/bash.bashrc
are not needed?

HemanthJabalpuri said:
Thanks a lot for your time..
and Happy New Year...
but I just place in xbin without any other files?
Click to expand...
Click to collapse
Right. Then chmod 0755 it

Zackptg5 said:
Right. Then chmod 0755 it
Click to expand...
Click to collapse
/system/etc/bash/bashrc
/system/etc/bash.bash_logout
/system/etc/bash.bashrc
are not needed?
I saw these files in your main zip v1.8.4

HemanthJabalpuri said:
/system/etc/bash/bashrc
/system/etc/bash.bash_logout
/system/etc/bash.bashrc
are not needed?
Click to expand...
Click to collapse
They're technically not needed but can be useful. You can place them manually, or unzip the bash module zip and replace the bash binary in the arm folder in the custom.tar.xz folder with the one I attached

Added zip and zipalign binary build repos

Updated bash to v5.0 stable

Zackptg5 said:
Updated bash to v5.0 stable
Click to expand...
Click to collapse
API 19?
also why nanodroid bash is 4.*mb and yours is 1.*mb?

HemanthJabalpuri said:
API 19?
also why nanodroid bash is 4.*mb and yours is 1.*mb?
Click to expand...
Click to collapse
I have it as minimum of 21 because that's the magisk minapi so I'm just keeping it consistent. You can always compile it for 19 with my build script here: https://github.com/Zackptg5/Bash-for-Android-Build-Script
My compiled binaries are stripped which means that inessential stuff (things not required for normal functions) were removed. See more on that here: https://en.wikipedia.org/wiki/Strip_(Unix)

the Kernel Sepolicy Patcher dont work for j5 pro android 8.1 twrp says error 1 when try to install

tutibreaker said:
the Kernel Sepolicy Patcher dont work for j5 pro android 8.1 twrp says error 1 when try to install
Click to expand...
Click to collapse
Log?

That all the rom installed busybox, and i try 2 versions of it and Same results

tutibreaker said:
That all the rom installed busybox, and i try 2 versions of it and Same results
Click to expand...
Click to collapse
Can you save the actual recovery log so I can see the cause of the error? After flashing zip, go to advanced -> copy log

[UNOFFICIAL][11] LineageOS 18.1 w/ microG patch for Pixel 4a (sunfish) (20210610)

Introduction
This is my personal build of LineageOS 18.1 for Pixel 4a with the microG patches applied. If you do not want / need to use microG, it may be a better idea to use the official build available here: https://download.lineageos.org/sunfish. This build is exactly the same as the official build except for the microG patch.
For discussion about the official build, please use the other thread instead: https://forum.xda-developers.com/t/rom-official-sunfish-lineageos-18-1.4255751/
Installation
Before installation, make sure your phone is updated to Android 11 firmware on both of the slots.
Whether you are installing the ROM for the first time or updating the ROM, please make sure you reboot to recovery again after `adb sideload`-ing the ROM before installing add-ons such as Magisk and GAPPS.
1. Download `boot-XXXX.img` (this contains the recovery needed for initial flashing)
2. Download `lineage-18.1-XXXX-UNOFFICIAL-petercxy-sunfish.zip`
3. Reboot your phone to fastboot mode
4. Run `fastboot flash boot boot-XXXX.img` from your PC
5. Reboot your phone into recovery mode (`fastboot reboot`, then press volume up immediately)
6. Erase data
7. Select Apply Update -> Apply Update from ADB
8. Run `adb sideload lineage-18.1-XXXX-UNOFFICIAL-petercxy-sunfish.zip` and wait for installation to finish
9. If you do not need to install any add-ons (e.g. Magisk or GAPPS), then just reboot into system
10. Otherwise, if you do need to install add-ons, reboot into recovery again (this puts your phone into the recovery of the newly-installed system), then install the add-ons using sideload. If you want to use GAPPS, they must be installed here before you boot into system for the first time (this doesn't apply to microG).
11. Enjoy
Updating
1. Download the newly released zip and reboot your phone into recovery
2. Select Apply Update -> Apply Update from ADB
3. Run `adb sideload lineage-18.1-XXXX-UNOFFICIAL-petercxy-sunfish.zip` and wait for installation to finish
4. If you did not have any add-ons installed before update (e.g. Magisk or GAPPS), then just reboot into system
5. Otherwise, if you did, you need to reboot into recovery again at this point before rebooting to system and re-flash every single one of the add-ons you had before. If you do not re-flash them before rebooting to the new system, the boot will fail and your phone will switch back to the old system automatically.
6. Reboot and enjoy.
Note: You don't need to update official firmware manually while LineageOS is installed by flashing latest official factory images. This LineageOS build now ships with latest official firmware updates which are tested to work with the ROM. Please avoid flashing the firmware manually while LineageOS is installed to avoid unnecessary issues.
Known Issues
- Use Magisk v21.4 or later if you want Magisk
- Some applications require microG to be installed in system partition to function, in which case you can consider using the Magisk microG module
- The eSIM manager only works with either GAPPS or microG installed. Without them, you can use eSIM, but you will not be able to add / remove / rename / disable your eSIM. The eSIM manager will also crash once or twice on first boot without GAPPS or microG, but after that it won't crash anymore (the system automatically disables it until you install microG or GMS)
- Disabling / Enabling eSIM may hang even with GAPPS or microG. However, rebooting normally fixes the issue and makes your action effective.
- I provide no guarantee for SafetyNet status or compatibility with any app that requires SafetyNet. Google has been tightening its SafetyNet verification and there is really not much we can do about it, and frankly most apps that require SafetyNet should not have done so in the first place. If you need SafetyNet, you are on your own.
Downloads
Note: This build has compatibility issues with MindTheGapps (just like the recent LineageOS weekly builds). It will be fixed in newer official weekly builds, but since this build is for microG users, I am not going to upload a new microG-patched build just to work around a GAPPS compatibility issue.
20210610: June 05 security update; sorry for the delay, LineageOS had some issues while merging this month's ASB.
This update also fixed some long-standing bugs, such as the initial crash dialog of the eSIM manager (when GAPPS or microG is not installed), and the extraneous battery percentage option in settings -> battery. Read the LineageOS changelog for the full update.
- boot-20210610.img: https://mega.nz/file/TVolEYKL#MrJH-AVk37JDc_iKCVJ2lFGgFLG9czrE4FnJokbjnqI
- lineage-18.1-20210610-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/uYw30SxT#CwWc0GwqMYoAT54TJqPK2U7M8Y3OzhbpPuvejkOB65o
20210507: May 05 security patches
- boot-20210507.img: https://mega.nz/file/rcJVHQYZ#KjFu84Wnqdx4Rq0fd6TZUlJuaD-RXFXmMCJM4V4z0Tc
- lineage-18.1-20210507-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/jYBTESqZ#ZRc7CkUt8aUYgZRLpF6S1_LHdUXwcUOKPsCBorcYZ1w
20210410: April 05 security patches
- boot-20210410.img: https://mega.nz/file/eYggCKba#l7QJUMkvyEBtyptVMmWVbXochJKmY__X4VIwTla1KqE
- lineage-18.1-20210410-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/bUpQhAQJ#uTe-2nHLKYsfFBKuJg0VAYISUCGMTbIpaC9qjEHFZ1c
20210308: March 05 security patches and official firmware / binary updates.
- boot-20210308.img: https://mega.nz/file/WIZxjAwA#P77ZdJ2YEed5WWmlijKcyRMLJ30KG36eL0mhQGjZWjI
- lineage-18.1-20210308-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/eRBTkYzC#iNZUA84XR80V1so7YvjQ7TyJuZKGY9BZf-MGRtgQOH8
20210222: Updated sources; Removed some non-functional LiveDisplay features; Switched to using Google's wifi_ext HAL; Reserved more space in system partitions for potentially larger GAPPS packages
- boot-20210222.img: https://mega.nz/file/KVxRDY6L#7l7oejw-XEd_m1BUdp0_Z2TyHVLE2KkaGQ6g7Op7dpk
- lineage-18.1-20210222-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/mUgzGSbC#88q95qVsI-7RJsecM8L2MHZ6EwNXrs54Xk6yi428rjU
20210207: Updated LineageOS source; Applied 2021-02-05 security patches; Added support for glove mode; Enabled support property for Google Assistant; Optimized vibration
- boot-20210207.img: https://mega.nz/file/aZxlDKgC#_9VR2ruCYUqmX8gLCBKX1KSMAsBYFDsLA6utk5EjB-g
- lineage-18.1-20210207-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/yZpFQQRJ#PZlNYzI2t2fZdf1T3v6pMRi1zJe7J26f-Eu_Pohm7p4
20200118: Updated LineageOS source; Attempted to fix GAPPS bootlooping issue
- boot-20210118.img: https://mega.nz/file/ONYSRLKC#FhRYEhfsBndqcrJrhd1F4Tv3uu3UZNDYnQe3EcrMyC0
- lineage-18.1-20210118-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/3VRgwZQQ#ynCPIDbW42hXvBWp8MoG-R9eEEzvnaQ649ULZM8lrAc
20210109: Updated LineageOS sources and updated build fingerprint to January.
- boot-20210109.img: https://mega.nz/file/qU5T2CLY#A7dkDfRS0gUaKzphT2_mm0IHW9_-3cIR76yvNV1Cs4A
- lineage-18.1-20210109-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/GNwyxb4S#UGHclk8p60QuRWrGl3LI-Hur9X_VKF46tBNfuD0Z9-o
20210107:
1) Synchronized LineageOS updates and AOSP Jan 5 security patch
2) The ROM now ships with latest official firmware, so you won't need to worry about updating firmware separately (you still need latest official firmware when installing the ROM for the first time though)
- boot-20210107.img: https://mega.nz/file/OYRnwaII#3Ipj99mG5tpXouRRKMqWDJmimH8U2q5mZ5LKj8ZEmdo
- lineage-18.1-20210107-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/aEBTFAwK#EM3fKYQG4Y2najLhRkZlPqDwPSwkV-yfsSlH7Za7UYM
20201229: Synchronized LineageOS updates and fixed biometric authentication (fingerprint) in third-party applications.
- boot-20201229.img: https://mega.nz/file/yMow3aDb#ByY4yG6LeAquqBd2vu2UnZUz2xukHYjWbIfXnlkT_XM
- lineage-18.1-20201229-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/SA5WDAZQ#fMRB9w4LLSxSAGxHOtEmN9gRBTmrnF8ozKawM34cIxU
20201227:
- boot-20201227.img: https://mega.nz/file/6cI3lKKK#p8Nq3jUOsOoPDeV6yPj4hQtXGIHu8-D54_g3gkzdi0w
- lineage-18.1-20201227-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/SdQnTaBa#83JjZojOS9JCRdYOng6Y0LLoUl8StAdrwsTbCSqAMhs
Sources
Device Tree: https://github.com/PeterCxy/android_device_google_sunfish
Kernel: https://github.com/PeterCxy/android_kernel_google_sunfish
Thanks: DirtyUnicorn sunfish contributors, SuperiorOS sunfish contributors, LineageOS coral contributors and the LineagOS community.

After some trial and error I got it up and running. After booting the ROM I returned to recovery, factory reset then side loaded Razorloves micro gapps.
Thanks for the build

Nice! Appreciate the work you've done on the trees!
@PeterCxy what vendor do you use? Can I clone it? Or should I extract myself?

Gave this a shot, everything seemed to loadup fine. Wasn't able to get call screen to show up tho, I flashed razorloves gapps, anything to do to get that to work?

ny-hardcore said:
Nice! Appreciate the work you've done on the trees!
@PeterCxy what vendor do you use? Can I clone it? Or should I extract myself?
Click to expand...
Click to collapse
I pushed the vendor blobs I extracted on my GitHub at https://github.com/PeterCxy/android_vendor_google_sunfish, but you can also extract it yourself as I have also pushed my full sunfish-proprietary-files{,-vendor}.txt

This is amazing, thanks @PeterCxy
Where the instructions state to be on A11 on both slots does that mean I can do a flash-all with the latest A11 factory image? Currently on LOS 17

xeropressence said:
Gave this a shot, everything seemed to loadup fine. Wasn't able to get call screen to show up tho, I flashed razorloves gapps, anything to do to get that to work?
Click to expand...
Click to collapse
Unfortunately I have zero clue about this, and I don't live somewhere Call Screening is supported in the first place. This would probably need to be figured out by someone other than me :/

EggZenBeanz said:
This is amazing, thanks @PeterCxy
Where the instructions state to be on A11 on both slots does that mean I can do a flash-all with the latest A11 factory image? Currently on LOS 17
Click to expand...
Click to collapse
Yes you can, but that flash-all script only flashes it on one slot, so to guarantee you have A11 on both slots you'd still need to manually switch the slot and execute that script a second time. The reason why you need A11 on both slots is that the recovery installs the new ROM to the inactive slot, so if the inactive slot is not also on A11, the ROM will probably not boot properly.

PeterCxy said:
Yes you can, but that flash-all script only flashes it on one slot, so to guarantee you have A11 on both slots you'd still need to manually switch the slot and execute that script a second time. The reason why you need A11 on both slots is that the recovery installs the new ROM to the inactive slot, so if the inactive slot is not also on A11, the ROM will probably not boot properly.
Click to expand...
Click to collapse
Thank you

EggZenBeanz said:
This is amazing, thanks @PeterCxy
Where the instructions state to be on A11 on both slots does that mean I can do a flash-all with the latest A11 factory image? Currently on LOS 17
Click to expand...
Click to collapse
You could just sideload the ota after booting the factory image as well.[/QUOTE]

10 hours so far and everything is smooth, great ROM, but I've noticed the battery consumption is less on SuperiorOS, need couple of days to confirm.

xeropressence said:
Gave this a shot, everything seemed to loadup fine. Wasn't able to get call screen to show up tho, I flashed razorloves gapps, anything to do to get that to work?
Click to expand...
Click to collapse
Considering call screen doesn't work on other Lineage pixel ROMs, this wouldn"t be any different.

Thank you very much @PeterCxy
I flash-all latest december 11 images and --set-active= slot to other partition and re flashed again. Following the instructions I now have LOS18 with micro-g running. Awesome! I would be interested in any builds with micro-g patches even when/if sunfish goes official LOS

Biometric/fingerprint unlock is not available in any apps like Bitwarden, wirex etc. Has this feature been removed in A11?
I have a working fingerprint and pattern unlock working on the phone, just no options in any usual apps

EggZenBeanz said:
Biometric/fingerprint unlock is not available in any apps like Bitwarden, wirex etc. Has this feature been removed in A11?
I have a working fingerprint and pattern unlock working on the phone, just no options in any usual apps
Click to expand...
Click to collapse
Do you have Play Services on it? I assume they use the Biometric API for that feature. And I assume that requires Play Services. Or a locked bootloader, some Trust Zone thing... basically it probably isn't designed to work on a ROM that doesn't have some integrity check or secure thingy access.
info:
Login with Biometrics on Android | Android Developers
In this codelab you will add biometric authentication to your app as part of your login process. You will not replace your current login process – users can still log in with their account password. Instead, you will augment your login process, giving users the convenience to not have to...
developer.android.com

jawz101 said:
Do you have Play Services on it? I assume they use the Biometric API for that feature. And I assume that requires Play Services. Or a locked bootloader, some Trust Zone thing... basically it probably isn't designed to work on a ROM that doesn't have some integrity check or secure thingy access.
info:
Login with Biometrics on Android | Android Developers
In this codelab you will add biometric authentication to your app as part of your login process. You will not replace your current login process – users can still log in with their account password. Instead, you will augment your login process, giving users the convenience to not have to...
developer.android.com
Click to expand...
Click to collapse
I don't use play services, but biometric unlock like autofill I think doesn't rely on play services, its part of AOSP? Both my Tab S5e and previous pixel 4a builds were LOS17 with no google services or microg installed and I have Biometric support in all usual apps

jawz101 said:
Do you have Play Services on it? I assume they use the Biometric API for that feature. And I assume that requires Play Services. Or a locked bootloader, some Trust Zone thing... basically it probably isn't designed to work on a ROM that doesn't have some integrity check or secure thingy access.
info:
Login with Biometrics on Android | Android Developers
In this codelab you will add biometric authentication to your app as part of your login process. You will not replace your current login process – users can still log in with their account password. Instead, you will augment your login process, giving users the convenience to not have to...
developer.android.com
Click to expand...
Click to collapse
I noticed the same issue with bitwarden, never had this issue before

EggZenBeanz said:
Biometric/fingerprint unlock is not available in any apps like Bitwarden, wirex etc. Has this feature been removed in A11?
I have a working fingerprint and pattern unlock working on the phone, just no options in any usual apps
Click to expand...
Click to collapse
hmmm it's also not available in my Keepass2Android. I'll look into this later -- I don't think fingerprint support is part of Play Services.

EggZenBeanz said:
Biometric/fingerprint unlock is not available in any apps like Bitwarden, wirex etc. Has this feature been removed in A11?
I have a working fingerprint and pattern unlock working on the phone, just no options in any usual apps
Click to expand...
Click to collapse
It might be an issue with the LineageOS source tree when I last synchronized. I checked some of my other devices with LOS built on the same date and they all don't have the fingerprint option available in apps.

PeterCxy said:
It might be an issue with the LineageOS source tree when I last synchronized. I checked some of my other devices with LOS built on the same date and they all don't have the fingerprint option available in apps.
Click to expand...
Click to collapse
I came from this build, https://forum.xda-developers.com/t/lineage-18-android-11-for-pixel-4a-sunfish.4199889/
And there it worked fine
I first installed with MicroG, then went with Gapps, and neither work