{
"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"
}
Edit: FYI the LineageOS S5 klte family maintainer created a new thread here:
[ROM][OFFICIAL][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*)
***
Code:
#include "std_disclaimer.h"
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
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.
All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit the Wiki.
Important Info
WARNING: the official 17.1 build 20201101 is defective, causing a bootloop & got removed from the Lineage servers. The ROMs affected are klte, klteduos & kltedv.
If you updated to 20201101 and are caught in a bootloop as reported by several S5 users in the pages #3 of this thread and the following pages: flash an older version like 20201025 without wiping anything (a.k.a. dirty flash) and you will not lose your aps & settings:
1- On the S5 you can simulate a battery removal if you press Volume down + Power button for 10-20 seconds while frozen, in bootloop or Download Mode: the S5 goes black & turns off.
If you keep on pressing the buttons until the Samsung bootloader splash screen appears & release them then S5 should reboot in System.
Or remove the battery to turn it off.
2- With the S5 turned off hold Volume Up + Home + Power to boot in recovery and either sideload the older version or copy to the S5 the older build as MTP is enabled by default in TWRP and flash it from there.
***
To flash this rom you need TWRP version 3.3.1-0 or newer or the Lineage Recovery specific to your device model.
Some TWRP 3.4.0 users reported fail to install LineageOS after a wipe. Rebooting to TWRP recovery after the wipe solves this issue.
The adb command adb reboot sideload does not work in TWRP for the S5 as if you sideload a file afterwards it will fail as I tested myself with this error message: " command is: 'sideload' and there is no value". You must manually select in TWRP > Advanced > ADB Sideload > swipe to begin sideload then you can sideload your file. You must do the same for each files if you sideload more than one.
The S5 maintainer haggertk recommends not choosing Internal storage for the Micro SD card (adoptable storage) when formatting the card in the device and posted about it here: "...my opinion is no one should use adoptable storage. It's a fragile mess and always has been since Google explicitly does not care about sdcards.".
Some S5 17.1 users reported being stuck in an endless boot animation after restoring a 17.1 TWRP backup. A workaround tested by @wireroot & posted here is to flash the original LineageOS ROM that you were running when you made that backup right after the restore operation. This was confirmed by @jdrch in his post here.
An other possible workaround is to flash "fix_rootfs_label.zip" that you can find here right after restoring the TWRP backup. Note: this was NOT confirmed yet by S5 users in this thread.
EFS Partition Restore - @Eadn33 reported here in the old 16.0 thread that he could not restore the EFS partition with TWRP 3.4.0 but could with TWRP 3.3.1-0 on his S5 G900V. Other models may have that problem also but no other reports so far. See EFS Partition Backup - No Service, No IMEI & No SIM Card Fix for explantions.
Warning: do NOT select install TWRP app in TWRP as it will cause a bootloop.
Download Links
The Galaxy S5 klte variants currently supported by LineageOS are:
klte - SM-G900F, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8
klteactivexx - SM-G870A, SM-G870F
kltechn - SM-G9006V, SM-G9008V
kltechnduo - SM-G9006W, SM-G9008W
klteduos - SM-G900FD, SM-G900MD
kltedv - SM-G900I, SM-G900P
kltekdi - SCL-23, SC-04F
kltekor - SM-G900K, SM-G900L, SM-G900S
Each respective download pages include a link to the official clean installation instructions and a link to Device info which includes a link about how to upgrade to a higher version. For example from official 16.0 to official 17.1 without losing your settings & apps.
The wiki mentions only the Lineage recovery but several S5 users reported successful clean install or 16.0 > 17.1 upgrading while using TWRP instead.
TWRP: https://twrp.me/samsung/samsunggalaxys5qualcomm.html
Google apps (Optional. The S5 requires the ARM for Android 10 version because LineageOS 17.1 is based on Android 10 & the S5's ARM architecture.): https://wiki.lineageos.org/gapps.html
As a rule of thumb the larger the Open GApps package, the more chance of a problem on first boot with the ever changing privapp-permissions.
I prefer the smaller Pico package & just add the extra apps I need from Play Store and https://f-droid.org/ See Open GApps Package Comparison
Some users prefer not installing any Gapps packages & use the Aurora Store v3 - a FOSS Google Play client to download apps from Play Store. Note that some apps may require the Google Play Services & librairies which are included in the Gapps packages & may not work properly or will not get timely notifications because of it.
Root (Optional): The LineageOS AddonSU and Privacy Guard are deprecated in 17.1.
Magisk which is the only root solution for 17.1 @ the present is not supported by LineageOS. See Magisk download & Installation instructions by the Magisk dev & also the excellent Magisk and MagiskHide Installation and Troubleshooting guide by @Didgeridoohan. Thread on XDA: Magisk General Support / Discussion.
Magisk can be installed later at anytime so it's not necessary to install it during the initial installation of LineageOS.
Bug Reporting
If a bug is discovered, confirm it with other users in this thread & include your device model & build date (for ex. lineage-17.1-20201025-nightly-klte), then report it following the LineageOS wiki here: https://wiki.lineageos.org/bugreport-howto.html
Known Bugs - Known Issues
1- On an encrypted S5 17.1 + Gapps if Secure Startup is enabled it may fail to reboot or take a very long time to boot. See bug report here.
From haggert's post here:
...there is some kind of timeout that hits ALL legacy devices - addition of gapps is seemingly enough to push it over the edge. Aside from first boot or upgrade, sometimes you'll be able to get in and sometimes not. I bet if you are able to decrypt in twrp and delete dalvik cache you'll get fully booted again.
Bottom line, if you are encrypted, make sure to disable secure startup (go change the pin/pattern/password, even to the same thing, and say that you do not want to have to answer for the device to start). {bold by me}
Click to expand...
Click to collapse
2- Not a bug really but some S5 users reported fail to boot on 17.1 or no SIM card recognized because they had an older baseband/modem. See S5 Odin Flashable Modem & Bootloader.
Haggertk posted here about 17.1: "...I'm willing to bet that you have some L or earlier baseband. Except for the activexx build, you have to be running M baseband now." {bolding by him}.
3- Google Backup cannot be restored if you use a 4x4, 5x5 or 6x6 lock screen pattern in LineageOS instead of the Android default 3x3 pattern. See the bug report here.
4- Display accepts touch input while off due to proximity and screen does not turn back on after call bug report by @Eadn33. The bug was fixed with klte family builds 2020-11-13 or newer. Thank you Mr. haggertk.
5- SMS reception notification delay depends on doze / unlock state by @wireroot. He posted about it in this thread here.
6- Bluetooth Crashing - Some users reported having issues with Bluetooth in this thread: @KrautHolg here, @liquidraver here and here, @pmduper here, @navcar here and included a logcat, @badesh here and here, @mrmarioman who posted here.
@KrautHolg created a report in the LineageOS bug tracker with a logcat here: Bluetooth repeatedly crashes with multiple devices for the S5 klte LineageOS 17.1.
OTOH @Eadn33 reported here that he does not have any problems "with a soundbar, music and hands free in car , or scan tool for car". I tested for 2 hours listening to music with Bluetooth headphones, received a call & also had no problems on my S5 G900M klte.
So far nobody created a Bluetooth bug report with an attached logcat in the LineageOS bug tracker for the S5 running LineageOS 17.1. See this post about how to create one: S5 Bluetooth Crashing Bug Report?
7- Fingerprint Scanner: Some S5 users reported not being able to register their fingerprints in > Settings > Security > Fingerprint. Contrary to the Lineage instructions the finger must be swiped down & not just "Touch the sensor". See the screenshot & the linked trick if you still can't register the fingerprint in S5 G900F Fingerprint Issue.
Not a bug but some users reported the scanner not working on older basebands but working after updating it like @jackass5 in his post here. See S5 Odin Flashable Modem & Bootloader.
Several users, including me, reported a higher battery usage after registering some fingerprints. See S5 Screen Lock Fingerprint Battery Tests @ Idle - BetterBatteryStat
8- Camera (Snap) > Settings > Storage > if you select SD Card the photos are saved to /external sdcard I.D./Android/Data/org.lineageos.snap/Files/ but taping on the thumbnail of the photo you just took mistakenly opens /storage/emulated/0/DCIM/Camera/. Additionally, Gallery does not see that Files folder but a third-party app like Simple Gallery Pro that does show the Files album.
In LineageOS 17.1 build 2020-11-23 or newer the SD Card option was deleted instead of fixing the bug. See LineageOS 17.1 - In Camera the Option Save to SD Card has Been Removed in this thread.
9- Call Forwarding Not Working - In both the stock Phone app or when dialing a code it's broken. See this post that includes a link to a bug report: S5 klte LineageOS 17.1 Call Forwarding Error. Thanks to @uyguremre for reporting the issue here.
***
S5 U.I. Speed-Up Tip: Try those as fast as you can before the tweak: expand/close notification curtain, app drawer & scroll, recent apps & scroll, horizontal scroll fast between hope pages if you have a few, open Settings & scroll, etc.
Then: Settings > Accessibility > enable Remove animations.
Test again as you did before. Profit!
LineageOS FAQ
https://wiki.lineageos.org/faq.html
LineageOS Stats
https://stats.lineageos.org/
Credits
The S5 klte + variants LineageOS maintainer is @haggertk who valiantly supported the S5 klte family through LineageOS 14.1, 15.1, 16.0 & now 17.1. Big thanks for his perseverance & dedication.
He is also one of the 9 LineageOS directors and maintains other devices as well as you can see in https://wiki.lineageos.org/contributors.html
Many thanks also to the LineageOS team and all the contributors out there in the community that made the Lineage project possible. You can see their names or nicknames in the zoomable & searchable > Settings > About phone > Contributors.
Haggertk seemed uninterested in creating an S5 17.1 tread on XDA or he is too busy maybe so I went ahead and created one using part of the OP of his old S5 LineageOS 15.x thread. If he wants a transfer of this thread's ownership I will gladly do it.
haggertk said:
Device source code:
msm8974-common (shared by all Samsung msm8974 devices): LineageOS/android_device_samsung_msm8974-common
klte-common (shared by all klte* devices): LineageOS/android_device_samsung_klte-common
klte: LineageOS/android_device_samsung_klte
klteactivexx: LineageOS/android_device_samsung_klteactivexx
kltechn: LineageOS/android_device_samsung_kltechn
kltechnduo: LineageOS/android_device_samsung_kltechnduo
klteduos: LineageOS/android_device_samsung_klteduos
kltedv: LineageOS/android_device_samsung_kltedv
kltekdi: LineageOS/android_device_samsung_kltekdi
kltekor: LineageOS/android_device_samsung_kltekor
Click to expand...
Click to collapse
Kernel Source Code:
Kernel tree: https://github.com/LineageOS/android_kernel_samsung_msm8974/tree/lineage-17.1
LineageOS Gerrit code review: https://review.lineageos.org
Android version: 10
Note: this post as well as posts #2 & 3 will be updated soon.
***
Reserved.
Reserved for alternative clean install & upgrading tutorial.
If you are going to make a thread and list mappings to builds, please make it correct. Inspect the wiki (hint: G900AZ and S902L are no longer supported in the klte build).
Sent from my PH-1 using Tapatalk
haggertk said:
If you are going to make a thread and list mappings to builds, please make it correct. Inspect the wiki (hint: G900AZ and S902L are no longer supported in the klte build).
Click to expand...
Click to collapse
Fixed, thanks.
Are you sure you don't want the ownership of this thread?
***
... and for the one for hlte ...
Issue with brightness control 20201025 update
Hi all,
I did an update yesterday from 17.1-20201018-NIGHTLY-klte to 17.1-20201025-nightly-klte via the inbuilt updater and TWRP 3.4.0 on my sm-g900f.
Flash went smooth but brightness control stopped working in 20201025.
If I use the brightness adjustment slider, the global variable is set accordingly, I checked that via Tasker.
But the display itself does not change brightness one way or the other.
Same with auto-brightness on.
I manually flashed back to 20201018 just now. Brightness adjustment works fine again.
Anyone else?
Hawaiihemd said:
Hi all,
I did an update yesterday from 17.1-20201018-NIGHTLY-klte to 17.1-20201025-nightly-klte via the inbuilt updater and TWRP 3.4.0 on my sm-g900f.
Flash went smooth but brightness control stopped working in 20201025.
If I use the brightness adjustment slider, the global variable is set accordingly, I checked that via Tasker.
But the display itself does not change brightness one way or the other.
Same with auto-brightness on.
I manually flashed back to 20201018 just now. Brightness adjustment works fine again.
Anyone else?
Click to expand...
Click to collapse
Actually, was a little concerned, but, did it anyway (My build kltedv). Just concerned about the "Recovery", I have not, switched to LineageOS Recovery. So, knowing I was running what one could say , is Not the correct recovery (Still TWRP )
Had not issues, every thing went rather smooth and easy of course!
thanks
Still on 1 build before latest one
Will change soon, this ROM is brilliant
Hi,
Since updating to lineage-17.1-20201025-nightly-klte-signed.zip (2020-10-25) through the automatic updater, my bluetooth keeps crashing. As I use it all the time with the fitness tracker as well as the earphones it is more than a little nuisance. Any ideas on what should I try first to fix this issue?
Best,
Holger from Flensburg
Hi sorry if this already covered the latest version of this klte ROM keeps shutting down as it installs logo freezes then back to boot screen _ flashed unofficial version same klte phone flashed fine _ clean install always I'm mystified unless its a bootloader version problem ?
Is it safe to dirty flash 17.1 over 16.1 with TWRP? And if so do I also have to flash a newer gapps package?
Thanks!
Arrxa said:
Is it safe to dirty flash 17.1 over 16.1 with TWRP? And if so do I also have to flash a newer gapps package?
Thanks!
Click to expand...
Click to collapse
You have good chances to get it upgraded, if you follow wiki.lineageos.org
KrautHolg said:
Hi,
Since updating to lineage-17.1-20201025-nightly-klte-signed.zip (2020-10-25) through the automatic updater, my bluetooth keeps crashing. As I use it all the time with the fitness tracker as well as the earphones it is more than a little nuisance. Any ideas on what should I try first to fix this issue?
Best,
Holger from Flensburg
Click to expand...
Click to collapse
Nothing. Bluetooth sucks since LOS16, constant disconnects (more frequently if you use more than two devices watch+earphone+car - etc), smart watch can't reconnect after disconnection, etc.
There are temporary solutions, like go to apps and clear storage on bluetooth app + reboot, but it won't last.
If you want more stable bluetooth, go back to 14.1. (or stock)
liquidraver said:
... go back to 14.1.
Click to expand...
Click to collapse
I can only find builds from lineage-17.1-20201025-nightly-klte to lineage-16.0-20200913-nightly-klte -- but nothing older. How do I find a 14.1 build?
KrautHolg said:
I can only find builds from lineage-17.1-20201025-nightly-klte to lineage-16.0-20200913-nightly-klte -- but nothing older. How do I find a 14.1 build?
Click to expand...
Click to collapse
https://androidfilehost.com/?w=files&flid=140202
KrautHolg said:
.. Since updating to lineage-17.1-20201025-nightly-klte-signed.zip (2020-10-25) through the automatic updater, my bluetooth keeps crashing...
Click to expand...
Click to collapse
Have you tried flashing an older 17.1 build over it without wiping System & Data (a.k.a. dirty flashing) so not to lose your settings & apps?
***
curiousrom said:
Have you tried flashing an older 17.1 build over it without wiping System & Data (a.k.a. dirty flashing) so not to loose your settings & apps?
***
Click to expand...
Click to collapse
I haven't done anything yet, exactly because of this. Still considering my options. Reinstalling everything by hand is such a pain....
dtr. said:
Hi sorry if this already covered the latest version of this klte ROM keeps shutting down as it installs logo freezes then back to boot screen _ flashed unofficial version same klte phone flashed fine _ clean install always I'm mystified unless its a bootloader version problem ?
Click to expand...
Click to collapse
Solved _ flashed latest klte firmware via Odin (had to try a few times kept 'looping) eventually managed to install firmware then flashed twrp now running 25.10.20 fine no bootkoops everything OK thanks for the build
Arrxa said:
Is it safe to dirty flash 17.1 over 16.1 with TWRP? And if so do I also have to flash a newer gapps package?
Thanks!
Click to expand...
Click to collapse
Yes, I successfully dirty flashed 17.1 over 16.0 with TWRP 3.4.0. Yes, you need a newer gapps package(ARM, Android 10).
Related
{
"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 is BETA and not ready for daily use at the moment
As of 8-7-2017 permanently marked as BETA.
The project started out as Experimental, as I had no device. Thanks to @Sarum4n it was temporarely BETA since 27-1-2017 as he loaned me his T710. Thanks to donations a used T710 came into budget and is available to test code.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community
First I would like to thank the following developers :
@RaymanFX
@CTXz
@Sarum4n
I used @CTXz his T710 work and @RaymanFX's T815 image to base this lineage 14.1 build on.
Special thanks to @Sarum4n, as he loaned me the T710 to test the builds and debug the boot issue we had. All except lte functionality is tested, as the T710 doesn't have lte.
Before you start
THIS ROM IS ONLY FOR THE SM-T715
Code:
*
* Your warranty will be voided !
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
About the ROM
Current state of ROM : BETA/EXPERIMENTAL
Everything except what's reported below is working. Nothing 'fixed' yet, first build.
What is Fixed
Bootanimation not working
Mic not working
SDCard working again (broke after switch N blobs)
What is not working
Important
Fingerprint scanner not working (included, but not working)
Camera not working (killed it with kernel update )
Vibration not working (probably also kernel)
Adaptive brightness not working (after N blobs?)
Bluetooth not working (broke with switch to N blobs, works on images before 23-04)
Minor
Instructions
How to install Lineage 14.1
If you haven't run stock Android 6.x, flash that first with odin. (image won't boot without this step)
If you don't have TWRP yet, get it from here : TWRP by ashyx
Download the ROM and the Gapps that are located below to your device
Reboot into TWRP by holding VOL UP + POWER + HOME on boot
In case things go wrong make a backup
After the backup has completed return to home and select Wipe and then Advanced Wipe
Now ONLY tick Dalvik Cache, System, Data and Cache
After ticking those, Swipe below to wipe
Once the wipe has completed return to home and select the ROM
After you selected the ROM swipe below to install it
After the ROM has installed flash the Gapps
When all of this is done, reboot into system, wait, and enjoy Lineage 14.1
How to recover from issues
Looks like the reset to recovery (<HOME><VOL-UP><POWER>) is still broken on some or all T710/5 & 810/5 devices with this build.
Press and hold <HOME><VOL-DOWN><POWER> to enter 'download' screen.
Select cancel <VOL-DOWN>
Immediately press and hold <HOME><VOL-UP><POWER> to enter TWRP
Restore back-up made during installation phase
How to ROOT
Install the correct root package from here. (after flash of the image)
In LineageOS 14.1 Enable the developer options
Select Root access
Select Apps Only
Done
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions usually by the same user
Requests that are out of LineageOS's framework (Ex. Adding Samsung Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Changelog
Code:
**********
16-12-2017 - Recompile with latest security patches. (5 dec patchset)
**********
19-11-2017 - Recompile with latest security patches. (6 nov patchset)
**********
17-10-2017 - Recompile with krack patches.
**********
6-10-2017 - Recompile with latest security patches. (5 okt patchset)
**********
12-08-2017 - Recompile with latest security patches. (5 aug patchset)
**********
16-07-2017 - Recompile with latest patches, BT seems to work. (needs more testing)
**********
07-07-2017 - Recompile with security level july 5th.
**********
04-07-2017 - Recompile with latest patches.
**********
20-06-2017 - Recompile with latest gts2-common patches.
**********
16-06-2017 - Recompile with june security patches.
**********
28-05-2017 - Adaptive brightness seems to work.
**********
14-05-2017 - Build SDCard fix, SD card wordk again. (BT still broken)
**********
28-04-2017 - Build with Nougat T815 (common) and T810 (device specific) blobs.
- Broke external SDCard, BT
**********
16/04/2017 - Patched mixer paths.
- Included ril changes from gts210ltexx as they are needed due to changes in common sections.
- Vibrate patch added.
**********
12/03/2017 - Rebuild with patchlevel March 5th..
**********
26/02/2017 - Switched back to Samsung RIL.
**********
06/02/2017 - First build from LineageOS Github.
**********
Downloads
Latest LineageOS 14.1 build : https://www.androidfilehost.com/?fid=962021903579500326
All LineageOS 14.1 BETA releases can be found here : https://www.androidfilehost.com/?w=files&flid=141202
Recommended GAPPS by opengapps.org : http://opengapps.org/ (I use pico)
Source
Special Thanks to @RaymanFX for releasing his Exynos 5433 source, without him this ROM would most likely not be possible!
All our sources can be found here : https://github.com/LineageOS/android_device_samsung_gts28ltexx
Screenshots
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
XDA:DevDB Information
LineageOS 14.1 for Samsung Galaxy Tab S2 8.0 T715, ROM for the Samsung Galaxy Tab S2
Contributors
T_I,CTXz, Sub77, Moonbutt74, RaymanFX, Hennymcc
Source Code: https://github.com/LineageOS/android_device_samsung_gts28ltexx/URL]
ROM OS Version: 7.x Nougat
Based On: LineageOS
Version Information
Status: BETA
Created 2017-02-05
Last Updated 2017-02-05
XDA:DevDB Information
LineageOS 14.1 for Tab S2 8.0 2015, ROM for the Samsung Galaxy Tab S2
Contributors
[URL="https://forum.xda-developers.com/member.php?u=4557146"]T_I, RaymanFX, CTXz
Source Code: https://github.com/LineageOS/android_device_samsung_gts28ltexx
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Android 6.x flashed at least once before install
Based On: LineageOS
Version Information
Status: Beta
Created 2017-02-05
Last Updated 2017-12-26
Forgot 2 patches for the merge in Lineage, added them today and build image. OP updated.
Is there any diffrence to the build which was posted in the old thread?
xeta_at said:
Is there any diffrence to the build which was posted in the old thread?
Click to expand...
Click to collapse
Other then that the sources are coming from LineageOS github, nop. At least there are no changes in my sources, some in LineageOS sources, but I didn't notice any differences.
This was a test build to see if all was transferred correctly.
Ok.
Then I will wait for the next Update.
Except the mentioned problems the ROM already works fine for me.
Hi,
Have Problems with YouTube (Videos Looks after 30sec in Zoom) and Facebook Videos are Not starting.
(T715)
I think, I'll give it a try. Actually I'm using [ROM 5.0.2] [Kernel] [Mod] Tab S2 [T715-T715Y] v3.0 By Jafangie|Deodexed|Rooted . But there are still some issues, like failure "Gallery stopped".
Best regards
Tim
Slider-Override said:
Hi,
Have Problems with YouTube (Videos Looks after 30sec in Zoom) and Facebook Videos are Not starting.
(T715)
Click to expand...
Click to collapse
Same in T710 but it's random, I mean the YouTube problems
Great work, but this was built for the 10'' model. The screen size of the rom needs adjustment to fit exactly for this model. Other than that, once the important issues get resolved, this is my preferred ROM for my Tab S2. Already installed.
eliasps said:
Great work, but this was built for the 10'' model. The screen size of the rom needs adjustment to fit exactly for this model. Other than that, once the important issues get resolved, this is my preferred ROM for my Tab S2. Already installed.
Click to expand...
Click to collapse
You can try to set 700 instead of 768 dpi.
Yes, the camera isn't working.
In the upper tiles I found a button for the torch. The tablet hasn't a torch.
Sorry, this i my third post:
GPS isn't working . No signal in sight.
GPS isn't working .
Adaptive brightness with manual correction isn't possible.
+ hotspot won't work, video zooming in while changing to higher resolution
I use the fingerprint sensor a lot, maybe if this will be fixed i'll try the rom. I've heard about 7.1 coming for some 9.7" Tab S2 variant...not sure if 8" version will receive it too. But i didn't hope. Samsung teached me how to kill a device without major updates with my previous device.
Giuskiller said:
I use the fingerprint sensor a lot, maybe if this will be fixed i'll try the rom. I've heard about 7.1 coming for some 9.7" Tab S2 variant...not sure if 8" version will receive it too. But i didn't hope. Samsung teached me how to kill a device without major updates with my previous device.
Click to expand...
Click to collapse
Lineage 14.1 is Android 7.1, so yeah, it'll be there for T715. Fingerprint sensor isn't working on any Samsung device (at least on any Tab S2, 2015 or 2016 release). This is being worked on, at least for all Samsung Exynos devices. (common lib)
T_I said:
Lineage 14.1 is Android 7.1, so yeah, it'll be there for T715. Fingerprint sensor isn't working on any Samsung device (at least on any Tab S2, 2015 or 2016 release). This is being worked on, at least for all Samsung Exynos devices. (common lib)
Click to expand...
Click to collapse
Yeah i know that Lineage OS is Android 7.1, but i was talking about official one by Samsung. I've heard it's coming for some Tab S2 9" variants but it's not sure if it will be avaible for 8" models too. Anyway, hope that the fingerprint will be fixed soon thaks for all the work you do guys
Hello and a big thank for your work so far. I gave it a try (2017-02-06 build) and liked it very much. Despite the camera problem I encountered a strange behaviour when receiving the first call: I was able to pick up but couldn't hear anything. Then I tried to analyse the issue the behaviour changed - no incoming calls were possible. When I called someone from my mobile they could pick up the call but audio wasn't working. I couldn't hear anything and was not heard. Mobile data worked like a charm over LTE. Do you have an idea how and if this could be fixed? I would like to use Lineage OS as productive OS on my T715 and yes - I am using it for making phonecalls although it might look funny to see me with an 8" device attached to my head. I didn't try if audio would work with a BT device, but maybe I can test this on this WE. For now I'm stuck with stock rom again.
Thanks & Regards, Simon
As I just have a T710 on loan, I can't test RIL and call related issues. Mic should have been fixed, but I'm not sure.
As hardware libs were rewrittento change back to Samsung ril instead of the AOSP one, I had to copy a few gts210ltexx patches to gts28ltexx. I just did a recompile and uploaded the image. OP is updated. Haven't tested it. (I don't own a T715 and haven't had time to test if it'll boot on the T710)
Hello, thank you for the new build. I gave it a quick try, but unfortunately the SIM module didn't recognise my installed SIM card. I tried shut downs etc. So telephony is broken . I rolled back to stock immediately and it worked again.
LineageOS 17.x Unofficial for Galaxy A3 2017
{
"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 10 (Quack), which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* Your warranty is now void. Or not. Depends.
* It's probably expired anyways :D
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
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 Gerrit Code Review.
What's working?
Audio
Calls
Wifi
Hotspot
Mobile data
GPS
Bluetooth
Fingerprint
Camera (both photos and video)
NFC
Sensors
Vibration
Others I have forgot
What isn't working?
Echo present in calls for the other side (no fix currently found)
Video recording with stock camera (fix known, will be implemented in next build)
Encryption and extended storage via SD (possible to fix, didn't have time to debug yet)
Stretched preview in camera, photos are fine (fix has more downsides than upsides)
Supported variants
Galaxy A3 (2017). Dual SIM is also supported.
All variants should be working but only A320FL is well tested since all developers have it.
How to install
Make sure you have latest bootloader and modem before installing this.
Make sure you are using the latest OrangeFox build. (the older ones will fail)
Make sure you have flashed the repartition script.
Download the Lineage build, optionally GApps and Magisk.
In OrangeFox format data. (Menu > Manage Partitions > Data > Format Data)
In OrangeFox wipe everything except SD and OTG.
Flash LineageOS.
Optional: Flash GApps (rightafter).
Optional: Flash Magisk.
Reboot.
Generally it's ok to dirty flash, but if you encounter issues a clean flash should be the first thing on your mind.
Downloads
• ROM
get.mcfy.fr
Google Drive
• Recovery
OrangeFox
• GApps
OpenGApps (arm64): OpenGApps
BiTGApps (arm64): AFH
• Root
Magisk: GitHub
Credits
Huge thanks to:
@Astrako for all the hours spent on the device tree/kernel/vendor/hardware and making this possible.
@McFy for help along the way and letting me use his server as a mirror.
LineageOS Team
Anybody that reported bugs or helped test various stuff, without every one of you Android 10 would never get so stable here
XDA:DevDB Information
[UNOFFICIAL][ROM][A320FL/F/Y] LineageOS 17.x [10.0][64 BIT][Treble], ROM for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
MartinYTCZ
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest modem + BL recommended
Version Information
Status: Beta
Created 2020-02-22
Last Updated 2020-08-26
Telegram group
Join here!
Go also thank @Astrako for his work on the DT, kernel, ports, recoveries and many more
Changelogs
- 20200221
Initial build
- 20200403
March security patches
Many optimisations and smaller fixes
Rootdir updated from A6 2018 Q, along with some proprietary files
Graphics now r29, from A6 2018 Q
Way too much stuff to list here, thx @Astrako for the work
- 20200613
Fixed GPlay crashes
June security patch, and all other LineageOS source changes
SEPolicy Enforcing
Reworked shims
Now using new power HAL
Many smaller optimisations
- 20200713
July security patch and all other LineageOS source changes
Reworked overlays
ROM now passes SafetyNet out of the box
Defined location provider to *hopefully* fix location with MicroG
Updated OMX libs
Other smaller fixes and optimisations
- 20200825 20200830
August security patch and all other LineageOS source changes
Updated FP from coral's April patch to keep passing SafetyNet
Switched to proprietary audio HAL - fixed in-call echo
Other smaller fixes and optimisations
NOTE: Encryption is currently extremely broken and your device will not boot if you'll try and encrypt.
- 20210118
January security patch and all other LineageOS source changes
Other smaller fixes and optimisations
Reserved
Nice work, thanks!
Any guess what could cause the SM-320FL to hard reboot when I insert the microSD card, choose to extend the internal memory, then start to format? It rebooted at 20% of the formatting process, then reboots all the time when I give the PIN code after the bootup and it tries to read the microSD card (I guess). If I take out, no reboot of course.
Edit: any temp. workaround? Formatting in twrp or in another device? (For using it as an internal memory extender, not just as an external storage.)
banciii said:
Nice work, thanks!
Any guess what could cause the SM-320FL to hard reboot when I insert the microSD card, choose to extend the internal memory, then start to format? It rebooted at 20% of the formatting process, then reboots all the time when I give the PIN code after the bootup and it tries to read the microSD card (I guess). If I take out, no reboot of course.
Edit: any temp. workaround? Formatting in twrp or in another device? (For using it as an internal memory extender, not just as an external storage.)
Click to expand...
Click to collapse
I'm dumb for not testing this, I gotta look at home
Hello. First nice work !! I used to have your Lineage 16 which worked fine and decided to upgrade to Lineage17. Yet I have some troubles with the camera with the error "unable to connect to the camera" and camera won't launch. When having this error I have spotted that there is a camera icon in the status bar and I can't get rid of it. Else no other problem detected. Thanks.
yann29 said:
Hello. First nice work !! I used to have your Lineage 16 which worked fine and decided to upgrade to Lineage17. Yet I have some troubles with the camera with the error "unable to connect to the camera" and camera won't launch. When having this error I have spotted that there is a camera icon in the status bar and I can't get rid of it. Else no other problem detected. Thanks.
Click to expand...
Click to collapse
I am not the author of Lineage 16.0, I only use the same mirror
The maintainer of LineageOS 16.0 is @McFy.
If you have the problems with the camera, this sounds like an app using the camera when you try to use it and I haven't been able to reproduce the problem. Please check all your apps and report back.
Hope you like the ROM
Ok thanks. Another issue : I can't get split-screen working with any apps. And you?
Other issue : the echos in calls...but well-known issue on lineage. Hope you will find something...
That is good we do have a separate thread of LOS17 now.
Is spoofing (for microG) already included? Not sure whether patcher works for LOS17 already. If one of you guys here get it working with microG - please rise a hand.
Is OrangeFox a must have or can I keep latest TWRP?
starbright_ said:
That is good we do have a separate thread of LOS17 now.
Is spoofing (for microG) already included? Not sure whether patcher works for LOS17 already. If one of you guys here get it working with microG - please rise a hand.
Is OrangeFox a must have or can I keep latest TWRP?
Click to expand...
Click to collapse
From what other users told me spoofing doesn't work with MicroG.
You can either use the TWRP included in the repartition script or latest OrangeFox. Either way it must support /vendor or you'll get error 7 while flashing
MartinYTCZ said:
From what other users told me spoofing doesn't work with MicroG.
You can either use the TWRP included in the repartition script or latest OrangeFox. Either way it must support /vendor or you'll get error 7 while flashing
Click to expand...
Click to collapse
I think you misunderstood this. The Rom is either spoofed (but obviously not, what a pity!) - or it has to be by external tools like Nanodroid Patcher. Otherwise microG will not work. But as I checked that some time ago, the Patcher couldn't handle Android Q. That's why I am asking. So best option (and less effort) would be if ROM is spoofed already.
Vendor I have already with my Treble+GSI LOS 16 Rom.
starbright_ said:
I think you misunderstood this. The Rom is either spoofed (but obviously not, what a pity!) - or it has to be by external tools like Nanodroid Patcher. Otherwise microG will not work. But as I checked that some time ago, the Patcher couldn't handle Android Q. That's why I am asking. So best option (and less effort) would be if ROM is spoofed already.
Vendor I have already with my Treble+GSI LOS 16 Rom.
Click to expand...
Click to collapse
Yup, ROM is not spoofed out of the box, so your only hope is nanodroid patcher, which doesn't seem to work in Q :/
Also if you've already got Treble, you can flash this with the TWRP you are currently using
Hello, thanks for your great job.
I have two points :
- When using your ROM, after UI start, I have the message system_error_manufacturer (msgid="8086872414744210668") popup. I googled and chek the code isBuildConsistent. On my phone, the two checked strings seem ok. So I dont uderstand why I have this message.
- I try to build myself with the gitlab manifest readme. My first atemp was ok but I also have the system_error_manufacturer error message. Some days latter, I try to patch the function with a big /* */ to avoid the check and always return true. I sync the lineage code and patch the isConsistent() function, rebuild and flash my rom. My phone keep on the bootimg anim and never start. On the /proc/last_krnl, nothing else than some SElinux warning. I try with androidboot.selinux=permissive on kernel command line but same result. I delete all my lineage root and resync all from scratch but the build did not boot anymore. Please, could-you check if your build boot with the last comit of lineage 17.1 and android_samsung_universal7870 ?
Thanks by advance.
Pascal.
pascalr0410 said:
Hello, thanks for your great job.
I have two points :
- When using your ROM, after UI start, I have the message system_error_manufacturer (msgid="8086872414744210668") popup. I googled and chek the code isBuildConsistent. On my phone, the two checked strings seem ok. So I dont uderstand why I have this message.
- I try to build myself with the gitlab manifest readme. My first atemp was ok but I also have the system_error_manufacturer error message. Some days latter, I try to patch the function with a big /* */ to avoid the check and always return true. I sync the lineage code and patch the isConsistent() function, rebuild and flash my rom. My phone keep on the bootimg anim and never start. On the /proc/last_krnl, nothing else than some SElinux warning. I try with androidboot.selinux=permissive on kernel command line but same result. I delete all my lineage root and resync all from scratch but the build did not boot anymore. Please, could-you check if your build boot with the last comit of lineage 17.1 and android_samsung_universal7870 ?
Thanks by advance.
Pascal.
Click to expand...
Click to collapse
I am building myself and running the latest at this time (using the crdroid device tree) and everything is running perfectly for me! (even with a few patches of my own like enabling dark mode in defaults app and a few command-line programs like rtl-sdr, no gapps (f-droid only)). Added screenshots to prove it indeed boots.
If I'm not mistaken this ROM uses the android_samsung_universal7870 device tree as it is on Gitlab?
Then the only few bugs I can talk about are the USB settings unable to be changed live while that worked on the outdated device tree from Github (screenshot can be provided), and the Camera, but I know that's already WIP.
(Sure there's echo in calls but... No one was successful at fixing this and even the crappiest patches I tried myself didn't work)
Thanks to all those who works on this device tree.
The provided Rom of the dedicated XDA thread run fine on my device but when building myself, I have the same problem : traped on bootanim.
Strange, I supose it's my buid env, my laptop is on Debian 10 and I did not make any mod on the standard base.
I will try with a VM and Ubuntu LTS as sugested by AOSP Project.
MartinYTCZ said:
LineageOS 17.x Unofficial for Galaxy A3 2017
How to install
Make sure you have latest bootloader and modem before installing this.
Created 2020-02-22
Last Updated 2020-02-22
Click to expand...
Click to collapse
Thank you for great work, can I ask from where can get latest modem and boot-loader without download whole firmware?
Hello,
Problems are solved ?
Echo present in calls for the other side (investigating)
Video recording with stock camera (fix known, will be implemented in next build)
Encryption and extended storage via SD (investigating)
Stretched preview in camera, photos are fine (probably unfixable)
And stay at home.
Best regards
Migrate doesn't detect it as an installed rom, any help?
pascalr0410 said:
Hello, thanks for your great job.
I have two points :
- When using your ROM, after UI start, I have the message system_error_manufacturer (msgid="8086872414744210668") popup. I googled and chek the code isBuildConsistent. On my phone, the two checked strings seem ok. So I dont uderstand why I have this message.
- I try to build myself with the gitlab manifest readme. My first atemp was ok but I also have the system_error_manufacturer error message. Some days latter, I try to patch the function with a big /* */ to avoid the check and always return true. I sync the lineage code and patch the isConsistent() function, rebuild and flash my rom. My phone keep on the bootimg anim and never start. On the /proc/last_krnl, nothing else than some SElinux warning. I try with androidboot.selinux=permissive on kernel command line but same result. I delete all my lineage root and resync all from scratch but the build did not boot anymore. Please, could-you check if your build boot with the last comit of lineage 17.1 and android_samsung_universal7870 ?
Thanks by advance.
Pascal.
Click to expand...
Click to collapse
I have pushed some changes to GitLab yesterday which fix this problem. You should be able to boot a new build just fine now :highfive:
{
"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 (P), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
Known issues:
Moto Mods Projector and Hasselblad Camera are unknown to work.
Moto Mods with Battery do not report the battery
VoLTE and VoWIFI not working
Moto Mods:
Moto Mods Projector and Hasselblad Camera are unknown to work.
All the other Moto Mods work, but Battery Mods do not report the percentage in the status bar
Instructions:
Always have a backup of the EFS partition made with TWRP stored somewhere, as you may lose IMEI. Restore it if you get 0 as IMEI when booted into the ROM.
Before installing, make sure oreo was the last stock ROM you installed. See notes below if you come from Stock Pie
Download Official TWRP from twrp.me
Flash the TWRP via fastboot
Enter TWRP, go to wipe menu and Wipe Dalvik, Cache, Data, System and Internal Storage.
In TWRP Wipe Menu, do Format Data, then reboot into recovery
Flash the latest build
Flash eventual GApps and SU addon
Reboot
Downloads:
Latest Unofficial build: AFH
Google Apps: OpenGapps
SU Addon: LineageOS Extra Downloads
Notes
TWRP
If the touchscreen doesn't work when rebooting into recovery, press the power button twice to turn off and on the screen. The touchscreen will now work just fine.
GSIs
This LineageOS build ships with Project Treble compatibility (lite VNDK), meaning you can flash a GSI as System Image from TWRP. Please don't report GSI bugs here, report them instead to the GSI's maker. A Format Data from TWRP is required after flashing a GSI in order to avoid problems.
Technical details on our Treble implementation:
This device is a community-treble device, meaning other devs before us made it compatible with Project Treble (lite VNDK), using the oem partion as a vendor. GSIs still have some problems regarding cpu frequency scaling and camera. You have been warned.
.
Coming from stock pie?
For the sake of simplicity, I said that coming from stock oreo was needed. In reality you just need to flash the oreo modem files. There's a script that does exactly that, made by @juniorpassos: https://mega.nz/file/IRxjGDjL#vkdvh4JcMy-LuWgQz4rHhgpWV80029X4ql0_zcMpVug. The script will erase your userdata and cache.
Before starting this script, make sure you have a backup of your EFS partition stored somewhere safe, outside phone's internal storage. After the backup is done, you can reboot your phone into fastboot mode and start the script. Now reboot into TWRP, go into "Wipe" menu and Format Data. Now you can reboot into the ROM. If you get 0 as IMEI, or any other problem related to RIL, go into TWRP and restore the EFS backup made previously.
Wanna help?
If you find a problem or a bug, please share a logcat with us, alongside an explanation of the problem and steps to reproduce. We won't accept bug reporting without a logcat. Collect logcat with:
Code:
adb logcat -b all > logcat.txt
You can also join our Telegram Channels:
Global: https://t.me/z2play
Ex KVT group: https://t.me/Z2PlayGSI
There's a guide made by a user to install the ROM, written in both Portuguese and English, here it is: https://telegra.ph/Como-instalar-LOs-160-How-to-install-LOs-160-08-04
Thanks
Many thanks to @marcost22 for the pair-working we are doing in this adventure, to @davidsonsjesus for his work on KVT, to @jeferson1979 for his help and teaching. Thanks to all the testers that have helped us testing this ROM.
Sources
Device tree
Vendor tree
Kernel
XDA:DevDB Information
LineageOS 16.0 Motorola Moto Z2 Play (albus), ROM for the Moto Z2 Play
Contributors
EmaMaker, marcost22, rahulsnair, @erfanoabdi @vache @kubersharma @jeferson1979
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: ALBUS_OPS27.76-12-25_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
Version Information
Status: Stable
Current Stable Version: 16.0
Stable Release Date: 2020-09-27
Created 2020-07-31
Last Updated 2020-09-27
So how's battery? I'm not sure what does it mean:
CPU governorns have some issues. Conservative is recommended for an optimal battery life
Click to expand...
Click to collapse
Also if I run Oreo 8.1 ROM currently and never had Pie installed do I need anything to do before flashing this? Like upgrading firmware or something?
meelten said:
So how's battery? I'm not sure what does it mean:
Also if I run Oreo 8.1 ROM currently and never had Pie installed do I need anything to do before flashing this? Like upgrading firmware or something?
Click to expand...
Click to collapse
Regarding battery: it's quite good, it can get you through the day without any flaws. Since I'm doing frequent tests and I often hook up the phone to the computer, I don't have good screenshots to show you. Will edit the post eventually when I get some. In alternative, you can join the telegram groups and ask someone. We worked on the cpu scaling and governorns and an update will come for it soon.
Regarding firmware: no, you don't have need to update firmware, and updating it may actually cause some problems with RIL. It's perfect if you stay on the oreo firmware.
Changelog
2020-12-08: Cleanup and uprev kernel (3.18.113->3
18.116). Update camera blobs: fix Electronic Image Stabilization, bring back laser focus sensor, fix recording in WhatsApp., fix issues with video recording in Snap cam Fix encryption and decryption (official twrp over at twrp.me is needed for this to fully work). SeLinux is now Enforcing. Update VNDK to full enforcement. Update graphics props. This is the final build for Android Pie 9.0. We will will soon start the Q bringup, and will not be building any Pie ROM anymore, unless some critical bug is discovered: https://www.androidfilehost.com/?fid=17248734326145679504
2020-09-27: Updated Moto Mods blobs. Updated Audio and BT Blobs. Updated media profiles. Thanks to @marcost22: https://www.androidfilehost.com/?fid=8889791610682947394
2020-09-10: Updated Radio blobs and radio init scripts. Workaround for Ambient Display in Q GSIs. Remove batt_health (has been discovered useless): https://www.androidfilehost.com/?fid=8889791610682934965
2020-08-03: Fixed CPU governors. Updated init scripts. New kernel, updated to 3.18.113. Batt_health is back. Fixed offline charge. Updated perf and IOP blobs : https://www.androidfilehost.com/?fid=8889791610682905855
2020-07-29: First beta release: https://www.androidfilehost.com/?fid=8889791610682905855
I'm tempted to give it a try and probably will next weekend but as Z2P is my main phone I want to ask few things:
1. Do fingerprint gestures work?
2. Does notification LED work?
3. Does "active display" (showing notifications and time with locked screen) work?
4. Have you tried it with Magisk? I'd prefer Magisk rather than Addon SU.
meelten said:
I'm tempted to give it a try and probably will next weekend but as Z2P is my main phone I want to ask few things:
1. Do fingerprint gestures work?
2. Does notification LED work?
3. Does "active display" (showing notifications and time with locked screen) work?
4. Have you tried it with Magisk? I'd prefer Magisk rather than Addon SU.
Click to expand...
Click to collapse
1. Work
2. Work
3. The feature you are speaking about is Ambient Display, and yes, that works
4. Yes, magisk works
hi people, nobody is testing it?
i would like to try it, but i can't right now
battery work fine after cpu governors fix?
thanks
I tried today. ROM installs and boots fine but my SIM card is not detected at all (I live in Europe if it matters).
Also, encryption doesn't work. Every attempt to encrypt phone resulted in bootloop.
Can't say much more because without SIM I can't use it and had return to LOS 15.1
UPDATE: I tried restoring ESF partition as well as flashed stock modem as stated in #1 post but with no luck. Even tried install 15.1 first and then flash 16.0 on top of it (without full wipe/format) but it didn't help either. SIM is just not detected.
On-Screen Navigation Bar
I upgraded from the old Official Lineage 15.1 today. I am having a problem getting the navigation bar to show up (Back, Home, App). I search the settings and it hits "Enable on-screen nav bar" in the "Buttons" sub-menu, but when I go there, there is no option shown
Hi. I installed this rom a few days ago from Havoc based in 8.0 and I had to flash modem cause my imei was 0 in lineageos, after this i have signal normally but can't get H+ or 4G, only H. Another problem is that my whatsapp voices notes are recorded with low volume. All the other things work fine, battery, performance, active display, fingerprint and motorola gestures, all it's ok. Great rom!
I would like that the power off menu and quick settings can't be disables in the lockscreen. In third world it would be usefull haha.
Nahuel123 said:
...
Click to expand...
Click to collapse
Did you flash this modem linked in first post? I wonder what your "fastboot getvar all" shows because mine says "baseband: not found". Which is strange to me because on Oreo roms everything works. I don't know if I flashed that modem correctly.
Nahuel123 said:
Hi. I installed this rom a few days ago from Havoc based in 8.0 and I had to flash modem cause my imei was 0 in lineageos, after this i have signal normally but can't get H+ or 4G, only H. Another problem is that my whatsapp voices notes are recorded with low volume. All the other things work fine, battery, performance, active display, fingerprint and motorola gestures, all it's ok. Great rom!
I would like that the power off menu and quick settings can't be disables in the lockscreen. In third world it would be usefull haha.
Click to expand...
Click to collapse
Yeah, first issue is modem, second is audio; both things were updated and are now in testing. So keep an eye out!
And lastly, i dont think that's possible, at least on our side, it seems to be Lineage controlled
---------- Post added at 11:05 PM ---------- Previous post was at 11:02 PM ----------
meelten said:
Did you flash this modem linked in first post? I wonder what your "fastboot getvar all" shows because mine says "baseband: not found". Which is strange to me because on Oreo roms everything works. I don't know if I flashed that modem correctly.
Click to expand...
Click to collapse
There were some issues on modem on the latest release, mostly location-related; so keep an eye out for the update!
My sim card don't work even after I flashed the moden and the .EFS backup, and the device cant connect with the pc via usb when it's turned on.
How to get an on screen navigation bar
How to get an on screen navigation bar:
1. Root phone (I used the SU addon in the OP)
2. Enable navbar with the app "Navigation bar remover/activator (root)" by Conena
3. If you want to customize the navbar use "Custom Navigation Bar" by paphonb (you can reorder buttons freely in "Expirimetal tweaks")
---------- Post added at 09:55 AM ---------- Previous post was at 09:54 AM ----------
Does anyone know how i can disable the fingerprint gestures ?
Rigulel said:
How to get an on screen navigation bar:
1. Root phone (I used the SU addon in the OP)
2. Enable navbar with the app "Navigation bar remover/activator (root)" by Conena
3. If you want to customize the navbar use "Custom Navigation Bar" by paphonb (you can reorder buttons freely in "Expirimetal tweaks")
---------- Post added at 09:55 AM ---------- Previous post was at 09:54 AM ----------
Does anyone know how i can disable the fingerprint gestures ?
Click to expand...
Click to collapse
Use adb shell as su and run setprop qemu.hw.mainkeys 0
Hey there, I was about to tell a friend to give a try to this ROM instead of phhusson's AOSP v222 to see if by any chances it could solve his trouble with NFC not working.
Therefore can we have any feedback from people here about this? So does the NFC work?
Thanks by advance
And thanks @EmaMaker and others for this work!
voxit said:
Hey there, I was about to tell a friend to give a try to this ROM instead of phhusson's AOSP v222 to see if by any chances it could solve his trouble with NFC not working.
Therefore can we have any feedback from people here about this? So does the NFC work?
Thanks by advance
And thanks @EmaMaker and others for this work!
Click to expand...
Click to collapse
NFC it's not reported in the Know Issues section, hence it's a working feature
EmaMaker said:
NFC it's not reported in the Know Issues section, hence it's a working feature
Click to expand...
Click to collapse
I'm feeling dumb to ask you this, but where is the Known Issues section?
up
OK, IDK how I missed it...
{
"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.
LineageOS is a free, community built, aftermarket firmware distribution of Android 11 (R), which is designed to increase performance and reliability over stock Android for your device.
Do not lock your bootloader with this installed. You must be 100% stock, I'd suggest on both slots, in order to re-lock your bootloader.
Code:
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community.
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.
Unofficial LineageOS Builds
Essential PH-1 (mata): GitHub Release Page (link was changed to 2021.03.12 Build)
Google Apps
Google Apps are not included in this build. At this time I do not plan to release gapps included builds. Users who require this will have to build or flash gapps their own.
Source
Device | Kernel | Proprietary blobs
Here's a local_manifest for those who want to build at home.
Known Issues
Wi-Fi WPA3 Network Connection (Connection to WPA2 Wi-Fi still works.)
Essential Camera App (Need to install Google apps.)
Release Signature (Signed with test-key. You can sign using your release-keys.)
Prerequisites
Unlocked bootloader
February 2020 Release | QQ1A.200105.032
Fastboot and ADB set up
Installation
Make sure you meet the prerequisites before continuing!
Using Fastboot
1, Flash February 2020 Stock Firmware (Run flashall.bat)
2, Flash LineageOS images (fastboot flash ***_a ***.img)
3, Erase userdata (fastboot -w)
(Reboot to Recovery and install Gapps)
Using TWRP
1, Install TWRP image
2, Reboot to TWRP (Power + Volume UP)
3, Start ADB sideload
(If your phone doesn't work touch panel, connect to PC using USB-C cable and enter this command in terminal.)
adb shell twrp sideload
4, Install LineageOS ZIP via sideload (adb sideload ***.zip)
5, Erase userdata
(Install Magisk and Gapps imitate steps 3 and 4)
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Contributors
conochy (github.com)
(I don't speak English as my main language, so sometimes the sentences are strange or I can't understand comments correctly.)
Source Code: https://github.com/LineageOS
Screenshots
{
"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"
}
Version Information
Status: Beta
ROM OS Version: Android 11, LineageOS 18.1
ROM Kernel: Linux 4.x
Based On: LineageOS
Security Patch 2020-03
Released Date: 2021-03-12
Created 2021-03-11
Last Updated 2021-03-12
Cool, Thanks man.
Ok, First issue using the "lineage-18.1-mata-magisk.img"
dememted1 said:
Ok, First issue using the "lineage-18.1-mata-magisk.img"
Click to expand...
Click to collapse
I noticed that I was building with the WITH_SU=true option.
I'm currently creating a build that doesn't have LineageOS SU.
If you're in a hurry, you can use LineageOS su removal (arm64) Version 16.0 to solve this problem.
(In my environment, I was able to solve it by using this.)
Thank you!
I have just released a new version.
The conflict Magisk SU and LineageOS SU has been resolved.
New version : GitHub Release Page (2021.03.12 Build)
Old version : GitHub Release Page (2021.03.11 Build)
(The link in the first post has been changed to a new one.)
｡･ﾟ･ヾ(｡•﹏•｡)ﾉﾞ･ﾟ･｡ said:
I have just released a new version.
The conflict Magisk SU and LineageOS SU has been resolved.
New version : GitHub Release Page (2021.03.12 Build)
Old version : GitHub Release Page (2021.03.11 Build)
(The link in the first post has been changed to a new one.)
Click to expand...
Click to collapse
Ace thanks. Great work.
Thanks for this ROM.
What GApps are you using? I normally use NikGapps, but it fails to install...
MuddyDog said:
Thanks for this ROM.
What GApps are you using? I normally use NikGapps, but it fails to install...
Click to expand...
Click to collapse
I'm using NikGApps.
But in this LineageOS build, the NikGApps installer doesn't work, so I created a GApps Magisk module instead.
NikGapps Core, Basic Magisk Module installers, and a module that removes LineageOS apps whose functions overlap with Basic.
*It is used personally, I do not guarantee complete operation.
GitHub Module Download Page
Also, the official NikGApps installer has files to install in [Installer-File].zip/AppSet/[AppName]/[AppName].dat.br
If you extract [AppName].dat.br with 7-zip etc. and copy the files in it to the corresponding location of /system with a file manager, you can install it manually without using the Magisk module or the official installer.
Example: __etc__permissions -> Copy the files in that folder to /system/etc/permissions/
Example2: ___priv-app___PrebuiltGmsCore -> Copy the files in that folder to /system/priv-app/PrebuiltGmsCore/
If you want to use Google Setup Wizard, you need to format /data after manual installation.
｡･ﾟ･ヾ(｡•﹏•｡)ﾉﾞ･ﾟ･｡ said:
I'm using NikGApps.
But in this LineageOS build, the NikGApps installer doesn't work, so I created a GApps Magisk module instead.
NikGapps Core, Basic Magisk Module installers, and a module that removes LineageOS apps whose functions overlap with Basic.
*It is used personally, I do not guarantee complete operation.
GitHub Module Download Page
Also, the official NikGApps installer has files to install in [Installer-File].zip/AppSet/[AppName]/[AppName].dat.br
If you extract [AppName].dat.br with 7-zip etc. and copy the files in it to the corresponding location of /system with a file manager, you can install it manually without using the Magisk module or the official installer.
Example: __etc__permissions -> Copy the files in that folder to /system/etc/permissions/
Example2: ___priv-app___PrebuiltGmsCore -> Copy the files in that folder to /system/priv-app/PrebuiltGmsCore/
If you want to use Google Setup Wizard, you need to format /data after manual installation.
Click to expand...
Click to collapse
Excellent, thanks again.
Are you planning to maintain this ROM through to Official Release?... or is it a personal project?
Either way, your work is greatly appreciated.
MuddyDog said:
Excellent, thanks again.
Are you planning to maintain this ROM through to Official Release?... or is it a personal project?
Either way, your work is greatly appreciated.
Click to expand...
Click to collapse
Sorry, I have no plans to continue building LineageOS 18.1 until official distribution begins.
The reason is that my Essential Phone was physically broken today.
(Please be assured that this LineageOS 18.1 Build is not the cause)
Therefore, I will not build for this model until we get it second hand again.
(If I build in the future, I'll post it in this thread to let you know.)
(However, considering the official build start time of LineageOS 17.1 last year, I think that the LineageOS 18.1 build will be officially distributed around next month.)
Thanks for this rom; enjoying trying it out.
Does VoLTE work properly on this ROM?
Hi,
For those who can't wait.
I've followed the instructions from
｡･ﾟ･ヾ(｡•﹏•｡)ﾉﾞ･ﾟ･｡(https://github.com/conochy/LineageOS/tree/mata-18.1.)
You can download the files here :
MediaFire
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
And how do you like it? Any mejor bugs?
It's my daily driver since March 12, but I don't use Magisk and Gapps.
I was on ArrowOS before. They seems on par, at least for my usage
Build Updated.
Download Link
This is final my unofficial build of LineageOS 18.1 for mata.
My Essential Phone was physically broken, this build was not tested on my phone.
Official LineageOS 18.1 was released in 2021.04.02.
I recommend you to install official build.
｡･ﾟ･ヾ(｡•﹏•｡)ﾉﾞ･ﾟ･｡ said:
Build Updated.
Download Link
This is final my unofficial build of LineageOS 18.1 for mata.
My Essential Phone was physically broken, this build was not tested on my phone.
Official LineageOS 18.1 was released in 2021.04.02.
I recommend you to install official build.
Click to expand...
Click to collapse
Thank you for all the hard work. I really appreciate that.
｡･ﾟ･ヾ(｡•﹏•｡)ﾉﾞ･ﾟ･｡ said:
Build Updated.
Download Link
This is final my unofficial build of LineageOS 18.1 for mata.
My Essential Phone was physically broken, this build was not tested on my phone.
Official LineageOS 18.1 was released in 2021.04.02.
I recommend you to install official build.
Click to expand...
Click to collapse
Hey i'm having an issue where my cellular radio keeps connecting and disconnecting rapidly. Anything I can try to fix this? I've tried both your latest build and the official build.
Edit: Ive now observed the behavior after a fresh install. It only starts to happen after the device has been restarted. It will operate fine up until that point.
Edit 2: When I roll back to recovery lineage-17.1-20210329-recovery-mata.img and lineage-17.1-20210329-nightly-mata-signed.zip everything seems to work fine. So the issue must be in the latest builds.
Chirtan said:
Hey i'm having an issue where my cellular radio keeps connecting and disconnecting rapidly. Anything I can try to fix this? I've tried both your latest build and the official build.
Edit: Ive now observed the behavior after a fresh install. It only starts to happen after the device has been restarted. It will operate fine up until that point.
Edit 2: When I roll back to recovery lineage-17.1-20210329-recovery-mata.img and lineage-17.1-20210329-nightly-mata-signed.zip everything seems to work fine. So the issue must be in the latest builds.
Click to expand...
Click to collapse
On my phone, there was no particular problem with the connection of the cellular line (Japan, NTT docomo).
LineageOS 18.1 has some network bugs, such as Wi-Fi (WPA3), which I think are related as well. However, I think it will be fixed in the near future.
The official update for 2021.04.05 fixes some networks and APN, so give it a try.
｡･ﾟ･ヾ(｡•﹏•｡)ﾉﾞ･ﾟ･｡ said:
On my phone, there was no particular problem with the connection of the cellular line (Japan, NTT docomo).
LineageOS 18.1 has some network bugs, such as Wi-Fi (WPA3), which I think are related as well. However, I think it will be fixed in the near future.
The official update for 2021.04.05 fixes some networks and APN, so give it a try.
Click to expand...
Click to collapse
Installed the latest update still getting mostly the same symptoms. LTE network connecting and disconnecting rapidly still. Only difference is the device will no longer crash haha. I connect via Koodo mobile in Canada in case anyone else is having a similar issue.
I have a second essential phone I'm going to test this out on.