[ROM][10.0][OneUI-2.5][UNOFFICIAL][EOL]LineageOS-17.1 for samsung M51 - Final - Samsung Galaxy M51 ROMs, Kernels, Recoveries, & Ot

{
"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"
}
This ROM will not be getting more updates or support​
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, 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.
Disclaimer
Instructions :
Download the latest build and gapps
Reboot to TWRP
Do a factory rest
Flash the latest build
Flash proximity sensor fix uninstaller (You only need to flash it if you flashed Proximity sensor fix before. check here)
Flash gapps (Optional; Open Gapps Nano Recommened)
Reboot
Downloads :
TWRP
LineageOS-17.1
Proximity sensor fix uninstaller
GAPPs
Known Issues:
VoLTE (samsung Volte support is not ported to AOSP Yet)
Proximity Sensor
SElinux is permissive
FM radio
did you find any?
Sources:
Device tree
Kernel tree
Credits:
dgattupalli - Initial build
Michael Benedict - For S10 light initial device tree
Version Information
Status: Final​ROM OS Version: Lineage 17.1​Android Security Patch: 5th of February 2021​Vendor Security Patch: 1st of November 2020​

Change Log:
23rd of February 2021:
- Fix Bluetooth crashes when using Bluetooth audio devices
- Fix Bluetooth in-call audio
- Fix SELinux denials
- Fix screen recorder lag
- Enable LTE by default
- Disable proximity HAL for now
28th of January 2021:
- Fix the problem if you flashed open gapps then flashed another ROM without flashing gapps, the new ROM won't boot unless you flash open gapps again
- Fix Offline charging
- Make audio as loud as the stock
8th of January 2021:
- Fix double tap to wake
- Partially fix proximity sensor
- Add hide notch option (Settings > Advanced > Developer options > Display cutout > hide)
5th of January 2021:
- Initial release

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:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Click to expand...
Click to collapse

F.A.Qs:
How to hide notch?
First, activate developer options by going to settings > about phone > click on build number 7 times
Second, Go to Settings > Advanced > Developer options > Scroll down until you find Display cutout then choose hide

Some info about why I do stuff
Why do you need to flash proximity fix uninstaller?
Because if the screen gets turned off during a call, it won't turn back on until the call ends, in addition to that, it makes the phone stuck on black screen in other ROMs

nice!

Great News. Good Effort. Please keep it up.

Download the latest build and gapps
Reboot to TWRP
Flash the latest build
Flash proximity sensor fix (You only need to flash it once or when coming from stock ROM)
Flash gapps (Optional; Open Gapps Nano Recommened)
Reboot
Click to expand...
Click to collapse
Do I need to wipe anything in recovery prior to the flashing procedure? Do I need to format data?

kry52 said:
Do I need to wipe anything in recovery prior to the flashing procedure? Do I need to format data?
Click to expand...
Click to collapse
Yes do a factory rest

Does it increase m51 performance?
Does it improve gaming...

Prxtek said:
Does it increase m51 performance?
Does it improve gaming...
Click to expand...
Click to collapse
I haven't test any games and I haven't used the stock rom at all so I don't know is it better or not... maybe you can test it and tell us

There's some problems (the recorder and 4g problem don't happen with the lineage from dgattupalli):
the lineageos screen recorder make my system extremely slow (~20fps) while recording, the same happens with basically any other recorder. while on the original ROM from samsung, this does not happen.
also, the adaptative brightness does not work. (Now it does!)
bonus: if I use xposed, the lineageos screen recorder just crashes. every other screen recorder just works, but with that lag. (please ignore this! it was my fault: I was restricting the recorder to run as a background task. this kills the application).
relax: the logs are from my installation with open gapps nano and proximity fix, nothing more.
the hardware acceleration of the system seems to be working fine for recording videos with the camera, also for decoding on vlc. things get very slow while recording the screen.
also, the cellular network doesnt reach 4G, just H+. (i'm from brazil) (It was configured to 3G not 4G, please forget this, i'm sorry)
lineageOS version: 17.1 (January 8th, 2021)
lineageOS Download url: https://sourceforge.net/projects/sa...age-17.1-20210108-UNOFFICIAL-m51.zip/download
gapps version: open_gapps-arm64-10.0-nano-20210122
am I using:
a task killer: no
a non-stock kernel: no
other modifications: just the proximity sensor fix

Another problem: the proximity sensor partial fix blanks my screen, but never get it back. So I had to press all the 3 buttons at the same time to force rebooting the phone. (update: that's why the sensor's partially broken)
Why the sound of default screen recorder is so bad? (update: probably because the default sample rate of lineage is very low)

myghi63 said:
There's some problems (the recorder and 4g problem don't happen with the lineage from dgattupalli):
the lineageos screen recorder make my system extremely slow (~20fps) while recording, the same happens with basically any other recorder. while on the original ROM from samsung, this does not happen.
also, the adaptative brightness does not work.
bonus: if I use xposed, the lineageos screen recorder just crashes. every other screen recorder just works, but with that lag. relax: the logs are from my installation with open gapps nano and proximity fix, nothing more.
the hardware acceleration of the system seems to be working fine for recording videos with the camera, also for decoding on vlc. things get very slow while recording the screen.
also, the cellular network doesnt reach 4G, just H+. (i'm from brazil)
lineageOS version: 17.1
lineageOS Download url: https://sourceforge.net/projects/sa...age-17.1-20210108-UNOFFICIAL-m51.zip/download
gapps version: open_gapps-arm64-10.0-nano-20210122
am I using:
a task killer: no
a non-stock kernel: no
other modifications: just the proximity sensor fix
Click to expand...
Click to collapse
myghi63 said:
Another problem: the proximity sensor partial fix blanks my screen, but never get it back. So I had to press all the 3 buttons at the same time to force rebooting the phone
Why the sound of default screen recorder is so bad?
Click to expand...
Click to collapse
Proximity is partially broken. the screen doesn't turn back on until the call ends.
Adaptive brightness is working, but it takes a few seconds until it detects the light changes.
for the screen recorder, did this problem appear in the latest build or all the builds?
For network doesn't reach LTE make sure that in network settings that the preferred network type is LTE

Thank you for an update. The previous version caused random reboots even on a clean flashed phone, now I'll try to install a new one.

Can someone tell me, is the parallel application feature (dual apps) available in this rom?

k1n9n0th1n9 said:
Can someone tell me, is the parallel application feature (dual apps) available in this rom?
Click to expand...
Click to collapse
This is a probably a knox feature. So I coudn't find anything about it on my LineageOS installation, and if I go back to the stock rom, this feature + some stuff like samsung pay will not work anymore. (nope, it works! sorry. I thought this wouldn't work anymore, considering what I saw on wikipedia about knox).

