[ROM][OFFICIAL][11] LineageOS 18.1 for Galaxy Note10/Note10+/Note10+ 5G Exynos - Samsung Galaxy Note 10+ ROMs, Kernels, Recoveries,

[ROM][OFFICIAL][11] LineageOS 18.1 for Galaxy Note10/Note10+/Note10+ 5G Exynos - Samsung Galaxy Note 10+ ROMs, Kernels, Recoveries,

{
"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:
Follow the instructions on the wiki page for your device https://wiki.lineageos.org/devices/#samsung
Only the provided lineage recovery will be supported, using TWRP might result in a possible data loss!
Note: You may use Odin instead of Heimdall, for this you will need to rename the recovery image to recovery.img and pack it into a tar archive.
Downloads:
Builds: https://download.lineageos.org
GApps: https://wiki.lineageos.org/gapps.html
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. 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:
Support
Telegram group
Contributors
Linux4
Source Code: https://github.com/LineageOS
Kernel source: https://github.com/LineageOS/android_kernel_samsung_exynos9820

reserved

reserved

What is different between this build and your previous one ?

Big guy, can you come up with a LineageOS that d2q can use, d2q users feel distressed, and there is no rom available

Vishnarov said:
What is different between this build and your previous one ?
Click to expand...
Click to collapse
Read the thread's title ... It's official now.
[email protected] said:
Big guy, can you come up with a LineageOS that d2q can use, d2q users feel distressed, and there is no rom available
Click to expand...
Click to collapse
No, sorry hardware is too different.

builds have been removed from the lineage os website?

Enddo said:
builds have been removed from the lineage os website?
Click to expand...
Click to collapse
Yes, see this for the reason
This affected all devices so builds of last few days were pulled and sadly we had only that one build yet
There will be new ones next week

Does the build support hardware encryption or software encryption?

You should put what models this is for as to avoid confusion

just flashed the recovery image via heimdal (got recovery upload success message), but when I try to boot into recovery mode (or even just boot into Android now) I get pushed into download mode with a 'dt load fail' message at the top
says dt entry not found
load kernel could not do normal boot
error verifying vbmeta image - hash mismatch

Enddo said:
just flashed the recovery image via heimdal (got recovery upload success message), but when I try to boot into recovery mode (or even just boot into Android now) I get pushed into download mode with a 'dt load fail' message at the top
says dt entry not found
load kernel could not do normal boot
error verifying vbmeta image - hash mismatch
Click to expand...
Click to collapse
I recall getting a vbmeta error too and I think it was a locked bootloader issue? Not sure. Definitely a d2s model?
I just reflashed stock and started again. Long press the volume up button at download selection to unlock bootloader.
I'm fairly sure Odin accepted the recovery file if you convert it to .tar. and disable auto reboot so you can button combo directly to recovery. From there install the main ROM zip.
ROM runs fine, few thing missing that I needed so came away from it unfortunately.

CerebralFlex said:
I recall getting a vbmeta error too and I think it was a locked bootloader issue? Not sure. Definitely a d2s model?
I just reflashed stock and started again. Long press the volume up button at download selection to unlock bootloader.
I'm fairly sure Odin accepted the recovery file if you convert it to .tar. and disable auto reboot so you can button combo directly to recovery. From there install the main ROM zip.
ROM runs fine, few thing missing that I needed so came away from it unfortunately.
Click to expand...
Click to collapse
certainly no locked bootloader here (have had it unlocked since right after I bought it at launch)
but yea, I'm going to try and reflash the ROM and start from scratch. I was on an outdated version of ONe UI (maybe from December) so maybe that was part of the issue
EDIT - oddly enough, I couldn't get LOS recovery installed via Odin. I tried, got success messages, but a reboot into recovery mode just showed stock recovery (I wasn't missing the button combo, to my knowledge). tried a few times before going back to using heimdall
the second attempt (with a fresh install of OneUI's latest firmware) helped me get past that vbmeta error with heimdall
got LOS recovery installed, the ROM sideloaded, and I'm up and running
thanks for the hard work @Linux4 (and all others involved in working on lineageos)

First, thanks a lot for your work and for making it official, @Linux4 !
One question: I'd like to use MicroG instead of the google stuff. But since I'd rather keep it all simple, I'd not use Magisk, if possible. Is there a recommended and/or simple way to get the signature spoofing patch into this rom? Preferably so that OTA updates still work? Would NanoDroid in system mode work?

Phosphoros said:
First, thanks a lot for your work and for making it official, @Linux4 !
One question: I'd like to use MicroG instead of the google stuff. But since I'd rather keep it all simple, I'd not use Magisk, if possible. Is there a recommended and/or simple way to get the signature spoofing patch into this rom? Preferably so that OTA updates still work? Would NanoDroid in system mode work?
Click to expand...
Click to collapse
I guess the best way here would be waiting until there's a build for your device on https://lineage.microg.org/ (they build for all officially supported devices)

is the bug with registering a fingerprint common? I noticed the issue after I first installed it but then was able to add one very quickly
had to format /data to record a tutorial and after installing the build again, I can't seem to get past the fingerprint register issue I noticed before

Enddo said:
is the bug with registering a fingerprint common? I noticed the issue after I first installed it but then was able to add one very quickly
had to format /data to record a tutorial and after installing the build again, I can't seem to get past the fingerprint register issue I noticed before
Click to expand...
Click to collapse
It is not broken or whatever, see this from my telegram group in case you just don't figure it out on your own:
If fingerprint enrollment fails for first fingerprint do the following to get it working (doesn't apply to beyond0lte):
1. Retry adding fingerprint but this time tap fast and don't press too hard when putting your finger on the sensor for the first time
2. Repeat step 1 until enrollment continues without error
3. After that it will work fine and doesn't need any special handling anymore
Click to expand...
Click to collapse
All samsung devices using FOD have that issue it seems, only on first enrollment tho, after that it's completely fine

Linux4 said:
If fingerprint enrollment fails for first fingerprint do the following to get it working (doesn't apply to beyond0lte):
1. Retry adding fingerprint but this time tap fast and don't press too hard when putting your finger on the sensor for the first time
2. Repeat step 1 until enrollment continues without error
3. After that it will work fine and doesn't need any special handling anymore
Click to expand...
Click to collapse
EDIT - was able to get it working through a factory reset with the 'tap fast' being the key thing. it needs to fail that first attempt or something?
but it's quite quick once that hassle is over with

Enddo said:
this worked for me on my first install. describes my exact experience
but yea, it's not working right now. you need a logcat or something?
it's immediately throwing up the enrollment error message right when it attempts the first scan (every time)
Click to expand...
Click to collapse
No need for a logcat, it does work, for retrying you will need to close settings completely, just going *back* is not enough (HAL will stay in that error state)
I'm 100% sure you didn't do so also it works for everyone else

Linux4 said:
I guess the best way here would be waiting until there's a build for your device on https://lineage.microg.org/ (they build for all officially supported devices)
Click to expand...
Click to collapse
Ok, thought about waiting for this ... thanks for confirming it!

Related

[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.

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

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?

[ROM][UNOFFICIAL][RAMDISK][11] LineageOS 18.1 for Galaxy Note10/Note10+/Note10+ 5G Exynos

Requirements:
Any Q or R based firmware installed on your device.
Pre-Install Instructions
Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.
Connect the device to a Wi-Fi network.
Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
From within the Developer options menu, enable OEM unlock.
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Volume Up and connect USB cable to PC.
Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
Your device will reboot, you may now unplug the USB cable from your device.
The device will demand you format userdata, please follow the onscreen instructions to do so.
Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.
Installing LineageOS for the first time
Flash lineage recovery
Only the provided lineage recovery will be supported,
using TWRP might result in a possible data loss!!
If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot
Boot lineage recovery
IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
If using Odin untick auto-reboot before flashing.
After flashing reboot by pressing Volume Down and Power for approximately 7 seconds,
immediately hold Volume Up and Power to boot recovery
IMPORTANT: As of OneUI 3 your device needs to be connected to a PC via USB cable in order to be able to
boot recovery via Volume Up, Bixby and Power.
Factory reset using Factory reset -> Format data/factory reset
Warning: Unlike TWRP this will also erase internal storage!
Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
Optional:
Sideload GApps and magisk by repeating above step
with their zip/apk
Magisk
As this ROM has a working ramdisk sideloading the magisk apk is enough, just as it is
on every other device, no bootimage with magisk included or installing to recovery is needed!

Features
SELinux enforcing
AES-256-XTS FBE encryption
Latest Linux 4.14.x kernel
All cameras are working
Ramdisk is working
Dolby atmos is working
Known issues
VoLTE/VoWiFi
You tell me

This may be a silly question but what distinguishes this from Ivan's Lineage OS 18.1 Rom?
[ROM][Signature Spoofing]LineageOS 18.1 for Note10+ 5G/Note10+/Note10 Exynos
Awesome
forum.xda-developers.com

KiwiNote+ said:
This may be a silly question but what distinguishes this from Ivan's Lineage OS 18.1 Rom?
[ROM][Signature Spoofing]LineageOS 18.1 for Note10+ 5G/Note10+/Note10 Exynos
Awesome
forum.xda-developers.com
Click to expand...
Click to collapse
The main differences are these:
- It's open source
- SELinux is enforcing
- File based encryption on /data
- Merged upstream 4.14.x kernel
- It has a ramdisk (which makes installing e.g magisk a lot easier)

Hello,
Stuck at boot screen.
after side-loading the zip as well as MindTheGapps (x64 version).
Mind you I also added FDroid because I wasn't sure if it's included. Was that bad?
files used were:
"lineage-18.1-20210611-recovery-beyond0lte.img" (of course renamed and .tar'ed flashed with odin)
"lineage-18.1-20210611-UNOFFICIAL-beyond0lte.zip"
"MindTheGapps-11.0.0-arm64-20210412_124247.zip"
"F-Droid.apk" (most recent version)
I have attached a pic of the boot screen just do be clear what I mean. Pressing "vol down + power" does reboot(cannot even turn it off) however neither "vol up + bixby" nor "vol down + bixby" has any effect so I cannot access the phone via heimdall, odin, ADB or fastboot.
are there any options left to try or do I own a shiny new paperweight?`
any help is appreciated.
PL

PortentousLad said:
Hello,
Stuck at boot screen.
after side-loading the zip as well as MindTheGapps (x64 version).
Mind you I also added FDroid because I wasn't sure if it's included. Was that bad?
files used were:
"lineage-18.1-20210611-recovery-beyond0lte.img" (of course renamed and .tar'ed flashed with odin)
"lineage-18.1-20210611-UNOFFICIAL-beyond0lte.zip"
"MindTheGapps-11.0.0-arm64-20210412_124247.zip"
"F-Droid.apk" (most recent version)
I have attached a pic of the boot screen just do be clear what I mean. Pressing "vol down + power" does reboot(cannot even turn it off) however neither "vol up + bixby" nor "vol down + bixby" has any effect so I cannot access the phone via heimdall, odin, ADB or fastboot.
are there any options left to try or do I own a shiny new paperweight?`
any help is appreciated.
PL
Click to expand...
Click to collapse
First, you posted this in the wrong thread, this one is meant for Note10 series, the one for S10 series is over here:
[ROM][UNOFFICIAL][RAMDISK][11] LineageOS 18.1 for Galaxy S10e/S10/S10+/S10 5G Exynos
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...
forum.xda-developers.com
Could you please provide more information on your issue?
Like which firmware version were you on before flashing the ROM etc,
Also I don't quite understand why you list F-Droid.apk in used files, that's not something you sideload in recovery, so it booted up before I guess?
Also if BL splash is still shown I'm quite sure you can still enter DL mode ... just keep in mind your phone needs to be connected to a PC in order for it to work (force reboot and immediately press and hold combination for DL mode while it's connected to a PC)

Linux4 said:
First, you posted this in the wrong thread, this one is meant for Note10 series, the one for S10 series is over here:
[ROM][UNOFFICIAL][RAMDISK][11] LineageOS 18.1 for Galaxy S10e/S10/S10+/S10 5G Exynos
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...
forum.xda-developers.com
Click to expand...
Click to collapse
...Well that explains it I guess.
Linux4 said:
Could you please provide more information on your issue?
Like which firmware version were you on before flashing the ROM etc,
Click to expand...
Click to collapse
yeah... the wrong one.
Linux4 said:
Also I don't quite understand why you list F-Droid.apk in used files, that's not something you sideload in recovery, so it booted up before I guess?
Click to expand...
Click to collapse
that was me being more stupid and no I did not try to boot before.
Linux4 said:
Also if BL splash is still shown I'm quite sure you can still enter DL mode ... just keep in mind your phone needs to be connected to a PC in order for it to work (force reboot and immediately press and hold combination for DL mode while it's connected to a PC)
Click to expand...
Click to collapse
that does nothing. I'll keep trying a bit before I move one.
Thanks for your quick response anyway.

I did the installation by sideload (ROM + Gapps) but when "trying to boot" the device returns to the DL screen.
even restarting to exit the DL screen, the device insists on returning to it.
Galaxy Note 10 (D1)

stenncell said:
I did the installation by sideload (ROM + Gapps) but when "trying to boot" the device returns to the DL screen.
even restarting to exit the DL screen, the device insists on returning to it.
Galaxy Note 10 (D1)
Click to expand...
Click to collapse
Could you please provide more information?
Like I'm pretty sure you get some error message on DL mode screen
As you're actually the first one trying this on d1 (only found a tester for d2s before) you might want to PM me and/or join my telegram group for further debugging if needed

Linux4 said:
Could you please provide more information?
Like I'm pretty sure you get some error message on DL mode screen
As you're actually the first one trying this on d1 (only found a tester for d2s before) you might want to PM me and/or join my telegram group for further debugging if needed
Click to expand...
Click to collapse
i joined the telegram group... i will try to install again.

Linux4 said:
The main differences are these:
- It's open source
- SELinux is enforcing
- File based encryption on /data
- Merged upstream 4.14.x kernel
- It has a ramdisk (which makes installing e.g magisk a lot easier)
Click to expand...
Click to collapse
Thanks for providing the ROM! Does it support signature spoofing?

tempe222 said:
Thanks for providing the ROM! Does it support signature spoofing?
Click to expand...
Click to collapse
I don't include out-of-tree patches, sorry
However in my S10 Series thread there's another solution for this one
Anyways, read the OP, download links are taken down temporarily as some users apparently had problems with getting it to boot
Will be up again next week hopefully (will get a device myself by that time)

Fixed builds are now up

Hi I am new here, I have two questions:
1. Installing using twrp is: just wipe internal storage and install file?
2. Why zipfile from Ivan's version is like ~1,2gb and this .bin file is only ~700MB?

Donkey666 said:
Hi I am new here, I have two questions:
1. Installing using twrp is: just wipe internal storage and install file?
2. Why zipfile from Ivan's version is like ~1,2gb and this .bin file is only ~700MB?
Click to expand...
Click to collapse
1. Do not use TWRP (read the instructions in post #2!) it will eventually corrupt your data when using encryption which we do here
Use lineage recovery instead
2. I only have the proprietary blobs from stock that are *actually needed* probably it's different in ivan's ROM
Also it's a zip too idk why you say it's a ".bin"

Linux4 said:
1. Do not use TWRP (read the instructions in post #2!) it will eventually corrupt your data when using encryption which we do here
Use lineage recovery instead
2. I only have the proprietary blobs from stock that are *actually needed* probably it's different in ivan's ROM
Also it's a zip too idk why you say it's a ".bin"
Click to expand...
Click to collapse
@Linux4
I managed to install your version, its more stable than ivans version so thank you man great job, on ivans version had microphone issues and telephoto2x did not work, this one feels very good and probably usable as a daily driver phone..
I have a question for you, is there a way to add option in settings that blocks notification&quick-access-tiles from being accessed from locked screen?
And S-pen question: is there a way to make keyboard appear when I tap whit S-pen on txt field (it puts cursor there but keyboard does not apper until I tap there with finger.)

@Linux4
I notice S-pen issue, aside from seeing this icon when hovering over clickable button there are scrolling issues, something like one in four attemps fails to regognize gesture, you can open gsmarena.com a try scrolling there and it is very unrelialable and often instead of scroll it taps on some link over there, I tried ivans version and this issue wasnt there, (the hand logo also wasnt there) so maybe you can somehow take S-pen module from him, probably after that this build will be 99.9% complete

Donkey666 said:
View attachment 5367685
@Linux4
I notice S-pen issue, aside from seeing this icon when hovering over clickable button there are scrolling issues, something like one in four attemps fails to regognize gesture, you can open gsmarena.com a try scrolling there and it is very unrelialable and often instead of scroll it taps on some link over there, I tried ivans version and this issue wasnt there, (the hand logo also wasnt there) so maybe you can somehow take S-pen module from him, probably after that this build will be 99.9% complete
Click to expand...
Click to collapse
You know that both this and the other keyboard thing aren't even really device specific issues (actually rather stylus specific, it's the same on another device with SPen I have)?
It's just that AOSP doesn't have good support for these pens, they're basically handled like a mouse
Scrolling is fine for me on my own device tho and I do not get that hand icon (which is due to it being a "mouse") on the post reply button (tho in some other places I do get it)
I'm going to mess with that stuff in the future maybe

Linux4 said:
You know that both this and the other keyboard thing aren't even really device specific issues (actually rather stylus specific, it's the same on another device with SPen I have)?
It's just that AOSP doesn't have good support for these pens, they're basically handled like a mouse
Scrolling is fine for me on my own device tho and I do not get that hand icon (which is due to it being a "mouse") on the post reply button (tho in some other places I do get it)
I'm going to mess with that stuff in the future maybe
Click to expand...
Click to collapse
Yea you are right, I did pay closer attention to S-pen behavior and you are right, it is basicaly a mouse.. And issue solved, had magnetic case and that messed up S-pen behavior..

General [ROM][OFFICIAL][lynx] LineageOS 20

Great

Great. Thanks. Just got my Pixel 7a today.

I gave it a shot and the rom itself works fine, but nothing I did would let Mindthegapps install. Do you have any suggestions? I am following the install steps exactly to reboot to recovery while still in recovery to sideload prior to ever starting the ROM. It says it installs fine but no icons ever show up for the Google apps.

sumdewd01 said:
I gave it a shot and the rom itself works fine, but nothing I did would let Mindthegapps install. Do you have any suggestions? I am following the install steps exactly to reboot to recovery while still in recovery to sideload prior to ever starting the ROM. It says it installs fine but no icons ever show up for the Google apps.
Click to expand...
Click to collapse
Does the Play Store icon exist?
The GApps package may just install Play Services and the Play Store, from which you can install all optional Google apps.
Such packages avoid installing these apps as system apps, since you wouldn't be able to uninstall them without root.

sumdewd01 said:
I gave it a shot and the rom itself works fine, but nothing I did would let Mindthegapps install. Do you have any suggestions? I am following the install steps exactly to reboot to recovery while still in recovery to sideload prior to ever starting the ROM. It says it installs fine but no icons ever show up for the Google apps.
Click to expand...
Click to collapse
You have to reboot to recovery again for it to install on the correct slot

Thank you very much for this ROM.
I will test it and see if it is stable. I hope we will have official lineageOS Builds soon.
Edit: GApps don't work for me either. I'm new to A/B devices (coming from Poco F1), so maybe it's a layer 8 error
I have flashed Lineage, than rebooted to recovery, flashed Gapps+magisk (did not throw any errors, log seemed fine).
No sign of Gapps being installed. So I did it again
Active Partition:A Flashed L+G+M, reboot
now active Partition:B Flashed L+G+M, reboot
now active Partition:A Flashed G+M, reboot
now active Partition:A Factory reset.
Now booted the phone, still no Gapps. However if I understand A/B Partitioning correctly, both Partitions should now contain Lineage, Gapps and Magisk.
What am I doing wrong? The recovery logs don't show any issues, all partitions get mounted, and it seems like the Gapps installer runs without problems.
Edit2: Just tried it again with todays build (from mega) - still the same issue. Gapps just don't install

Optimissimus99 said:
Thank you very much for this ROM.
I will test it and see if it is stable. I hope we will have official lineageOS Builds soon.
Edit: GApps don't work for me either. I'm new to A/B devices (coming from Poco F1), so maybe it's a layer 8 error
I have flashed Lineage, than rebooted to recovery, flashed Gapps+magisk (did not throw any errors, log seemed fine).
No sign of Gapps being installed. So I did it again
Active Partition:A Flashed L+G+M, reboot
now active Partition:B Flashed L+G+M, reboot
now active Partition:A Flashed G+M, reboot
now active Partition:A Factory reset.
Now booted the phone, still no Gapps. However if I understand A/B Partitioning correctly, both Partitions should now contain Lineage, Gapps and Magisk.
What am I doing wrong? The recovery logs don't show any issues, all partitions get mounted, and it seems like the Gapps installer runs without problems.
Edit2: Just tried it again with todays build (from mega) - still the same issue. Gapps just don't install
Click to expand...
Click to collapse
Hmm I guess the issue is with the partition system on our Pixel 7A so has nothing to do with the A/B partitions but the Pixel 7A uses special partitions for Boot and recovery etc, so I guess that the gapps packages can not detect/handle those partitions and therfor it does not work.
I recognized that when I wanted to flash Magisk, it shows as successfull but was not installed.
So I had to patch the init_boot file and flash that to the init_boot partition so I assume something like that applies for Gapps as well!

This was the issue I had. I tried multiple times and combinations to reflash and reboot, and reboot to recovery while in recovery and I eventually gave up and went back to stock. No Google icons of any sort and it would always say it installed fine.

Ok, glad to see I'm not the only one having problems flashing GApps. Does anyone know of a method of getting just the play store functioning outside of flashing from recovery?

treblechet said:
Ok, glad to see I'm not the only one having problems flashing GApps. Does anyone know of a method of getting just the play store functioning outside of flashing from recovery?
Click to expand...
Click to collapse
You can install Aurora Store and login there with your Google account.

treblechet said:
Ok, glad to see I'm not the only one having problems flashing GApps. Does anyone know of a method of getting just the play store functioning outside of flashing from recovery?
Click to expand...
Click to collapse
sumdewd01 said:
This was the issue I had. I tried multiple times and combinations to reflash and reboot, and reboot to recovery while in recovery and I eventually gave up and went back to stock. No Google icons of any sort and it would always say it installed fine.
Click to expand...
Click to collapse
Wishmasterflo said:
Hmm I guess the issue is with the partition system on our Pixel 7A so has nothing to do with the A/B partitions but the Pixel 7A uses special partitions for Boot and recovery etc, so I guess that the gapps packages can not detect/handle those partitions and therfor it does not work.
I recognized that when I wanted to flash Magisk, it shows as successfull but was not installed.
So I had to patch the init_boot file and flash that to the init_boot partition so I assume something like that applies for Gapps as well!
Click to expand...
Click to collapse
Optimissimus99 said:
Thank you very much for this ROM.
I will test it and see if it is stable. I hope we will have official lineageOS Builds soon.
Edit: GApps don't work for me either. I'm new to A/B devices (coming from Poco F1), so maybe it's a layer 8 error
I have flashed Lineage, than rebooted to recovery, flashed Gapps+magisk (did not throw any errors, log seemed fine).
No sign of Gapps being installed. So I did it again
Active Partition:A Flashed L+G+M, reboot
now active Partition:B Flashed L+G+M, reboot
now active Partition:A Flashed G+M, reboot
now active Partition:A Factory reset.
Now booted the phone, still no Gapps. However if I understand A/B Partitioning correctly, both Partitions should now contain Lineage, Gapps and Magisk.
What am I doing wrong? The recovery logs don't show any issues, all partitions get mounted, and it seems like the Gapps installer runs without problems.
Edit2: Just tried it again with todays build (from mega) - still the same issue. Gapps just don't install
Click to expand...
Click to collapse
Pulled old builds and uploaded new ones. Something went wrong with my build configuration which prevented gapps install. Please use the new pre-install steps and images too

Great work @nicknitewolf .. can i wonder what are the main things needed to clear the road for official LineageOS status? Is it that you're not really in the LineageOS community and expect @mikeioannina (who has official builds for most of the Pixel devices) to eventually do it? Or is it that there's specific issues or things that don't conform well. Either way, maybe mike has any idea if the 7a will get official support any time soon..
I will put this on a family member's new Pixel 7a, and maybe leave some feedback, but i still prefer official

mxz55 said:
Great work @nicknitewolf .. can i wonder what are the main things needed to clear the road for official LineageOS status? Is it that you're not really in the LineageOS community and expect @mikeioannina (who has official builds for most of the Pixel devices) to eventually do it? Or is it that there's specific issues or things that don't conform well. Either way, maybe mike has any idea if the 7a will get official support any time soon..
I will put this on a family member's new Pixel 7a, and maybe leave some feedback, but i still prefer official
Click to expand...
Click to collapse
No promises but we are waiting for June ASB

nicknitewolf said:
Pulled old builds and uploaded new ones. Something went wrong with my build configuration which prevented gapps install. Please use the new pre-install steps and images too
Click to expand...
Click to collapse
This fixed it, thanks. I would like to mention that there are sone UI inconsistencies when it comes to the status bar, there's padding on one side and not the other, and when you go into the notification drawer (I think that's what it's called, swiping down from the status bar) the time and the date are not aligned by a little bit vertically. It's a small problem but still somewhat noticeable.

nicknitewolf said:
No promises but we are waiting for June ASB
Click to expand...
Click to collapse
Ok, cool.. are you working together with people from the LineageOS team?
Also, since i never tried this before with any device - would it require a wipe with clean install to upgrade to official should the time come? Or it's likely to be compatible?

mxz55 said:
Ok, cool.. are you working together with people from the LineageOS team?
Also, since i never tried this before with any device - would it require a wipe with clean install to upgrade to official should the time come? Or it's likely to be compatible?
Click to expand...
Click to collapse
Yes and yes. I am already part of the LineageOS team... Current builds are signed with test keys but official builds are signed with separate keys, hence a full wipe is required. You could try the zip attached but I doubt it works (since I don't really wanna test it).

nicknitewolf said:
Reboot into fastboot (With the device powered off, hold Volume Down + Power)
Flash
Click to expand...
Click to collapse
Just wanna say it should be "Reboot into bootloader", as the bootloader type of fastboot is required to flash some of the images: the dtbo, vendor_boot and vendor_kernel_boot partitions can't be read by pure fastboot (what's usually called fastbootD) mode and will throw this sort of error:
Warning: skip copying .. name .. image avb footer (.. name .. partition size: 0, .. name .. image size: .. ).
Sending '.. name ..' (... KB) OKAY [ 0.404s]
Writing '.. name ..' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Click to expand...
Click to collapse
So anyone that got confused should just use `adb reboot bootloader` instead of reboot fastboot

I've flashed the ROM and so far it looks & feels really smooth, thanks!

Currently using GrapheneOS. Will flash LOS once they release a user build with release keys.

Database Info

welcome