Database Info

[ROM][STABLE][R7S/R7Sf][OFFICIAL][9.0] LineageOS 16.0 (Qualcomm)

{
"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 is a free, community built, aftermarket firmware distribution of Android 9.0 (Pie), 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. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
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.
Devices supported by this package :
Officially: Oppo R7S ( R7Sf / R7Sfg / Snapdragon Model Only! )
What's working :
Boots
RIL (Calls, SMS, Data)
Wifi
Bluetooth
Camera ( Videos And Photos )
Video Playback
Audio ( Record and Playback )
Sensors
Flash
Led
GPS
What's not working :
Instructions :
Official Instructions here in LOS Wiki.
Download the latest build and gapps arm64 for 9.0
Open GApps (choose the variant you want. Recommended nano package)
Reboot to recovery
Flash the latest build and gapps
Reboot
Downloads :
Builds
ROM : https://download.lineageos.org/r7sf
Google Apps : http://opengapps.org/
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 /sys/fs/pstore/console-ramoops. (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. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
Phone model (R7Sf, R7Sfg):
LOS version:
LOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
LOSSettings/Performance settings (other than stock):
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Credits :
[MENTION]My wife[/MENTION]: For her patience
[MENTION]Uberlaggydarwin[/MENTION]: For you know what!
[MENTION]mikeioanna & maniac103[/MENTION]: For all their amazing work on the R7 series!
Unknown Oppo Dev: For providing the PS Kernel Source Code
LineageOS Team
Donations :
Please consider donations to support development.
mikeioannina: Donating via PayPal without him LineageOS 16.0 for the R7sf would not have been possible!
XDA:DevDB Information
LineageOS-16.0 for Oppo R7S (1080p), ROM for the Oppo R7S
Contributors
mikeioanna,maniac103,celoxocis
Source Code: https://github.com/LineageOS
ROM OS Version: 9.0 Pie
ROM Kernel: Linux 3.10.108
ROM Firmware Required: Unlocked bootloader
Based On: LineageOS 16.0
Version Information
Status: R7Sf entered Official builds.
Created 2019-04-17
Last Updated 2019-04-17

*reserved*

Please make sure before upgrading to LineageOS 16.0 to read the Official Instructions here in LOS Wiki carefully!
Make sure before flashing you upgrade the TWRP version with the one provided in the instructions page due to changes to support hardware accelerated encryption on our R7S!
You will run into issues if you do not upgrade to the provided TWRP version!
I recommend a clean install due to above changes.

Followed the instruction exactly but wifi does not work (mac address 02:00:00, it can not find any AP...)
If someone has this issue like me, flash back to Spectrum then boot into it and connect to some AP, then flash LineageOS again, but do not wipe anything.

Does Pixel Launcher work for you?
It crashes on my phone. A workaround: https://www[.]reddit[.]com/r/LineageOS/comments/awjvnk/lineageos_16_stock_open_gapps_pixel_launcher/

Working well so far even though I updated using twrp 3.2.3
Only issues are, app permissions seem to show up when they want and bluetooth connection can be ropey depending on device. Have one receiver with no issues but my Sennheisers cant keep a connection from two feet. Will try re-pairing.
Thanks to you all. :highfive:
I needed this for root, so for anyone who needs it...
https://mirrorbits.lineageos.org/su/20190304/addonsu-16.0-arm64-signed.zip
Edit.....Just updated to latest build and root disappears so the above will be needed.
Will the SU binaries be reinstalled for future builds?

LordAlberto said:
I needed this for root, so for anyone who needs it...
https://mirrorbits.lineageos.org/su/20190304/addonsu-16.0-arm64-signed.zip
Edit.....Just updated to latest build and root disappears so the above will be needed.
Will the SU binaries be reinstalled for future builds?
Click to expand...
Click to collapse
Why not use Magisk?

trmdi said:
Why not use Magisk?
Click to expand...
Click to collapse
I do use magisk, I need to install this beforehand or magisk doesn't work.
When I first installed 16, I read that lineage removed the su binaries so there is no root out of the box.
Bit of a pain really.

When the screen is locked, you're still able to swipe down from the status bar to expand it to show buttons. Is there any way to disable expanding the status bar when the screen is locked?

Just tried the recommended TWRP image and it screwed it up. Now i have no recovery! I'll have to attach to a computer to see if I can reflash it to get back in. Anyone else try this with the same result?

Hi, is there any difference between the build 16-04 and 17-04 ? No changelog is shown.
https://download.lineageos.org/r7sf/changes/

Luuta said:
Just tried the recommended TWRP image and it screwed it up. Now i have no recovery! I'll have to attach to a computer to see if I can reflash it to get back in. Anyone else try this with the same result?
Click to expand...
Click to collapse
The recommended TWRP image is actually a lower version than the official image through the TWRP app, and that's why my recovery got screwed up. I'd flashed an earlier image onto a later one. The recommended one would probably be the one to use if you were switching to Lineage for the first time, maybe? Just to warn people not to be as careless as I am!
I spent half a day messing about with getting the tools again to perform a flash from my pc. Every time, I end up relying on "Minimal ADB & Fastboot" because I have no luck getting any other driver package to work. But this package really is the smallest pack to get it done and it makes it easy to use, thank goodness.
Thanks to the developers for continuing to work on the phone. I'm loving Android 9/Lineage 16. There isn't much of a visual change, which is great. Under the hood, it's more obvious, but it's definitely running much smoother than L15 already.
---------- Post added at 08:41 PM ---------- Previous post was at 08:39 PM ----------
trmdi said:
Hi, is there any difference between the build 16-04 and 17-04 ? No changelog is shown.
https://download.lineageos.org/r7sf/changes/
Click to expand...
Click to collapse
There will, of course, be changes, or it wouldn't be offered. Most changes are bug fixes or security updates, so you wouldn't necessarily notice any change.

Maybe the gestures are sensitive but every time I go out, the phone always opens my music player at destination. Have turned them off see if it happens again.
Never happened on 15.

Bluetooth seems to be a mixed bag so far. When it works it's fine, but when connection is lost re-pairing and forget/connect can be hit and miss. It will show the device but not be connected so you have to go deeper into settings to fix it.
More often I always end up going the long way round just to get connection.
BT ended up rock solid on 15 so I'm confident it'll improve.
Update. So clearing storage and cache in 'App info' seems to have fixed connection issue. Let's see how we get on...

LordAlberto said:
Bluetooth seems to be a mixed bag so far. When it works it's fine, but when connection is lost re-pairing and forget/connect can be hit and miss. It will show the device but not be connected so you have to go deeper into settings to fix it.
More often I always end up going the long way round just to get connection.
BT ended up rock solid on 15 so I'm confident it'll improve.
Update. So clearing storage and cache in 'App info' seems to have fixed connection issue. Let's see how we get on...
Click to expand...
Click to collapse
1
Mine keeps connecting, disconnecting, connecting... But only when there's no music playing, like it's trying to save power (so maybe it's one of the battery saving services under Android 9). Mine isn't forgetting, though. At least not yet...

Luuta said:
1
Mine keeps connecting, disconnecting, connecting... But only when there's no music playing, like it's trying to save power (so maybe it's one of the battery saving services under Android 9). Mine isn't forgetting, though. At least not yet...
Click to expand...
Click to collapse
Tried again today, it has the device listed but wont connect. Have to go all the way in BT menu to connect manually.
It's a problem with Pie on the whole apparently.

LordAlberto said:
Tried again today, it has the device listed but wont connect. Have to go all the way in BT menu to connect manually.
It's a problem with Pie on the whole apparently.
Click to expand...
Click to collapse
Ah, yes, it loses the pairing in our car, too. It's a small annoyance, can live with that!

is anyone success to install magisk on this rom ?

spongelovers said:
is anyone success to install magisk on this rom ?
Click to expand...
Click to collapse
yes. I flashed it right after flashing the rom without any problem.

spongelovers said:
is anyone success to install magisk on this rom ?
Click to expand...
Click to collapse
On page one of this thread I've linked the su code to get magisk to install.

[A-ONLY][TREBLE][9.0][A530F/A530W/A730F] Vendor Pie For Galaxy A8/A8+ 2018

I'm not responsible for whatever damage this could possibly cause to your device.
Before Starting Make Sure You Treble Your Device By This Guide here
If you appreciate the work i have done, Feel free to buy me a cup of coffee @paypal
Welcome to Pie Vendor For Galaxy A8/A8+ 2018 ONLY FOR A530F/A530W/A730F​
Some information you should know..
Full TREBLE Documentation here : https://source.android.com/devices/architecture
Generic System Image (GSI) Documentation here : https://source.android.com/setup/build/gsi
GSIs are not the most stable and many users prove they are unable to read. they just want ready stuff. with this project that is not the case. if you skip the instructions/F.A.Qs and notes, dont bother installing this project as you probably wont be able to get it running.
This is a fully featured VENDOR and KERNEL designed for this device to support project treble, it is based on other Exynos 7885 Vendors and modified to support our devices, i have also added few patches and fixes to this vendor to get the best possible experience
The vendor is pretty much bugles, therefore any bugs you face, Report them to the appropriate Threads of the GSI you installed or github issues section, as those are not mine to fix i only provide the vendor and kernel that allows GSIs to run on.
- VENDOR FEATURES:
Wi-Fi & Hotspot
Telephony & Ril (Mobile Data, Calls, SMS, MMS)
NFC
Camera
Bluetooth
GPS
Fingerprint
All Sensors
- STEPS FOR INSTALLING TREBLE VENDOR:
Make Sure You Treble Your Bevice By This Guide here
Boot into Twrp recovery
Wipe System, Data, Dalvik and Vendor.
Select Vendor_Dumpster.zip
- STEPS FOR INSTALLING GSIs:
Download the desired GSI (it MUST be A-only_arm64 Variant)
unpack it if it wasn't in .IMG format
Go to TWRP , Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
Reboot to TWRP Recovery
- STEPS FOR INSTALLING GAPPS
Download the appropriate opengapps
Go to TWRP , Install
Pick your OpenGapps.zip
Reboot to System
- KNOWN BUGS:
Bluetooth calls are broken
Credits:
- @ananjaser1211 for his contribution
- @TaifAljaloo for testing
Downloads. Changelogs , F.A.Qs below
XDA:DevDB Information
Project Treble, Vendor for the Samsung Galaxy A8 (2018)
Kernel Source
Contributors
prashantp01
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Current Stable Version: v1
Created 2019-05-17
Last Updated 2019-05-17

{
"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"
}
Come hang with us on our chat : Telegram
----------------------------------------------------------------
Treble Pie Vendor Dumpster V1.0 [LATEST]
Treble folder : Gdrive
Recommended GSI : Gdrive
Generic System Image (list) : Github
---------------------------------------------------------------
Bugs :
1- some users might face SDCard issues
If you did , back up its data and format it in GSI.
2- If you face "Error 70: Insufficient storage space available in the system partition" while flashing Gapps
If you get do this : Wipe > Advanced Wipe > select system > Repair or Change File System > Resize File System
Go back and flash Gapps
V1.0
-initial release

F.A.Q
For more details related to this project, read our dedicated Wiki page here.
Q : Do i need to format internal storage ?
A : No
Q : Can i use the Treble recovery for normal ROMs ?
A : Yes, it is preferred especially when making backups. just be sure to wipe vendor when switching to non treble roms
Q : What Camera is recommended ?
A : Footej and open camera works the best
Q : Can i flash any GSIs ?
A : No, only A-ONLY_ARM64 Are supported
Q : Can i flash any sGSIs ?
A : No unless they match the Arch above

reserved

I just flashed the Lineage OS v16 GSI with this vendor and found no problems other than no network bars (as mentioned above) and there were no problems with the camera and fingerprint. I will notify you later if there is a bugs
Thanks for your hard work ?

Sweet! I'm gonna be up all night!

This is fantastic. The boot time has decreased immensely.
Finally got aosp extended 6.5 to boot. Well i didn't, you did.
What a difference. Ressurection Remix as well. The 9.0. That one seems a bit iffy no matter.
I am noticing a different mobile data icon. It'll say 4g+
Not too far from normal full usage. Thank you.

mindlery said:
This is fantastic. The boot time has decreased immensely.
Finally got aosp extended 6.5 to boot. Well i didn't, you did.
What a difference. Ressurection Remix as well. The 9.0. That one seems a bit iffy no matter.
I am noticing a different mobile data icon. It'll say 4g+
Not too far from normal full usage. Thank you.
Click to expand...
Click to collapse
Where you able to get gapps installed it always failed for me.
This has happened on most of these roms

Yes i was. My method is a bit harsh though. I am a fan of internal destruction
So for the gsi, i wipe everything including internal. Then i reboot to recovery. Swipe to allow modifications. Install vendor. Install system image. Then reboot recovery flash fix boot. I almost never bother with gapps anymore until it boots fully. Then i'll immediately go into recovery and flash gapps then reboot of course.
I got sick of errors myself. If you find one you like or want to go back to then it may be worth trying for that perfect install. Almost there.
---------- Post added at 04:33 AM ---------- Previous post was at 04:20 AM ----------
https://downloads.aospextended.com/treble_gsi
Before only 6.1 worked. Now 6.5 starts in a minute or so. 6.3 boot looped before so i am going to see what happens now.

mindlery said:
Yes i was. My method is a bit harsh though. I am a fan of internal destruction
So for the gsi, i wipe everything including internal. Then i reboot to recovery. Swipe to allow modifications. Install vendor. Install system image. Then reboot recovery flash fix boot. I almost never bother with gapps anymore until it boots fully. Then i'll immediately go into recovery and flash gapps then reboot of course.
I got sick of errors myself. If you find one you like or want to go back to then it may be worth trying for that perfect install. Almost there.
---------- Post added at 04:33 AM ---------- Previous post was at 04:20 AM ----------
https://downloads.aospextended.com/treble_gsi
Before only 6.1 worked. Now 6.5 starts in a minute or so. 6.3 boot looped before so i am going to see what happens now.
Click to expand...
Click to collapse
I'm using ion- v1.0.c 9.0 without any issues.
For some reason on the newer gsi roms you can't get gapps to install.
ion rom gapps are included.

mchlbenner said:
I'm using ion- v1.0.c 9.0 without any issues.
For some reason on the newer gsi roms you can't get gapps to install.
ion rom gapps are included.
Click to expand...
Click to collapse
I have never heard of that. Of course I am downloading but is there any information about it besides a file on android file host?

mindlery said:
I have never heard of that. Of course I am downloading but is there any information about it besides a file on android file host?
Click to expand...
Click to collapse
I had not heard of it also but it seems to work without issue.
Only thing on screenshot you have edit where photo is being stored.

Does this allow me to use system-as-root gsis? Since android 9 treble implementation is supposed to be system as root even on aonly, I would guess so, but I couldn't get my device to boot with one yet.

Weird, I can't even get aospextended to work... It just bootloops without bootanimation.
Edit: nvm, I got it to work, but I had to flash the oreo vendor first, and then the pie vendor.
Edit2: fingerprint doesn't seem to work even with fp patch (it's weird, it registers the fingerprint, and even validates it, but it does nothing on the lockscreen)
Edit3: restart fixed it

I have a few questions
I used to flash the usual custom roms so is this is the same thing i mean that if i can use it to flash custom roms
And which roms exactly working perfectly on this device without any issues
Also should i root my phone before installing it or what exactly should i do
Is it stable and doesn't have any problems or will i face some problems while im using it

For some reason on aosp extended gsi the phone will stay stuck at the charging screen (gray one without percentage) when charging when its turned off, disconnecting the cable doesn't do anything, it stays stuck on this screen till i force reboot

CoinKiller said:
For some reason on aosp extended gsi the phone will stay stuck at the charging screen (gray one without percentage) when charging when its turned off, disconnecting the cable doesn't do anything, it stays stuck on this screen till i force reboot
Click to expand...
Click to collapse
Did you install GSI_Fix_boot.zip?

So I want to install Google phone but I cannot get it to work. Can you give me an alternative ?

If I want to install a different GSI I follow the steps again (install vendor, flash GSI, flash boot fix and fixes if needed) or just wipe system, data, cache and flash the new image+ boot fix

slawdos said:
Did you install GSI_Fix_boot.zip?
Click to expand...
Click to collapse
Yes but i had to format /vendor after installing that zip (it wasnt the zip fault!), Didn't that get installed in /system?

[ROM][OFFICIAL][kirin][11] LineageOS 18.1

{
"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 is a free, community built, aftermarket firmware distribution of Android 11, 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. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
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.
Instructions :
https://wiki.lineageos.org/devices/kirin
Downloads :
https://download.lineageos.org/kirin
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 /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (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. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
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:

Thanks for the ROM!
Just installed the 20201003 build and it flawlessly so far.
Just a quick question, I can't seem to delete the search widget in the default launcher (quickstep), are there any way to delete it?
Also there are no "Advanced restart" option anymore, is there a way to have a reboot to recovery/bootloader entry in the new Android 11 power menu?

diyod said:
Thanks for the ROM!
Just installed the 20201003 build and it flawlessly so far.
Just a quick question, I can't seem to delete the search widget in the default launcher (quickstep), are there any way to delete it?
Also there are no "Advanced restart" option anymore, is there a way to have a reboot to recovery/bootloader entry in the new Android 11 power menu?
Click to expand...
Click to collapse
>Just a quick question, I can't seem to delete the search widget in the default launcher (quickstep), are there any way to delete it?
Launcher customizations aren't brought up yet thus search bar is stuck there for time being.
>Also there are no "Advanced restart" option anymore, is there a way to have a reboot to recovery/bootloader entry in the new Android 11 power menu?
Power menu additions aren't brought up either.

LuK1337 said:
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
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.
What's not working :
WFD
Instructions :
Download the latest build and gapps
Reboot to recovery
Flash the latest build and gapps
Reboot
Downloads :
Builds :
https://www.androidfilehost.com/?w=files&flid=318024
http://downloads.codefi.re/jdcteam/luk/lineage-18_0/kirin
https://sourceforge.net/projects/luk-lineageos/files/kirin/lineage-18.0
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 /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (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. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
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:
XDA:DevDB Information
[ROM][UNOFFICIAL][kirin][11] LineageOS 18.0, ROM for the Sony Xperia 10
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: Windows 8 Mobile
Based On: LineageOS
Version Information
Status: Testing
Created 2020-09-28
Last Updated 2020-09-28
Click to expand...
Click to collapse
Hello. Does the rom have signiture spoofing?

Gapps Not working
LineageOS version: 18.0
LineageOS Download url: First one I can`t submit the post with the link, this is the version: lineage-18.0-20201016_012612-UNOFFICIAL-kirin.zip
Gapps version: Here is where the issue occurs. None of the Gapps found here, and in first pages in Google by searching "Lineage OS 18 gapps" or either "Android 11 gapps" ever worked on Lineage OS 18.
I flashed with TWRP (I tried also with the Lineage OS recovery but I know that Gapps are not signed and return error from there) Immediately after a clean installation of Lineage OS 18 and wipe, All Open Gapps versions found, BitApps, NikApps and others came with error code 20, error code 70 (I tried with resizing the partition, switching slots, did not work) or fatal error. I managed to flash some of them successfully but they never showed up after turning on the phone.
Everything else except Gapps working as expected until now.
The same kernel is used as for Lineage OS 17.1 that was previously used with a working OpenGapps flash.
The phone version is Xperia 10 I4113, no modifications were made, just Unlocked bootloader, TWRP recovery, Flashed Lineage OS 18 and Flashed all versions of Gapps with no success.
In case you`ve tested and got Gapps successfully after installing the rom share this version with us so we can flash it and use the ROM for daily routines by continue testing.
Thanks in advance.
Regards.

dian1994 said:
LineageOS version: 18.0
LineageOS Download url: First one I can`t submit the post with the link, this is the version: lineage-18.0-20201016_012612-UNOFFICIAL-kirin.zip
Gapps version: Here is where the issue occurs. None of the Gapps found here, and in first pages in Google by searching "Lineage OS 18 gapps" or either "Android 11 gapps" ever worked on Lineage OS 18.
I flashed with TWRP (I tried also with the Lineage OS recovery but I know that Gapps are not signed and return error from there) Immediately after a clean installation of Lineage OS 18 and wipe, All Open Gapps versions found, BitApps, NikApps and others came with error code 20, error code 70 (I tried with resizing the partition, switching slots, did not work) or fatal error. I managed to flash some of them successfully but they never showed up after turning on the phone.
Everything else except Gapps working as expected until now.
The same kernel is used as for Lineage OS 17.1 that was previously used with a working OpenGapps flash.
The phone version is Xperia 10 I4113, no modifications were made, just Unlocked bootloader, TWRP recovery, Flashed Lineage OS 18 and Flashed all versions of Gapps with no success.
In case you`ve tested and got Gapps successfully after installing the rom share this version with us so we can flash it and use the ROM for daily routines by continue testing.
Thanks in advance.
Regards.
Click to expand...
Click to collapse
Did you actually reboot recovery between installing rom and gapps?

LuK1337 said:
Did you actually reboot recovery between installing rom and gapps?
Click to expand...
Click to collapse
Yes, I did that multiple times during all night long with many different Gapps versions and reboots of the recovery between ROM flashing and Gapps.
If it is possible to provide a Download URL with Gapps version that has been tested on your end by this way after ROM flashes and it works that will be highly appreciated.
I`ve switched back in 17.1 twice by installing Gapps without issues.
I am currently using the ROM without Gapps so I can wipe and trigger a new flash of Gapps from the recovery, but none of the versions I already tried ever showing up or complete installation.
Thank you for your time and support.

dian1994 said:
Yes, I did that multiple times during all night long with many different Gapps versions and reboots of the recovery between ROM flashing and Gapps.
If it is possible to provide a Download URL with Gapps version that has been tested on your end by this way after ROM flashes and it works that will be highly appreciated.
I`ve switched back in 17.1 twice by installing Gapps without issues.
I am currently using the ROM without Gapps so I can wipe and trigger a new flash of Gapps from the recovery, but none of the versions I already tried ever showing up or complete installation.
Thank you for your time and support.
Click to expand...
Click to collapse
You tried fastboot booting twrp and installing gapps there?

LuK1337 said:
You tried fastboot booting twrp and installing gapps there?
Click to expand...
Click to collapse
Yes, exactly I am using adb to flash the ROM first, then flash TWRP recovery via fastboot and then flashing gapps via adb from TWRP recovery again by repeating this order in every gapps version which does not take effect or return error 20 or error 70 (open gapps) and fatal error for NikApps.
If it is important I am using MacOS, but we tried from Windows ADB once without much of success.

dian1994 said:
Yes, exactly I am using adb to flash the ROM first, then flash TWRP recovery via fastboot and then flashing gapps via adb from TWRP recovery again by repeating this order in every gapps version which does not take effect or return error 20 or error 70 (open gapps) and fatal error for NikApps.
If it is important I am using MacOS, but we tried from Windows ADB once without much of success.
Click to expand...
Click to collapse
What fatal error are you getting on nikgapps?

LuK1337 said:
What fatal error are you getting on nikgapps?
Click to expand...
Click to collapse
Currently I can not remember if BitApps version or NikApps returned the error, but the error said that this version is not compatible and the flash just stopped with general error in TWRP recovery log. One of them returned the error, the other one has completed but nothing has showed up after booting to the OS.
I am in the office right now and did not get the cable but if you have suggestions on specific versions of gapps that you think are working, I will try to flash each one by following your instructions tomorrow night after work and provide you with feedback of screenshot of TWRP recovery log for every single gapps package.
If there is a version which you know that can go thru the security signing check from Lineage recovery I can try to flash it from the sdcard right away.

dian1994 said:
Currently I can not remember if BitApps version or NikApps returned the error, but the error said that this version is not compatible and the flash just stopped with general error in TWRP recovery log. One of them returned the error, the other one has completed but nothing has showed up after booting to the OS.
I am in the office right now and did not get the cable but if you have suggestions on specific versions of gapps that you think are working, I will try to flash each one by following your instructions tomorrow night after work and provide you with feedback of screenshot of TWRP recovery log for every single gapps package.
If there is a version which you know that can go thru the security signing check from Lineage recovery I can try to flash it from the sdcard right away.
Click to expand...
Click to collapse
NikGapps-omni-arm64-11-20201010-signed.zip seems to install properly here.
>If there is a version which you know that can go thru the security signing check from Lineage recovery I can try to flash it from the sdcard right away
Not yet, I just ported the patch that allows for that btw.

LuK1337 said:
NikGapps-omni-arm64-11-20201010-signed.zip seems to install properly here.
>If there is a version which you know that can go thru the security signing check from Lineage recovery I can try to flash it from the sdcard right away
Not yet, I just ported the patch that allows for that btw.
Click to expand...
Click to collapse
Thanks I will give a try and let you know about the result.

LuK1337 said:
NikGapps-omni-arm64-11-20201010-signed.zip seems to install properly here.
>If there is a version which you know that can go thru the security signing check from Lineage recovery I can try to flash it from the sdcard right away
Not yet, I just ported the patch that allows for that btw.
Click to expand...
Click to collapse
I just want to let you know that this version worked as expected. I have no explanation but probably I did something wrong with the slots. Thanks. I will keep you posted in case of a bug found. However Gapps required TWRP, Lineage recovery does not install gapps due Signing request error.

Bugs Report
I would like to come up with a short report of what did not work with the rom for a few weeks of using.
Actually almost everything works except two main functions.
1. Wi - Fi HotSpot do not work. It shows up but when you connect from another device there is no internet connection. 4G has been established on LineageOS but do not reach the external device via Wi - Fi hot spot.
2. Google accuracy location service does not work, GPS works only when you stay outside. I do not know if it is related to GApps or Rom backend. If you run an app that requires location services will run only outside which is a quite too bad.
That's it for now. Hope it helps.

dian1994 said:
I would like to come up with a short report of what did not work with the rom for a few weeks of using.
Actually almost everything works except two main functions.
1. Wi - Fi HotSpot do not work. It shows up but when you connect from another device there is no internet connection. 4G has been established on LineageOS but do not reach the external device via Wi - Fi hot spot.
2. Google accuracy location service does not work, GPS works only when you stay outside. I do not know if it is related to GApps or Rom backend. If you run an app that requires location services will run only outside which is a quite too bad.
That's it for now. Hope it helps.
Click to expand...
Click to collapse
1. Consider not being over 5 builds behind.

LuK1337 said:
1. Consider not being over 5 builds behind.
Click to expand...
Click to collapse
You mean that Wi-Fi hot spot issue has been fixed already in a recent build?

dian1994 said:
You mean that Wi-Fi hot spot issue has been fixed already in a recent build?
Click to expand...
Click to collapse
Go ahead and try.

LuK1337 said:
Go ahead and try.
Click to expand...
Click to collapse
Gotcha. Thanks.

has anyone had any luck getting magisk 21.1 to work with this rom and twrp yet?
im going round in circles trying to root after updating. i can install magisk from twrp, but i end up in a bootloop, then installing the bootloop fix from twrp wipes magisk and breaks root.
i know 21.1 is a beta and likely doesnt support sony phones yet, but someone might have a fix.
EDIT: I have root working now. Anyone having trouble, DONT install twrp to ramdisk. just leave the lineageOS recovery in place and use fastboot on a pc to boot twrp when you need it.
I did the following:
1. fresh stock firmware via newflash
2.flash sony software binaries for a11
3. fastboot boot twrp.img
4.swap to partition b
5. power off
6. fastboot boot twrp.img (check you are booted to partition b)
7. flash lineageos 18
8.reboot select partition a and POWER OFF
9. fastboot boot twrp.img
10. check partition is a
11. flash copy partition.zip
12. flash magisk 21.1.zip
13. flash nikGapps basic for a11
14. reboot system
15. install magiskmanager 8.0.3.apk
16. reboot
17. update your apps on playstore.
18. PROFIT.
lineage os18 rooted on my xperia 10.

born2bkilled said:
I did the following:
1. fresh stock firmware via newflash
2.flash sony software binaries for a11
3. fastboot boot twrp.img
4.swap to partition b
5. power off
6. fastboot boot twrp.img (check you are booted to partition b)
7. flash lineageos 18
8.reboot select partition a and POWER OFF
9. fastboot boot twrp.img
10. check partition is a
11. flash copy partition.zip
12. flash magisk 21.1.zip
13. flash nikGapps basic for a11
14. reboot system
15. install magiskmanager 8.0.3.apk
16. reboot
17. update your apps on playstore.
18. PROFIT.
lineage os18 rooted on my xperia 10.
Click to expand...
Click to collapse
Which package is it you use?
If I flash the Gapps, Lineage can't boot into system and asks for a factory reset.
I'm following the steps exactly as they're described.
Am I missing something?

Just installed it. Was some effort, coming from SailfishX.
Had to install Sony binaries first, then get the latest TWRP (old one gave me errors, the provided one in this post as well). After that installed NikGapps (Gapps or open Gapps do not work I think). Was up till 3am
Got some problems though:
Cannot enable wifi.
Does not detect cellular network at all?
GUI stopped working error at every boot (works after clicking at away).
Settings stopped responding when I click network.
Fingerprint does not seem to be working? Do I need a specifiek Gapps version for that?
Can you tell me what the camera mod does? I do not see any difference?
Thanks for the effort this far!
Edit: I seem to be missing the firmware alltogether. Any ideas how to fix this?

[ROM][OFFICIAL][I003][obiwan] LineageOS 18.1

{
"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 is a free, community built, aftermarket firmware distribution of Android 11, 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. LineageOS does still include various proprietary hardware-specific code.
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.
Instructions :
Download the latest recovery image and rom zip
Boot to bootloader
fastboot flash recovery lineage-recovery.img
Boot to recovery
Format data
Sideload LineageOS zip
Optionally flash any addons:
Advanced > Reboot to recovery
Sideload the addons
Reboot
See https://wiki.lineageos.org/devices/obiwan/install for more detailed instructions
Downloads :
Official buids
Archived unofficial builds: sourceforge
Reporting Bugs
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 /sys/fs/pstore/* (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.
Known Issues
Downgrading to an Android 10 based rom (stock included) might not work. To be safe backup persist.img to restore when downgrading.
Depending on your carrier, you may need to force a 4G/5G-only connection for VoLTE to register (from the *#*#4636#*#* menu for example)
(minor) Touchscreen may fail to initialize in Lineage Recovery
How do i...
Change the screen refresh rate?
Settings > Display > Advanced > Minimum refresh rate
Contributors
luca020400
aleasto
OrdenKrieger
The LineageOS Team
Source Code: https://github.com/LineageOS
ROM OS Version: Android 11

These builds will include a frankensteined VNDK 29-30 vendor until we get stock Android 11
You can dirty flash over my UNOFFICIAL Lineage 17.1 builds

Please fix VOLTE properly.

aleasto said:
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
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.
Instructions :
Update to the latest stock rom
Download the latest recovery image and rom zip
Boot to fastboot
Flash recovery
Boot to recovery
Format data
Flash the latest build
Optionally, reboot to recovery and flash any addons
Reboot
Downloads :
Builds: Google drive folder
Reporting Bugs
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 /sys/fs/pstore/* (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.
Known Issues
Fingerprint sensor is not working
(minor) Touchscreen may fail to initialize in Lineage Recovery
How do i...
Change the screen refresh rate?
Drop down the notification shade
Tap the Pencil icon to edit Quick Settings
Scroll to the bottom.
Drag the Refresh rate tile to the top
Make VoLTE work?
This device seems to fail to register to VoLTE unless you force a 4G or 5G only connection.
To workaround that:
Navigate to your SIM options
Advanced
Preferred network type
Select "4G only (enables VoLTE)" or "5G/4G only (enables VoLTE)"
Contributors
luca020400
aleasto
OdenKrieger
The LineageOS Team
Source Code: https://github.com/LineageOS
ROM OS Version: Android 11
Click to expand...
Click to collapse

Thank you very much for your efforts,bro.
one question please, if i have a custom TWRP, do i still need to flash this lineage recovery img before flashing the rom ?

amr elfiky said:
Thank you very much for your efforts,bro.
one question please, if i have a custom TWRP, do i still need to flash this lineage recovery img before flashing the rom ?
Click to expand...
Click to collapse
TWRP should work but I cannot guarantee it does and will (and that's one of the main reasons Lineage makes its own recovery)

amr elfiky said:
Thank you very much for your efforts,bro.
one question please, if i have a custom TWRP, do i still need to flash this lineage recovery img before flashing the rom ?
Click to expand...
Click to collapse
No, TWRP works just fine.

bs3pro said:
You should fix VOLTE properly.
Click to expand...
Click to collapse
aleasto said:
TWRP should work but I cannot guarantee it does and will (and that's one of the main reasons Lineage makes its own recovery)
Click to expand...
Click to collapse
Does the rom already have Gapps.

[email protected] said:
Does the rom already have Gapps.
Click to expand...
Click to collapse
It doesn't. I currently suggest trying NikGapps "core". Opengapps test builds for 11 are very broken still.

bs3pro said:
You should fix VOLTE properly.
Click to expand...
Click to collapse
?

Hi
Will apps like Gpay and other banking apps work after installing this rom?
Thanks for your efforts

darudedudedocta said:
Hi
Will apps like Gpay and other banking apps work after installing this rom?
Thanks for your efforts
Click to expand...
Click to collapse
Gpay, NO.

After trying lineage os 17.1 and omnirom I installed this ROM and have decided to stay on it. ROM is smooth and don't have much issues. Minor issue noted is lack of haptic feedback on navigation gestures. Just for the sake of reporting geekbench scores (950/2850) seems to be bit low than stock, while los 17.1 and omni had stock scores(970/3300).
Thanks a lot aleasto for all the hard work and providing us with android 11 early.
Also would like to ask - Is there a way to hide the status bar in android 11? Earlier on android 10 it was very easy to do with adb commands, seems these commands were removed it android 11.

bs3pro said:
Please fix VOLTE properly.
Click to expand...
Click to collapse
hi rich

@aleasto Ran into a major problem, Need your help. So after trying 18.1 for sometime decided to go back to 17.1. So flashed Asus raw firmware to return firmware to stock before flashing 17.1 again. But the phone got stuck in bootloop, tried several versions of raw firmware , all flashed fine but was stuck on bootloop. Was able to get to recovery so tried 17.1 and omni too only to bootloop. After this was able to boot again by flashing 18.1 .
The problem is now only 18.1 ROM works on my ww rog3 , all other ROMs are bootlooping even flashing the Asus raw firmware is resulting in bootloop.
please advice. Is 18.1 making any change to partitions? Even if it does flashing raw firmware must restore it right?

tuxing said:
@aleasto Ran into a major problem, Need your help. So after trying 18.1 for sometime decided to go back to 17.1. So flashed Asus raw firmware to return firmware to stock before flashing 17.1 again. But the phone got stuck in bootloop, tried several versions of raw firmware , all flashed fine but was stuck on bootloop. Was able to get to recovery so tried 17.1 and omni too only to bootloop. After this was able to boot again by flashing 18.1 .
The problem is now only 18.1 ROM works on my ww rog3 , all other ROMs are bootlooping even flashing the Asus raw firmware is resulting in bootloop.
please advice. Is 18.1 making any change to partitions? Even if it does flashing raw firmware must restore it right?
Click to expand...
Click to collapse
"bootloop" means you get boot animation?
Are you even formatting data?

Hi guys does the back lightning system works with this room or there's any way of making it work or install the armory crate app? Thank you

peixeskim said:
Hi guys does the back lightning system works with this room or there's any way of making it work or install the armory crate app? Thank you
Click to expand...
Click to collapse
Not currently

aleasto said:
"bootloop" means you get boot animation?
Are you even formatting data?
Click to expand...
Click to collapse
The phone keeps restarting at the republic of gamers screen. If i turn it off and restart it stays at fastboot screen.
Yes before trying each ROM install, I had formatted data, Except while flashing stock raw firmware which seems to be formatting everything.

bencozzy said:
Did you have security set up like a pin code or password? Did you remove it before flashing stock firmware? Did you format data after completing the stock firmware flash in the phones recovery?
Click to expand...
Click to collapse
No security (pin or password) was setup. Yes tried formating data from stock recovery after flashing stock raw firmware from PC. But didn't help.

[ROM][OFFICIAL][sunfish] LineageOS 18.1

{
"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 is a free, community built, aftermarket firmware distribution of Android 11, 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. LineageOS does still include various proprietary hardware-specific code.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Notes
Before the initial installation, please make sure your Pixel 4a has already been updated to Android 11 official firmware so that the recovery can function correctly.
This ROM comes with latest firmware bundled, so after the initial flash you don't need to worry about updating firmware manually.
This ROM comes with source-built kernel and modules
eSIM functions without GAPPS, but to manage (add / erase) eSIMs you will need to have GAPPS installed
Installation
Update your Pixel 4a to official Android 11
Download the latest boot.img and rom zip
Boot to bootloader
fastboot flash boot boot.img
Boot to recovery
Format data
Flash LineageOS zip
Optionally flash any addons:
Advanced > Reboot to recovery
Flash the addons
Reboot
Updating
Boot to recovery
Flash LineageOS zip
Flash the same addons you had previously installed:
Advanced > Reboot to recovery
Flash the addons
Reboot
Downloads
Official: https://download.lineageos.org/sunfish
Reporting bugs
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 /sys/fs/pstore/* (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.
Known Issues
On the first boot, you might be presented the message "SIM Manager has crashed". You can safely ignore it.
Source Code
LineageOS
A free and open-source operating system for various devices, based on the Android mobile platform. This is a mirror of https://review.lineageos.org/ - LineageOS
github.com

PeterCxy said:
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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. LineageOS does still include various proprietary hardware-specific code.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Notes
Before the initial installation, please make sure your Pixel 4a has already been updated to Android 11 official firmware so that the recovery can function correctly.
This ROM comes with latest firmware bundled, so after the initial flash you don't need to worry about updating firmware manually.
This ROM comes with source-built kernel and modules
eSIM functions without GAPPS, but to manage (add / erase) eSIMs you will need to have GAPPS installed
Installation
Update your Pixel 4a to official Android 11
Download the latest boot.img and rom zip
Boot to bootloader
fastboot flash boot boot.img
Boot to recovery
Format data
Flash LineageOS zip
Optionally flash any addons:
Advanced > Reboot to recovery
Flash the addons
Reboot
Updating
Boot to recovery
Flash LineageOS zip
Flash the same addons you had previously installed:
Advanced > Reboot to recovery
Flash the addons
Reboot
Downloads
Official: https://download.lineageos.org/sunfish
Reporting bugs
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 /sys/fs/pstore/* (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.
Known Issues
On the first boot, you might be presented the message "SIM Manager has crashed". You can safely ignore it.
Source Code
LineageOS
A free and open-source operating system for various devices, based on the Android mobile platform. This is a mirror of https://review.lineageos.org/ - LineageOS
github.com
Click to expand...
Click to collapse
Using it now... ROM is stable, smooth and fast... as of now...
Initially, I couldn't call or text but after resetting the apn and switching it once to 2G and reverting back to 4G should fix that...( Jio users India).
Used nikgapps
https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-R/30-Jan-2021/NikGapps-core-arm64-11-20210130-signed.zip/download

PeterCxy said:
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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. LineageOS does still include various proprietary hardware-specific code.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Notes
Before the initial installation, please make sure your Pixel 4a has already been updated to Android 11 official firmware so that the recovery can function correctly.
This ROM comes with latest firmware bundled, so after the initial flash you don't need to worry about updating firmware manually.
This ROM comes with source-built kernel and modules
eSIM functions without GAPPS, but to manage (add / erase) eSIMs you will need to have GAPPS installed
Installation
Update your Pixel 4a to official Android 11
Download the latest boot.img and rom zip
Boot to bootloader
fastboot flash boot boot.img
Boot to recovery
Format data
Flash LineageOS zip
Optionally flash any addons:
Advanced > Reboot to recovery
Flash the addons
Reboot
Updating
Boot to recovery
Flash LineageOS zip
Flash the same addons you had previously installed:
Advanced > Reboot to recovery
Flash the addons
Reboot
Downloads
Official: https://download.lineageos.org/sunfish
Reporting bugs
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 /sys/fs/pstore/* (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.
Known Issues
On the first boot, you might be presented the message "SIM Manager has crashed". You can safely ignore it.
Source Code
LineageOS
A free and open-source operating system for various devices, based on the Android mobile platform. This is a mirror of https://review.lineageos.org/ - LineageOS
github.com
Click to expand...
Click to collapse
Any way to use banking apps bro... (Like in descendent without magisk)

Raj Pandiyan said:
Any way to use banking apps bro... (Like in descendent without magisk)
Click to expand...
Click to collapse
I'm sorry but LineageOS does not provide any officially-supported way to bypass SafetyNet restrictions. Please look into third-party solutions for that.

I happened to install the last unofficial LOS (lineage-18.1-20210308) on a new phone an hour before this was released. I have everything setup and installed, safetynet passes etc etc, is it worth upgrading to this? Are there any big differences?
Also, is it possible to use twrp with this or lineage-18.1-20210308?
Thanks.

Fung-i said:
I happened to install the last unofficial LOS (lineage-18.1-20210308) on a new phone an hour before this was released. I have everything setup and installed, safetynet passes etc etc, is it worth upgrading to this? Are there any big differences?
Also, is it possible to use twrp with this or lineage-18.1-20210308?
Thanks.
Click to expand...
Click to collapse
The unofficial build will still be updated, but if you don't need microG it might be a better idea to switch to the official build for more timely updates and official guarantees. Of course, to switch to the official build, you have to wipe all data and start over.
I have no experience with TWRP on Pixel 4a.

has anyone had issues flashing rom using adb sideload and it failed , when loading recovery after reboot from data wipe , has failed mount emulated/0/
will try again and post imgs , have been able to flash unofficial and any other roms besides grapheneos, same issue upon flashing rom ,on latest stock android 11 unlocked bootloader

miko12312 said:
has anyone had issues flashing rom using adb sideload and it failed , when loading recovery after reboot from data wipe , has failed mount emulated/0/
will try again and post imgs , have been able to flash unofficial and any other roms besides grapheneos, same issue upon flashing rom ,on latest stock android 11 unlocked bootloader
Click to expand...
Click to collapse
No problem here, flashed with mindthegapps.

any idea why nikogapps stock package doesn't work (device does not boot ) but Core package does?

PeterCxy said:
The unofficial build will still be updated, but if you don't need microG it might be a better idea to switch to the official build for more timely updates and official guarantees. Of course, to switch to the official build, you have to wipe all data and start over.
I have no experience with TWRP on Pixel 4a.
Click to expand...
Click to collapse
hi,
first of all, i want to thank you very much for your hard work on this rom. I have installed it yesterday and it runs perfectly showing almost 50% battery life increase and much better performance comparing to stock. I just noticed one strange thing: I can not monitor the kernel wakelocks using BBS as well as GSAM Battery monitor utilities. Both got root permission but don't show Kernel Wakelocks at all. Do you have any idea what could be the reason? I can access the /sys/kernel/debug fs, but don't see anything helpful in logcat...

Does the "Show battery percentage in status bar" works for anyone?

HeartWood said:
Does the "Show battery percentage in status bar" works for anyone?
Click to expand...
Click to collapse
you should be able to configure the battery percentage using settings > system > status bar

wawap68 said:
any idea why nikogapps stock package doesn't work (device does not boot ) but Core package does?
Click to expand...
Click to collapse
It replaces many of LOS stock apps and stuff... So download omni variant, extract and edit nikgapps config file ( It is self understandable when you open and read it.. basically change variable from 1 to 0 which affect LOS framework and default apps like dialer etc...)... Again zip them and now sideload... It should work fine...

Got everything working passing safteynet

miko12312 said:
Got everything working passing safteynet
Click to expand...
Click to collapse
please tell us what method worked for you!

mma1162 said:
hi,
first of all, i want to thank you very much for your hard work on this rom. I have installed it yesterday and it runs perfectly showing almost 50% battery life increase and much better performance comparing to stock. I just noticed one strange thing: I can not monitor the kernel wakelocks using BBS as well as GSAM Battery monitor utilities. Both got root permission but don't show Kernel Wakelocks at all. Do you have any idea what could be the reason? I can access the /sys/kernel/debug fs, but don't see anything helpful in logcat...
Click to expand...
Click to collapse
fugured it out. It was the Magisk Fault. After reconfiguring BBS using ADB everything worked fine.
BTW the battery life is gorgeous comparing to stock ))

claviger-pc said:
please tell us what method worked for you
Click to expand...
Click to collapse
claviger-pc said:
please tell us what method worked for you!
Click to expand...
Click to collapse
1. extract the boot from LOS payload.bin
2. install Magisk 22 by patching the extracted boot image
3. hide the magisk from: google play store, play services, gpay, clear data for all these apps.
4. install magisk module safetynet-fix-v1.1.1.zip
5. reboot

Firstly, I want to thank the Lineage team and those who accompany our device.
I have been using this firmware since April 1 and have not seen any particular problems. However, it lacks some features that were in the RR 8 - a charging indicator when displaying a textual charge level, an extended reboot menu (recovery and bootloader). Or maybe I didn't find it =)
And as far as I understand it is now impossible to update LOS 18.1 via OTA, but only through recovery?

droncheg said:
Firstly, I want to thank the Lineage team and those who accompany our device.
I have been using this firmware since April 1 and have not seen any particular problems. However, it lacks some features that were in the RR 8 - a charging indicator when displaying a textual charge level, an extended reboot menu (recovery and bootloader). Or maybe I didn't find it =)
And as far as I understand it is now impossible to update LOS 18.1 via OTA, but only through recovery?
Click to expand...
Click to collapse
Advanced restart option is there.

Anyone coming off the unofficial build... tips? I nuked everything: went back to stock, flashed Lineage recovery, wiped/data reset, flashed zip, rebooted to recovery, then flashed MindTheGapps as OpenGapps won't install due to a version mismatch. Been stuck on the boot screen for eons.
Went back and repeated the process only to still be stuck on boot screen. Is there any log I can record/provide to figure out what's going on?