LahKeda said:
Proximity is partially broken. the screen doesn't turn back on until the call ends.
Adaptive brightness is working, but it takes a few seconds until it detects the light changes.
for the screen recorder, did this problem appear in the latest build or all the builds?
For network doesn't reach LTE make sure that in network settings that the preferred network type is LTE
Click to expand...
Click to collapse
I can confirm that the problem was happening on the build before january 28. I can't test the newest build now because I don't have an SD card or OTG cable to backup my current installation (well, my /data is encrypted too). If you really want me to test it, please reply and I'll do it. (I tested and the problem still there)
For now I'm using the another lineageOS rom, which has less updates than yours and it doesn't get that slow while recording the screen, just if I do some gpu-intensive task. https://forum.xda-developers.com/t/rom-10-0-unofficial-lineage-17-1-for-galaxy-m51.4212531/ (Not anymore. Now i'm using your rom).
If you're able to test, please: open the recorder app, start recording the screen and do any normal task, while checking if the UI is running at about the same framerate as before. Also, does the microphone audio on the recording sound really bad too? (things get worse if you choose to show taps on the developer options)

myghi63 said:
This is a probably a knox feature. So I coudn't find anything about it on my LineageOS installation, and if I go back to the stock rom, this feature + some stuff like samsung pay will not work anymore.
Click to expand...
Click to collapse
if i flash this rom then back to stock, dual apps feature will not work?

k1n9n0th1n9 said:
if i flash this rom then back to stock, dual apps feature will not work?
Click to expand...
Click to collapse
I can't confirm it now, because I would have to wipe everything and I can't do a backup, but I can say it probably will not work anymore (I tested, it works. sorry).

Related

[ROM][8.1.0][OFFICIAL][WEEKLY] LineageOS 15.1 for S9 and S9+ (Exynos)

Note: This is not a ROM based on the ROM shipped with your device. Exynos variants such as International (F), International Dual(Hybrid)-SIM (F/DS), Korean (N) ONLY. In NO way it is compatible with Snapdragon variants including but not limited to American(U/U1/A/T/P/V), Chinese(0/8/6), Hong Kong(0), Japanese(SC-*), Canadian(W) variants.
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. 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.
Features Overview:
https://www.xda-developers.com/lineageos-15-feature-list-overview-screenshots-video/
Screenshots:
View attachment 4491847View attachment 4491848View attachment 4491849
{
"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"
}
Device Info:
Galaxy S9 (Exynos): https://wiki.lineageos.org/devices/starlte
Galaxy S9+ (Exynos): https://wiki.lineageos.org/devices/star2lte
What's working:
This build is an official LineageOS build. Compliance with our device support requirements is enforced and guaranteed. That means including but not limited to these hardwares will work:
Wi-Fi
Bluetooth
Mobile Network (Calling, Data, etc.)
Audio
USB
GPS
Camera
Fingerprint Sensor
NFC
Etc. Check device support requirements for more.
What's not working:
Applicable exceptions granted in device support requirements.
Obviously Samsung's own features such as Samsung Pay, KNOX, Theme Center, Game Launcher, etc. won't be ported to LineageOS. We may have our own implementation to similar functions, though.
Iris sensor does not work because AOSP upstream does not support that yet.
IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port that to LineageOS.
Instructions:
Make sure TWRP has been installed and functional.
Download the latest build (and optionally gapps).
Reboot to recovery
Wipe data and cache (required if you switch from other ROMs)
Flash the latest build (and gapps)
Reboot
LineageOS updater will handle updates automatically (OTA).
If you upgrade manually from older official releases to newer releases, you don't need to wipe your data or reflash gapps.
Downloads:
Galaxy S9 Exynos (G960F/FDS/N): https://download.lineageos.org/starlte
Galaxy S9+ Exynos (G965F/FDS/N): https://download.lineageos.org/star2lte
Root addon: https://download.lineageos.org/extras
Google Apps: https://wiki.lineageos.org/gapps.html
Reporting Bugs:
https://wiki.lineageos.org/bugreport-howto.html
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 /proc/avc_msg.
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.
Please use LineageOS BUG tracker to report BUGs. BUGs reported in the thread could be ignored due to large number of posts.
Channel and Group:
LineageOS Channel (News and Updates):
https://t.me/lineageos_star
AOSP-like ROMs (not limited to LineageOS) Group (Discussion, Quick Tech Support and Early Testing):
https://t.me/joinchat/DTrGs0ygFKxHhc3bb11YKw
XDA:DevDB Information
LineageOS for Galaxy S9 and S9+, ROM for the Samsung Galaxy S9
Contributors
jesec
Source Code: https://github.com/LineageOS/
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Created 2018-04-24
Last Updated 2018-05-05
Changelog:
This post only includes important device-specific changes. It does NOT mean the LineageOS is not updated if this post is not updated as we frequently makes platform-wide changes which benefit all devices (not limited to this one). Check https://download.lineageos.org/ for global LineageOS changes.
For details (sources) of device-specific changes, watch these repos:
https://github.com/LineageOS/android_device_samsung_star-common
https://github.com/LineageOS/android_device_samsung_star2lte
https://github.com/LineageOS/android_device_samsung_starlte
https://github.com/LineageOS/android_kernel_samsung_universal9810
and/or follow me: https://github.com/jesec
May 15th, 2018:
Use Clang to compile kernel
Update kernel to Linux 4.9.99
Other optimizations for performance and battery life
May 7th, 2018:
Support stereo audio for dual speakers
Support haptic engine for vibration
Allow to use auto brightness while dozing (AOD, Ambient Display)
Add an option to invert navigation bar layout
You can find the toggle at Settings -> System -> Buttons -> Buttons and layout.
Samsung navbar layout is no longer default.
Enable charging LED
Fix USB accessory mode (Android Auto, etc)
Boost I/O performance
Allow device to enter deep sleep when AOD is on or when proximity sensor is blocked (eg. in pocket)
Decrease booting time
Update kernel to Linux 4.9.98
Other optimizations for performance and stability
May 1st, 2018:
Initial official LineageOS build
Troubleshooting and Frequently Asked Questions:
Critical hardwares (Wi-Fi, BT, Mobile Network, etc.) not working for you:
Developer has thoroughly tested hardwares guaranteed to work by official device support requirements.
It is highly unlikely this ROM itself has BUGs which make these hardwares unavailable to you.
If one or more of these critical hardwares are not working for you, there are several possible causes:
1. Vendor files or firmware on your device have been modified in an unexpected way (other ROMs may do those modifications).
In this case, please use Odin or other means to restore your phone to stock and then flash again.
2. Vendor files or firmware on your device is too old to be compatible.
In this case, please update the vendor files or firmware to the latest version.
3. Vendor files or firmware on your device is too new to be compatible.
LineageOS is actively maintained. It is unlikely that you will be faster than the developer in catching updates but this did happen sometimes. In this case, please file a formal BUG report.
4. There are BUGs with ROM but only limited to some devices.
If you believe this is the case, please file a formal BUG report.
Note that vendor firmware is NOT only the baseband and bootloader.
(Tip: Size of adequate vendor firmware package (contains bootloader, baseband AND vendor) should be at least 200MB.)
You can download vendor firmware package from https://www.androidfilehost.com/?w=files&flid=272468 and then flash it via Odin.
These files only contain necessary vendor firmwares. You won't lose your data when you flash them.
How's the camera?
Well. Given the hardware support is there, the camera is pretty much stable but the image quality can not be guaranteed as OEMs like Samsung use proprietary post processing algorithms which can't be made available to this ROM.
If you only use Camera to scan QR code or you don't really care about quality, you are good to go with built-in Camera.
If you want general good quality images and you don't rely on Samsung's features like 960fps slow-mo, you can try to use Google Camera port which can produce pretty decent images. (Optional: After install GCam, you can disable built-in camera so the system will default to GCam)
If you heavily rely on Samsung's camera features, unfortunately this ROM can not give you those features now and in the future.
Note: LineageOS does not provide technical support to GCam ports. Use at your own risk. DO NOT file BUG report of GCam.
How's the audio?
Speakers, earpieces, wired headphones, in-call audios, Bluetooth audio devices. Pretty much all audio hardware supports are there. But here are several things you should know:
1. Dual speaker is working but not perfect. I mean it is functional but it it not "tuned by AKG". Some apps have compatibility issues with dual speakers. If you met apps which don't use two speakers, a workaround is go to Settings -> Accessibility and then toggle "Mono audio" on and off.
2. Samsung's audio addons like Soundlive or Dolby Atmos are not available and they will not be available in the future.
Why some apps don't scale to full screen?
To ensure maximum compatibility, Google defaults max aspect ratio of old apps to 1.86 (roughly 16:9).
This is more of the app's problem instead of system's. If you found new commercial apps that are not compatible with longer screens, you can go to their Play Store page, write a review to demand support.
If you want to force apps to use full screen aspect ratio, go to Settings -> Display -> Full screen apps and choose which apps you want to use in full screen.
VoLTE, VoWiFi?
NO. It is not available now and it will not be available in the future.
Please do not spam the thread with any VoLTE, VoWiFi related requests/questions.
Thanks jesec for an official build already:good:
Hope the next build completes without errors!
cant wait for official release, been hanging to try it out
Is there any possibility of Volte working in near future? Also, Volte not working means data over LTE will work right?
Awesome as always!!
Unofficial build works great and now official!
Great work!
Greets Maik
All the main link are nonexistent: even the pre-release ones
""""Whoops - this page doesn't exist
This device has no available builds. Please select another device."""
harry92008 said:
Is there any possibility of Volte working in near future? Also, Volte not working means data over LTE will work right?
Click to expand...
Click to collapse
No. Do not expect VoLTE to work in any future version. No development effort will be put into that.
Your LTE mobile data will work fine.
cvenk said:
All the main link are nonexistent: even the pre-release ones
""""Whoops - this page doesn't exist
This device has no available builds. Please select another device."""
Click to expand...
Click to collapse
I accidentally put links of AFH developer console. The thread has been updated with new links.
what about the camera(s) compared to stock? (quality, 2x zoom, dual aperture etc) stereo speakers? thanks!
[email protected] said:
what about the camera(s) compared to stock? (quality, 2x zoom, dual aperture etc) stereo speakers? thanks!
Click to expand...
Click to collapse
Also curious
I really appreciate this release! S9 is definitely moving on in development
Guys, considering I am 100% stock, to go for this I would install TWRP following their tutorial and then I'm free to flash this?
Following this tutorial here for twrp: https://forum.xda-developers.com/ga...cross-device-development/twrp-exynos-t3763464
I'm unlocked and encrypted.
And what about battery life?
Anyway, thank you for supporting the S9 so quickly.
Thank you @jesec ! Had the S8, Note 8, and had no Lineage or AOSP support. Glad now with my S9+ there is proper support!
Is there anywhere I can make a small donation towards your development of this?
Magisk does not work, not even on LOS, causes bootloop.
Camera is quite bad, seems like there is no image processing at all, variable aperture and second lens not supported at all.
I flashed the addonsu-15.1-arm64-signed.zip but I still don't get root. Magisk and supersu don't work either. Is there something I missed?
Swarai said:
I flashed the addonsu-15.1-arm64-signed.zip but I still don't get root. Magisk and supersu don't work either. Is there something I missed?
Click to expand...
Click to collapse
Did you enable it in developer settings?
Exelios said:
Camera is quite bad, seems like there is no image processing at all, variable aperture and second lens not supported at all.
Click to expand...
Click to collapse
Have you tried the Gcam Port?
rhino666 said:
Did you enable it in developer settings?
Click to expand...
Click to collapse
Yes, with adb... And no profit. Thank you
ROM works great but there were a few annoying app glitches (Spotify transition freezing), NFS stutter/geo-tilt freezing etc... With in time it should get better. Back to TouchWiz I go for the time being.

[ROM][9.0.0_r35][Unofficial][LineageOS 16.0] [OSPREY] [20190420]

{
"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.
What's working :
Boots
RIL (Calls, SMS, Data)
Bluetooth
Dual-SIM
Wi-Fi
Camera
Video Recording
Video Playback
Audio ( Record and Playback )
Sensors
Flash
Led
Offline Charging
SELinux Enforcing
What's not working :
You tell me
Instructions :
Download the latest build and gapps
Reboot to recovery
Flash the latest build and gapps
Reboot
Downloads :
Builds : https://androidfilehost.com/?fid=1395089523397948075
Gdrive mirror - https://drive.google.com/file/d/1byxYWMV35fx-qQ_80qRoZLqFpnzN28oA/view?usp=drivesdk
Root addon : https://download.lineageos.org/extras (available for Lineage 16.0, use Magisk 18 or newer instead!)
Google Apps : http://opengapps.org/
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 /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--
Phone model:
Lineage version:
Lineage 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:
LineageSettings/Performance settings (other than stock):
Dual SIM:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Credits :
@Luk1337
@luca020400
@Somcom3X
@kaustubh88 and @crpalmer
@Thecrazyskull
@Carlos Arriaga
@RenanQueiroz
Motorola : For providing the Kernel Source Code
LineageOS Team
Kyle Harrison for his work on osprey
Contributors
anisgvr
chil360
NOTE:
Thanks a lot and lot to chil360 ( Kyle Harrison ) for his work in osprey . He helped a lot in bringing up pie for the device. Whole credits goes to him .
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Based On: AOSP
Version Information
Status: Stable , daily driver material
Created 2018-08-28
Last Updated 2019-04-20
Reserved
Screenshots
anisgvr said:
Screenshots
Click to expand...
Click to collapse
See charging speed in screenshots
Seems like you are on a roll with custom roms for osprey, @anisgvr. . Thanks for keeping osprey alive with your work:good:good:. Any plans to make the LOS build official?
superman234 said:
Seems like you are on a roll with custom roms for osprey, @anisgvr. . Thanks for keeping osprey alive with your work:good:good:. Any plans to make the LOS build official?
Click to expand...
Click to collapse
No one in community can make los official As of now because los needs the guy who brought up tree ... unfortunately Alberto97 is no longer developing for osprey.. and we have to wait some magic from sultan Qasim Khan (squid)
I don't understand. Could @squid2 or @Alberto97 or you explain that? This looks like a perfect good rom for official, I asume that you would be willing to carry on the torch but in the end we can't have a perfectly good phone?
Can it be dirty flashed over LineageOS 15.1?
Planning buy this phone as secondary phone, when i saw the development i went happy. Thx for keeping this phone alive!!
Error with wifi connection: buffer space
Hi,
I do not have yet logcat or anything like that. Will try to get some data if that could give more clue.
Flashed that software yesterday - added gapps and su from lineageos.
All looked very nice, but then I got wifi connected but no internet message. Only on that device, so no issues with my home network as first check.
So I used dirty hack with adding settings as suggested:
https://android.stackexchange.com/q...cted-no-internet-but-internet-works-just-fine
but it did not help - so my problem was not detection of internet - but connection on device itself.
In Brave browser the message was like ERR_NO_BUFFER_SPACE.
Restart helped. For a time like few hours.
Now my detection settings are indeed disabled but real problem shows up.
I found some topic on lenovo forum about G5 - close enough - but no real conclusion - for some update helped, some requested phone replacement, and so on. No real root cause explanation.
My plan is to restore back to previous 16 version or even further back to 14.1..
Before going that routine - anyone encountered something like that? Any ideas?
Restart helps, so maybe it is indeed some temp space filling out. Next time I can try to get more from adb - netstat?
Regards
Jan
I installed the PIE Lineage OS a few days ago on my Moto G3 x1541.I've not had one single problem.Fantastic rom.Best yet and the Lineage team have outdone themselves.
Build number Lineage_osprey-userdebug 9PQ2A
190305.002 eng.ubuntu.20190313.090534 test keys
Tip:Before I install any custom rom I do a Hard Reset/Factory reset.
Then once I've installed the rom I let it boot to normal phone mode(Can take quite a while) then reboot to Recovery and do another Hard Reset before setting up my phones.
Also I make Nandroid backups of my Setup Stock rom before installing any Custom roms then I can be up-and-running very quickly.Once I've setup my phone with a Custom rom I again make a Nanroid backup for fast reloading if required.
spljaa said:
Hi,
In Brave browser the message was like ERR_NO_BUFFER_SPACE.
Restart helped. For a time like few hours.
Click to expand...
Click to collapse
Now I was able to observe it via adb. Attaching logcat part. There is successful check, and then failed.
What is odd, DNS and ping like commands do work. It is HTTP calls that fail.
But I had no clue what shortage can be observed on resources.
That socket error in logcat might be something.
I'm quite confident that I run some wipe while installing ROM. But maybe I need to do it over again.
frogzz said:
Can it be dirty flashed over LineageOS 15.1?
Click to expand...
Click to collapse
Clean flash needed to avoid bugs
TWRP treble
https://drive.google.com/file/d/1JJ8bUBSHy5kLBqy3cX-hIAfoijdWKIK5/view?usp=drivesdk
here are almost all rom Osprey
https://androidfilehost.com/?w=search&s=Osprey&type=files
rom extended 6.4
https://builds.aospextended.com/osprey/
I have TWRP 3.2.3.0
Do I need the latest version of TWRP to use this ROM?
Thank you :3
nzkn said:
I have TWRP 3.2.3.0
Do I need the latest version of TWRP to use this ROM?
Thank you :3
Click to expand...
Click to collapse
Use latest
anisgvr said:
Use latest
Click to expand...
Click to collapse
Thanks, but I used the version that I had anyway and it worked without problems.
It is, as people said, a very good ROM. It could perfectly be official. I did not experience any problems at all.
(I did a factory reset before flashing the rom though. normal procedure, as I understand)
Tested:
>Camera: It works. Both photos and videos
>Screen Recording: It works
>Games: I do not play. Emulators work.
>Applications with real-time filters (eg SNOW): They work as expected.
>Netflix works
>Wi-fi and Mobile Data: They work, although in standby, and with Wi-fi, Data uses a lot of battery.
>VOLTE: Not available in my country, sorry
>Battery: It works much better than expected, but it's not magic. It works excellent because it kills applications in the background very aggressively. I did not see battery drains (and my phone is quite old).
Problems:
>Instagram, although it works well, does not show stickers, and neither those weird video recording modes that includes. And boomerang crash the app.
>The way it kills applications in the background is extremely aggressive by default. The first day I did not receive notifications until I opened those apps. I had to go to Battery settings, disable Battery Manager, and Optiization of battery in applications that I did not want it to kill.
This, if I'm not mistaken, is a general problem of Android Pie though
Tested on my Moto G3 8GB / 1GB ram variant.
Thanks for this marvelous 420 rom!
spljaa said:
Now I was able to observe it via adb. Attaching logcat part. There is successful check, and then failed.
What is odd, DNS and ping like commands do work. It is HTTP calls that fail.
But I had no clue what shortage can be observed on resources.
That socket error in logcat might be something.
Click to expand...
Click to collapse
As I saw some odd failed calls for some class with facebook in name I decided to remove one game: "Word Of Words". Plus removed AdAway. As other candidate for creating connections.
And so far so good. It might change, but based on above I'm thinking that even if OS could handle that better - the cause was in software I installed.
Regards
Jan
Does this rom have a separate vendor partition? What's the difference with althafvly's LineageOS 16.0 rom (also based on chil360's trees)?
does encryption work?

[ROM][10.0.0_r41]LineageOS 17.1 for Realme 3 Pro[UNOFFICIAL]

{
"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 6, 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.
What's working :
Audio
Bluetooth
Camera
EGL
Encryption
GPS
RIL (Calls, SMS, Data)
Sensors
Video Playback
Wi-Fi
Known issues:
You tell me the rest
Device specific features:
Game mode (touch boost). check Settings -> Realme Settings
FPS overlay Settings -> Realme Settings
Screen off gestures. check Settings -> system -> touchscreen gestures
Ambient gestures (AOD, Pickup, handwave & pocket). check Settings -> Display -> Lockscreen display -> Ambient display
Report 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 the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel (Ignore):
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
DO NO POST BUGS WITHOUT LOGS AND PROPER STEPS TO REPRODUCE THE ISSUE
DO NO POST BUGS IF YOU ARE USING CUSTOM KERNEL or ANY MODULE
Follow Instructions Carefully otherwise you will get error :
Reboot to recovery
Wipe cache, Dalvik cache, data (If you have done format instead of a wipe, reboot the recovery once or else it will end up with issues/errors)
Flash ROM & Gapps 10 arm64 together (Download Gapps from downloads section)
Done-Reboot Now
Enjoy the clean Rom
Downloads:
ROM:
Realme 3 Pro/X Lite (RMX1851) (Older builds)
Realme 3 Pro/X Lite (RMX1851)
Source code:
ROM: https://github.com/lineageos/android
KERNEL: HyperTeam/android_kernel_realme_sdm710
CREDITS:
LineageOS
Team Hyper
CAF
Testers (Sorry, I couldn't mention everyone here)
Special thanks to Donors for donating me the device :highfive:
XDA:DevDB Information
LineageOS-17.1 for Realme 3 Pro/X Lite, ROM for the Realme 3 Pro
Contributors
karthick mostwanted, darshan1205, nibaji
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: RealmeUI firmware & latest official TWRP
Version Information
Status: Stable
Created 2019-10-05
Last Updated 2020-09-18
CHANGELOGS OF BUILDS:
lineage-17.0-20200103-UNOFFICIAL-RMX1851.zip
lineage-17.1-20200228-UNOFFICIAL-RMX1851.zip
lineage-17.1-20200609-UNOFFICIAL-RMX1851.zip
Thanks a lot.
yeeeeeeeeees!
Screenshots please
Simply Waah !!!
LOS 17 for RM 3 Pro.
Great work ?
???
Some Problems I am facing: (followed the instructions)
- while flashing the provided gapps, it says gapps current android version is not 10 (flashing again fixes the problem)
-after very first boot, google play uncertified device screen occurs asking to register device id.
although device is certified and no such error in pie.
akkeo said:
Some Problems I am facing: (followed the instructions)
- while flashing the provided gapps, it says gapps current android version is not 10 (flashing again fixes the problem)
-after very first boot, google play uncertified device screen occurs asking to register device id.
although device is certified and no such error in pie.
Click to expand...
Click to collapse
Gapps to be blamed.
Digital wellbeing
Digital wellbeing is forceclosing
Hello all,
I am new to XDA, but I am not new in software development.
I wanted to install Lineage OS on my realme 3 pro, but all I have come across is download links to direct installers, and all I see is people blindly trusting and installing those ROMS.
Why aren't developers putting links to their modified source code of Lineage OS so people can review the code and compile directly from source?
How do I know these ROMS/installers/tools don't have malware/botnets in them?
Chandan Modiani said:
Hello all,
I am new to XDA, but I am not new in software development.
I wanted to install Lineage OS on my realme 3 pro, but all I have come across is download links to direct installers, and all I see is people blindly trusting and installing those ROMS.
Why aren't developers putting links to their modified source code of Lineage OS so people can review the code and compile directly from source?
How do I know these ROMS/installers/tools don't have malware/botnets in them?
Click to expand...
Click to collapse
Not everyone is pro like you so spoon feeding is done here
Review after using for 12 hours..
Battery backup is great better than pie
I don't use fingerprint so its not a problem
Play protect certification can be solved easily
I got the error not receiving messages but it got solved by swpping simcard to to other slot...
Kudos to dev for his work
thakur418 said:
Review after using for 12 hours..
Battery backup is great better than pie
I don't use fingerprint so its not a problem
Play protect certification can be solved easily
I got the error not receiving messages but it got solved by swpping simcard to to other slot...
Kudos to dev for his work
Click to expand...
Click to collapse
For play protect did you copy device ID to go.co/...??
Because on doing so it says "ID hexadecimal small in size"
If not, how did you fix play protect?
akkeo said:
For play protect did you copy device ID to go.co/...??
Because on doing so it says "ID hexadecimal small in size"
If not, how did you fix play protect?
Click to expand...
Click to collapse
Flash this in twrp i got it from realme 3 pro telegram group
https://drive.google.com/file/d/1-aiQfPCWKxIkWfv-oVOPXA1rsEuzy_vh/view?usp=drivesdk
gooodddaaaa
Installed Rom and used for a while.
1. SOT is way better than Pie. Not tested for long though.
2. Looks nice and attractive.
3. Voice call quality is good.
Noted following issues :
1. Digital well being keeps crashing. Clearing cache helps for a while but it starts crashing again after some time. May be its open gapps problem.
2. Video calling doesn't work on Jio. Can't say about others.
Rom is overall good and can be used as daily driver. Greater SOT may be a significant advantage.
However, I reverted back to previous installed Rom.
This Rom can be good but currently there are many issues.
1 video recorder not working.
2 digital well being crashes play store licence both connected to Gapps i think, they can be handled.
3 battery percentage, if you change it, nothing happens.
4 Gltools not working on this Rom.
5 CPU frequency is 1700 which is way down for this phone and GPU 504 so it will effect the performance of this phone.
6 now i just powered of my phone and screen went black and mobile didn't powered off neither i was able to reboot or do anything till 10 minutes.
So this makes me worry more about this Rom.
Other than that it's all good.
Don't get me wrong just highlighted the issues so they can fixed and we can use this Rom Thanks.
Sumair-ahmed said:
This Rom can be good but currently there are many issues.
1 video recorder not working.
2 digital well being crashes play store licence both connected to Gapps i think, they can be handled.
3 battery percentage, if you change it, nothing happens.
4 Gltools not working on this Rom.
5 CPU frequency is 1700 which is way down for this phone and GPU 504 so it will effect the performance of this phone.
6 now i just powered of my phone and screen went black and mobile didn't powered off neither i was able to reboot or do anything till 10 minutes.
So this makes me worry more about this Rom.
Other than that it's all good.
Don't get me wrong just highlighted the issues so they can fixed and we can use this Rom Thanks.
Click to expand...
Click to collapse
1. Works here
2. Not related to ROM I would say
3. Lineage team will fix it
4. I can't do much about 3rd party apps issues, I would say report it to the dev of that app (most apps will be crashy for a while until they get updates)
5. So what was the stock frequency?
6. Force reboot it, hold power button continuously
karthick mostwanted said:
6. Force reboot it, hold power button continuously
Click to expand...
Click to collapse
Faced Same dark screen issue here as in LOS 16. Force reboot didn't happen even holding the power button continuously
$adb devices #detected my device
$adb reboot #didnt work (USB debugging permission was given earlier)
Thus I found that
- the black screen keeps the phone ON and prevents button functionality.
-mostly happens when apps consume more memory and running services free <600MB eg. Gcam
only way I found was holding 3 buttons and it went to the bootloader menu

[ROM][UNOFFICIAL][11][lavender] 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"
}
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
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.
What's working:
Everything (if it's not true - tell me)
Features:
4.4 EAS kernel with generater energy model
QS panel 3x3, 3x2 when there is not enough space on the screen (TODO: Make a magisk module to change the QS panel)
Fixed traffic indicator location
Removed black QS status bar background
Oldcam blobs
Instructions:
Reboot to Recovery (Prefer OrangeFox)
Format data, wipe cache, dalvik
Flash fresh firmware (optionally)
Reboot to recovery again
Flash the LineageOS build and any other addons you want (for example, Magisk)
Reboot to the system
Downloads:
ROM: here
Firmware: here. All firmwares for lavender are supported (Prefer latest Global Stable)
NanoDroid with MicroG: here. MicroG will work without the need to patch the system, signature spoofing already exists, but only for MicroG! Flash via Magisk recommended.
NikGApps: here
XDADevDB Information
LineageOS, ROM for the Xiaomi Redmi Note 7
Contributors: ElXreno
Source Code: https://github.com/LineageOS
Device Source: https://github.com/ElXreno/android_device_xiaomi_lavender
Kernel Source: https://github.com/ElXreno/android_kernel_xiaomi_sdm660
ROM OS Version: Android 11
ROM Kernel: Linux 4.4
Based On: AOSP
Version Information
Status: Stable
Telegram links: Support chat && Channel
Created 2021-02-01
Last Updated 2021-02-14
LineageOS 18.1 MicroG
Release date: 31/01/'21
Changelog:
Initial build
Traffic indicator moved to the right side
Removed black QS status bar background
Something else
Notes:
MicroG not included (but signature spoofing available, only for MicroG!). Use NanoDroid package if you want.
4.4 EAS with another energy model
Oldcam blobs
IORap enabled
QS 3x3
Download: SourceForge | MEGA
The rom goes very fast, the only thing that is really annoying is that when making or receiving calls the call interface does not appear, is there any way to solve this problem?
WOLFLIFEX said:
The rom goes very fast, the only thing that is really annoying is that when making or receiving calls the call interface does not appear, is there any way to solve this problem?
Click to expand...
Click to collapse
* I am not responsible for what may happen to your device, it is simply a solution that worked for me *
I found a solution for this problem the problem was in the NikGApps the shortest solution is:
1
Flash the rom first then reboot
2
Boot up, set the device normally and turn it off
3
Start recovey and flash NikGApps ( preferably the latest Canary version:
https://sourceforge.net/projects/nikgapps/files/Canary-Releases/NikGapps-R/03-Feb-2021/ )
4
Reboot.
LineageOS 18.1 MicroG
Release date: 14/02/'21
Changelog:
IORap selinux denials fixed
AOSP Surfaceflinger used
Fluence recording enabled
Other changes
Notes:
MicroG not included (but signature spoofing available, only for MicroG!). Use NanoDroid package if you want.
4.4 EAS with another energy model
Oldcam blobs
IORap enabled
QS panel 3x3, 3x2 when there is not enough space on the screen
Thanks:
@VerpaPhallus & @projectfluid for his device tree & kernel
Download: MEGA | IPFS
I'm currently using official 17.1 lineage OS can i dirty flash this ROM to change to 18.1 Lineage OS and is it stable for daily driver? Thanks in Advance
Babloo1989 said:
I'm currently using official 17.1 lineage OS can i dirty flash this ROM to change to 18.1 Lineage OS and is it stable for daily driver? Thanks in Advance
Click to expand...
Click to collapse
I recommend you to make a clean install, but you can try dirty. As for stability: almost everything is stable, but I would not recommend it if stability is critical.
ElXreno said:
What's working:
Everything (if it's not true - tell me)
Click to expand...
Click to collapse
So, everyone writes that even if the ROM has easily discoverable bugs, BUT, how stable is this ROM? I'm trying to find a good one for a daily driver that won't let me down in an emergency but so far it seems that all the ones I've seen are either a beta or have obvious bugs even though they're called "official" The only one I would potentially end up on is MIUI.
Can it be used as daily Driver?
Netflix and other apps thar block rooted phones are working fine?
Hi, I was using LOS 17.1 for MicroG without any issues but recently upgraded to LOS18.1 for MicroG (downloaded from lineage.microg.org and verified the download). Everything works well except for the camera. Out of the box camera app freezes frequently and then I tried Open Camera and a another camera app. Open Camera is a bit stable but still freezes regularly. Problem is worse when the camera app is being called by other apps.
I note that this has been reported in LOS forum but wondering whether there is a quick work around for this problem.
Many thanks.
evil-google said:
Hi, I was using LOS 17.1 for MicroG without any issues but recently upgraded to LOS18.1 for MicroG (downloaded from lineage.microg.org and verified the download). Everything works well except for the camera. Out of the box camera app freezes frequently and then I tried Open Camera and a another camera app. Open Camera is a bit stable but still freezes regularly. Problem is worse when the camera app is being called by other apps.
I note that this has been reported in LOS forum but wondering whether there is a quick work around for this problem.
Many thanks.
Click to expand...
Click to collapse
Hi, actually this is the wrong thread to post it.
But your solution is to replace new cam blobs with oldcam blobs and flash a kernel that is made for oldcam blobs.
I am attaching the oldcam blobs file for los that can be flashed through recovery. But note that you must change the kernel afterwards that supports oldcam. Otherwise camera will not work at all.
Walden0 said:
Hi, actually this is the wrong thread to post it.
But your solution is to replace new cam blobs with oldcam blobs and flash a kernel that is made for oldcam blobs.
I am attaching the oldcam blobs file for los that can be flashed through recovery. But note that you must change the kernel afterwards that supports oldcam. Otherwise camera will not work at all.
Click to expand...
Click to collapse
Thanks very much for the response. From what you are saying, I feel it may be easier to just downgrade to LOS17.1 which I was using before? I guess the other option I have is to wait for the next update to see whether the issue will be fixed in that release.
Thanks for your suggestion and clarification.
evil-google said:
Thanks very much for the response. From what you are saying, I feel it may be easier to just downgrade to LOS17.1 which I was using before? I guess the other option I have is to wait for the next update to see whether the issue will be fixed in that release.
Thanks for your suggestion and clarification.
Click to expand...
Click to collapse
i am also using los Q because i find it the most stable one. I m using loscam patch in Q as well for better video quality although.
And the camera issue wont get fixed until and unless someone takes over the development of los. currently it has no maintainer and tge builds we get are automated with los source side changes, not device side changes.
Walden0 said:
Hi, actually this is the wrong thread to post it.
But your solution is to replace new cam blobs with oldcam blobs and flash a kernel that is made for oldcam blobs.
I am attaching the oldcam blobs file for los that can be flashed through recovery. But note that you must change the kernel afterwards that supports oldcam. Otherwise camera will not work at all.
Click to expand...
Click to collapse
@Walden0, I thought I might give your suggestion a try before downgrading to 17.1 version. Can you please clarify the following?
1. To add the old camera blob, I could install this zip via Yellowfox Recovery?
2. How can I find out which kernel will support this oldcam blob?
Many thanks.
I have never heard of yellowfox recovery but if its based on twrp then most likely it should be able to flash the zip. (maybe you mean orangefox, if yes then you can flash)
The kernel should have "oldcam" or "old" in its name.
Walden0 said:
I have never heard of yellowfox recovery
Click to expand...
Click to collapse
Just being color blind!!...of course, it is Orange Fox Recovery!!
Interestingly, after I did my post, I just opened Settings->Apps->Camera and pressed 'force stop'. Then I started Open Camera which is what I normally use and so far it appears to be behaving OK. I tried a few still shots and one or two short videos - no freezing as yet but it is too early to know. I will keep testing over the next couple of days and see how it goes.
Thanks for your prompt response.
Just to report that the work around by disabling the Camera app so far have fixed the problem.
Any one who has the same problem may want to try out the following steps;
1. Go to Settings->Apps->Camera->Force Stop
2. Then use an installed app such as Open Camera
Note this is not a permanent solution but a work around and this has to be done each time the phone is rebooted.
EDIT: updated to 6 Dec 21 version and the camera behaves even worse than with the initial install! The above fix does not work anymore although it worked most of the time with the November update.
This ROM was abandoned, pitty, much more polished than official https://forum.xda-developers.com/t/...8-1-for-redmi-note-7-lavender.4381893/page-10.
But both suffer from the same issue: no Mass Storage Gadget so that UMS can work to make memory as USB drive.

Development [ROM][OFFICIAL][barbet] LineageOS 20

{
"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, 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.
Informations :
This ROM uses source built kernel, kernel modules, boot kernel modules (vendor_boot) and vendor image.
This ROM bundles the latest firmware so you don't have to worry about updating firmware.
To use the eSIM you need to have GApps
Instructions :
Follow https://wiki.lineageos.org/devices/barbet/install for how to install
Follow https://wiki.lineageos.org/devices/barbet/upgrade for how to upgrade from LineageOS 19
Downloads :
Official builds
Optional GApps: MindTheGapps
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/*
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
Google Play Store provides a very out of date version of Google Camera. You can use GoogleCamera.apk extracted from stock here
Contributors
mikeioannina
aleasto
The LineageOS team
Source Code: https://github.com/LineageOS
ROM OS Version: Android 13
Source code temporarily on my github before it can be moved to the LineageOS organization
Thanks for putting this together so quickly! I've been running for a couple of days now with MindTheGapps and haven't noticed any significant issues. I'm now pretty darn satisfied with my new 5a (Even though it's a friggin chonk). I'm on Visible and I was able to just pop my SIM card in and everything worked. Wifi calling, texting, 5G connection, etc - all good.
Only weird thing I've noticed is that after setting up fingerprints for device locksreen security I'm not able to then use fingerprint security within my other apps. For example - Chase app tells me "You haven't set up fingerprint sign in on this device", PayPal app says "We're having trouble confirming your fingerprint right now" and Bitwarden app doesn't present an option to enable "Unlock with Biometrics". So I'm using currrently using PINs for these apps which is a fine compromise for me - would be curious to know whether others have experienced this.
There have been some changes to SafetyNet in the past couple of days that tripped ctsProfile on my Pixel 4a running official LineageOS but I was able to pass SafetyNet check in this ROM by installing kdrag0n's Universal SafetyNet Fix v2.0.0 and using MagiskHide Props Config to set device fingerprint to Pixel 5.
CapriciousCrawdad said:
Thanks for putting this together so quickly! I've been running for a couple of days now with MindTheGapps and haven't noticed any significant issues. I'm now pretty darn satisfied with my new 5a (Even though it's a friggin chonk). I'm on Visible and I was able to just pop my SIM card in and everything worked. Wifi calling, texting, 5G connection, etc - all good.
Only weird thing I've noticed is that after setting up fingerprints for device locksreen security I'm not able to then use fingerprint security within my other apps. For example - Chase app tells me "You haven't set up fingerprint sign in on this device", PayPal app says "We're having trouble confirming your fingerprint right now" and Bitwarden app doesn't present an option to enable "Unlock with Biometrics". So I'm using currrently using PINs for these apps which is a fine compromise for me - would be curious to know whether others have experienced this.
There have been some changes to SafetyNet in the past couple of days that tripped ctsProfile on my Pixel 4a running official LineageOS but I was able to pass SafetyNet check in this ROM by installing kdrag0n's Universal SafetyNet Fix v2.0.0 and using MagiskHide Props Config to set device fingerprint to Pixel 5.
Click to expand...
Click to collapse
I doubt you need to set device fingerprint to Pixel 5 for safetynet.
Will fix fingerprint in apps in the next build now fixed
Thanks for the build! it seems mostly good from my testing but one issue im having... for some reason the phone refuses to connect to the carrier after a sim card is inserted. I can see that it is detecting it, and that it sees that it should be using t-mobile, but It wont connect. Not sure if this helps, but i got a logcat of adding the simcard and airplane mode toggling on/off. maybe there is a useful log in there. Log is here. Thank you for your hard work!
grassyloki said:
Thanks for the build! it seems mostly good from my testing but one issue im having... for some reason the phone refuses to connect to the carrier after a sim card is inserted. I can see that it is detecting it, and that it sees that it should be using t-mobile, but It wont connect. Not sure if this helps, but i got a logcat of adding the simcard and airplane mode toggling on/off. maybe there is a useful log in there. Log is here. Thank you for your hard work!
Click to expand...
Click to collapse
I'm afraid i don't know what's wrong.
Can you try with adb logcat -d -b radio
aleasto said:
I'm afraid i don't know what's wrong.
Can you try with adb logcat -d -b radio
Click to expand...
Click to collapse
Here you go
aleasto said:
I doubt you need to set device fingerprint to Pixel 5 for safetynet.
Will fix fingerprint in apps in the next build now fixed
Click to expand...
Click to collapse
You're right. I'm passing now with Pixel 5a fingerprint.
Also thanks for the quick update. After flashing 09/07 build all the biometric security stuff is working as expected. All apps I'd listed in my previous post are fixed.
No new issues to report. Loving the setup
New build out with september security patch
@grassyloki Does your radio work on the latest build by any chance?
aleasto said:
@grassyloki Does your radio work on the latest build by any chance?
Click to expand...
Click to collapse
I can verify radio is fine on my phone. Maybe it's carrier related. I'm on Google Fi with E-sim.
aleasto said:
@grassyloki Does your radio work on the latest build by any chance?
Click to expand...
Click to collapse
The build did not initially... but some fiddling with hidden menus eventually triggered cellular to activate!
See this video as to the issue. Basically the phone was seeing the SIM but not activating, same as the other builds. Airplane mode did nothing, even leaving it for an extended period of time off. I did get it eventually working by heading into the secret menu *#*#4636#*#* in the dialer, then the phone info screen. In here I cycled mobile radio power and changed the prefered network type to something different. Then Cellular activated. Once that happened, i went and selected the correct APN and enabled mobile data, and it worked! Not sure if any code change effected this outcome, but im just glad its working now! Thanks for the build and looking at my issue. Maybe this will help someone out who is having the same issue.
does the lineage updater work on this build or whats the process to update to the newest build?
thanks
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. 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.
Informations :
This ROM uses source built kernel, kernel modules, boot kernel modules (vendor_boot) and vendor image.
This ROM bundles the latest firmware so you don't have to worry about updating firmware beforehand.
To use the eSIM you need to have GApps
Instructions :
Download the latest recovery image and rom zip
Boot to bootloader
fastboot flash boot 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/redfin/install for more detailed instructions (that's for Pixel 5 but the procedure is the same)​​Downloads :
Unofficial builds: sourceforge
Optional GApps: MindTheGapps or opengapps nano
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/*
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
Stock Google Camera app crashes in Night Mode or Astrophotography. As a workaround, install this magisk module.
Contributors
aleasto
The LineageOS team
Source Code: https://github.com/LineageOS
ROM OS Version: Android 11
Click to expand...
Click to collapse
The recovery I flashed keeps telling me that "E:Failed to open /dev/block/bootdevice/by-name/misc: No such file or directory"
Flash Factory Reset also fails for that reason.
I am unable to Enable ADB to Flash Lineage OS for this reason. What am I doing wrong? I used https://mirrorbits.lineageos.org/recovery/redfin/20210908/lineage-18.1-20210908-recovery-redfin.img
Zedicus said:
does the lineage updater work on this build or whats the process to update to the newest build?
thanks
Click to expand...
Click to collapse
Updater does not provide unofficial builds.
Boot recovery and sideload the new zip. If you had addons (gapps, magisk), reboot recovery and flash them again, like the first time.
weeems said:
The recovery I flashed keeps telling me that "E:Failed to open /dev/block/bootdevice/by-name/misc: No such file or directory"
Flash Factory Reset also fails for that reason.
I am unable to Enable ADB to Flash Lineage OS for this reason. What am I doing wrong? I used https://mirrorbits.lineageos.org/recovery/redfin/20210908/lineage-18.1-20210908-recovery-redfin.img
Click to expand...
Click to collapse
Pixel 5a is barbet. That recovery says it's for redfin (Pixel 5).
You need to download the recovery from the sourceforge link in the OP.
Uploaded a new build.
No differences except some experiments on kernel side (branch redbull-merge for the sources). Please let me know if audio still works:
https://sourceforge.net/projects/aleasto-lineageos/files/LineageOS%2018.1/barbet/lineage-18.1-20210911-UNOFFICIAL-barbet.zip/download
Is there a prebuilt magisk for this?
I am on 0909 and audio has been working. It does not get real loaud but otherwise works fine.
Thanks for the build.
Zedicus said:
Is there a prebuilt magisk for this?
Click to expand...
Click to collapse
Just adb sideload Magisk-v23.0.apk in recovery
aleasto said:
Uploaded a new build.
No differences except some experiments on kernel side (branch redbull-merge for the sources). Please let me know if audio still works:
https://sourceforge.net/projects/aleasto-lineageos/files/LineageOS%2018.1/barbet/lineage-18.1-20210911-UNOFFICIAL-barbet.zip/download
Click to expand...
Click to collapse
Just got my 5a delivery today. Applied today's image, worked without any issues whatsoever. Fantastic work, very much appreciated.

Categories

Resources