yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] Tomoms:
I've released new builds of both 17.1 and 18.1. The 17.1 build finally fixes the Eleven music player (thanks to the LineageOS team), brings the new Screenshot QS tile, and a few tweaks that will make those who don't want to rely on Google as much as possible happy: the SUPL server used by the GNSS subsystem is now Vodafone's (supl.vodafone.com) and I'm now using an independent 3rd-party captive portal server instead of Google's (more info in this Reddit post).

The 18.1 build probably fixes lockscreen PIN (please test it and let me know) and bring under-the-hood improvements for our phone.
[ONE Android Development] Pap0ose:
For the 18.1 it is necessary to make a clean flash from the previous 18.1 ?

Thanks
[ONE Android Development] sumitinhome:
The good thing is rom doesn't go to bootloop on lockscreen anymore.. but alternatively now it goes into indefinite loop of unlocking your phone. So problem is partially solved i guess.
[ONE Android Development] tolga1461:
Hello, I use your lineage 17.1 rom. Firstly, thank you so much. Battery performans awesome.

I wonder it, Can I uptade on ota?

again thnx.
[ONE Android Development] Tomoms:
The problem is easily solved for me if I remove TimeKeep, which is the system that restores the proper date & time when you reboot the phone, before you get the correct time from the network. This build features TimeKeep, so the problem is back again. Very weird, I'll try to look into it. If you're willing to help, send me a PM.

Sure thing. The OTA updater will download my unofficial builds instead of the official ones.
[ONE Android Development] tpuserhp:
Is the 18.1 lockscreen PIN issue related to the use of certain feature like Microg?

I'm running 20201226 of 18.1 rom and I am not encountering any lockscreen PIN issue. Thanks.
[ONE Android Development] Tomoms:
This is very strange. The issue should be related to time services, which are present (or not present) in each build and you cannot add them or remove them without rebuilding. If you can accept the risk, please upgrade to the latest build and check if you're still fine or not.
[ONE Android Development] tpuserhp:
I'll take a backup and dirty flash the new build. Will update later.
[ONE Android Development] tpuserhp:
Dirty flashed 20210103 rom. No problem with entering lockscreen PIN. I'm using Magisk root and Nova Launcher's Device Admin Screen lock method. Not sure it plays a part or not. Also, I did not set up lockscreen pin initially after boot. I set it up later after I have confirmed my apps are all working.
[ONE Android Development] Tomoms:
Maybe the key is to set up the PIN after completing the initial setup, and not immediately, don't really know... I'll have to investigate on the issue a bit more.

To everyone else having the issue: can you please flash this zip and check if the problem persists?

Thanks.
[ONE Android Development] tpuserhp:
With 20210103 rom, I found that root was lost twice. So I restored it back to 20201226 rom backup for now.
[ONE Android Development] Tomoms:
What do you mean with root was lost "twice"? Can you elaborate a bit and tell me what you had done, and what has happened?
[ONE Android Development] SHAKEOFABIOMEN:
@Tomoms, I am currently on the official LineageOS 17.1. Are there any docs on how to switch to the 18.1 here?
[ONE Android Development] Tomoms:
I've learnt that the fact that the official builds are signed with different keys than my builds is not an issue. So I'd say that you just have to flash 18.1, flash Gapps, reboot, done :)

But I suggest that you don't upgrade yet. As you can read, there still are a few minor issues with 18.1, and I'm not able to tackle them quickly because I'm still on 17.1 as well.
[ONE Android Development] SHAKEOFABIOMEN:
ok, thank you for this. I will then wait for all the kinks to be resolved before II install this. Appreciate the quick reply
[ONE Android Development] tpuserhp:
I just dirty flashed the new ROM, wiped caches and rebooted. Tested out lockscreen PIN and other non rooted apps ok. But when I used the root apps, I found out root is gone. Magisk manager verified my device was not rooted. I rebooted hopefully the root problem could be fixed. But no dice. I could have flashed magisk again. But I didn't. Might try it next time.
[ONE Android Development] Tomoms:
This has happened to me too when using Magisk beta v21.1. Basically, the addon.d script didn't restore Magisk after updating the ROM. It seems to have been fixed on Magisk v21.2. Which version were you using?
[ONE Android Development] tpuserhp:
I'm using Magisk v 21.2. It could be the issue is not completely fixed yet. I will retry when magisk v21.3 is available. Thanks.
[ONE Android Development] GasLoop:
Yes, I've rebooted straight away. No clue why that happens. Going to just use the regular GApps then, it's not a biggie.

I have now installed TWRP 3.5.0, LOS 18.1 (Jan 3), OpenGApps (Jan 1) and Magisk v21.2. I had the problem that the camera was not recognised sometimes in the beginning but permanently later. Let's see if that problem will reappear.
[ONE Android Development] jvifdz:
Hello everyone!! I want yo ask you, what are the differences with your 17.1 ROM and official lineage 17.1?
[ONE Android Development] Tomoms:
To everyone: the lockscreen PIN issue seems to have been fixed in the last build, at least if you do a clean flash. I'll soon release a new build with January's security patches, so that the Android 11 flashing party can officially begin! No major issues should be present now :)

Everything is written in the first post. As a general rule, reading carefully the first post is recommended before asking anything, because really, many times the answer is already provided there :)
[ONE Android Development] GasLoop:
The problem persists... :( The camera is not being recognised on my device.
[ONE Android Development] Gold Ribbed:
I have been having problems with Twrp since 3.4. Backups do not work and phone goes to fast boot. However dirty flashing rod and gapps it then boots. Has anybody else had this issue?
[ONE Android Development] Tomoms:
Restoring /system from a TWRP backup is kind of messed on Android 10, TWRP 3.5 should fix the issue for at least part of the users but I wouldn't do it anyway.
[ONE Android Development] GasLoop:
Hey Tomoms any feedback on the camera issue?
[ONE Android Development] Tomoms:
You'll hear from me tomorrow :)
[ONE Android Development] GasLoop:
Aight, much appreciated!
[ONE Android Development] hystrix65:
I tried to install 17.1, I have problems with Nova Launcher, it isn't working very well
[ONE Android Development] Tomoms:
I've uploaded a new 18.1 build with January's security patches. Starting from the next one I'll implement my OTA updater, so upgrading will be easier.
[ONE Android Development] Tomoms:
New 17.1 build available, with January's security patches.

Please provide logcat & dmesg taken after trying to use some camera app.
[ONE Android Development] SairesArt:
Many thanks for the awesome support, even in 2021!

That's is not much info to go by^^
[ONE Android Development] jvifdz:
A lot of thanks for keeping this alive
[ONE Android Development] GasLoop:
I will. Jan 6 build worked so far. Thank you.
[ONE Android Development] ExbeeCZ:
I have last version of 17.1 and have problem with screen sharing (mirroring). I choose tv and after this phone reset system.

So mirroring not working.

Second problem was with sms notify. Probably when is phone in deep sleep I dont get SMS. After waking up i get notify that i get SMS before 20 minutes or etc.
[ONE Android Development] MurikBMX:
Hi. How can I enable dark mode on los-17.1? I'm trying enable but it BLACK mode
[ONE Android Development] Tomoms:
You're welcome :)

Screen mirroring is broken starting from 17.1 on all legacy devices. There's nothing anyone can do. If you need that feature, you have to stay on LineageOS 16.0. For the SMS problem, try to whitelist the SMS app in the Battery optimization settings, or switch to another SMS app such as QKSMS (it's open source and it works flawlessly for me).

Settings > Display > Dark theme. What's the problem? There's a toggle to use the "dark" version or the "full black" version.
[ONE Android Development] MurikBMX:
Only black version
[ONE Android Development] srdempster:
Qudos to the OP for a buttery smooth ROM, so far so good
[ONE Android Development] Tomoms:
Hmm... It's working fine for me! Perhaps you installed some substratum theme or other customization app that is interfering with that option?

Thanks! ;)
[ONE Android Development] MurikBMX:
I didn't install any customization apps.
[ONE Android Development] jvifdz:
One question it is possible to have this ROM but with default frequencies of The processor Or do you not recommed me that? Thanks!!
[ONE Android Development] Tomoms:
Of course you can. Just download some kernel tweaking app (I recommend Smartpack Kernel Manager) and use it to restore the maximum frequency to 2,5 GHz.
[ONE Android Development] jvifdz:
Can i use franco kernel mánager?
[ONE Android Development] Tomoms:
Sure.
[ONE Android Development] srdempster:
If you want me to beta test for you I volunteer my services!
[ONE Android Development] sbhajband:
Only one question from me after tested all builds 18.1 linageos, What's different or more in update?

Because I didn't see anything. Only ui?...
[ONE Android Development] sbhajband:
Sorry for my English!!

Linageos 18.1 vs Linageos 17.1

What's new??
[ONE Android Development] Tomoms:
You'll hear from me soon via PM :)

First of all, 18.1 is based on Android 11 while 17.1 is based on Android 10. Then, my 17.1 has several optimizations, tweaks and improvements that are not present on my 18.1, but I'll gradually add them over the next months.
[ONE Android Development] fireG:
Hey folks, can u give me link I need open gaps for latest Linageos 17.1. Thank you!
[ONE Android Development] Phantom Thief:
Great work, op! Glad to see this device is still alive and with a A11 release. :)
[ONE Android Development] jvifdz:
The Open GApps Project

OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.

opengapps.org
[ONE Android Development] jvifdz:
same here if u need help tell me!!
[ONE Android Development] Tomoms:
Hello, I've released a new 17.1 build. This one brings some kernel fixes & improvements and the full implementation of January's security patches. In fact, shortly after I built the previous build (20210108), two more related commits appeared on Lineage's Gerrit. So this new build brings the full set of security patches. The updater can be downloaded manually right now, but it won't appear in the OTA updater before tomorrow morning because I forgot to push it there.
[ONE Android Development] steve8x8:
Not having found that latest 17.1 build on AFH made me a bit uneasy (I usually keep that file listing page open, not the thread opener). Is there a special reason to move to SF, and will 18.1 also be moved?
[ONE Android Development] Tomoms:
Yes, there is a very specific reason, which is that with all due respect for giving us a free service, AFH sucks big time. It's soooo unstable and quirky! And the direct links to files change every few hours/days, breaking the OTA updater regularly. I'll soon move 18.1 on SourceForge as well.

Bookmark this link for future downloads: https://sourceforge.net/projects/lineageos-for-bacon/files/
[ONE Android Development] nullington:
What version baseband and modem are you guys using?
[ONE Android Development] Tomoms:
I have just realized I've never pushed the latest build to the OTA updater. Just did it now. Well, better late than never :)

The ones present in the last CyanogenOS 13 build.
[ONE Android Development] capt.ron:
Hi @Tomoms, I flashed your latest 17.1 rom and seemed to have lost root. I tried re-installing latest Magisk 21.3 with the manager and get the following error. Is this ROM related? Thanks for your input.

Nevermind, I should of flashed *. zip with twrp and not used the "select and patch a file" option in Magisk Manager.
[ONE Android Development] Tomoms:
I've had trouble with odd-numbered Magisk releases (21.1) as well. On the contrary, 21.2 has worked fine for me and survived across flashes normally. Now 21.4 has been released, you might as well try this new version. Anyway, 21.2 should work fine.
[ONE Android Development] dankovac1999:
Does this rom has any special installing procedure? Im getting zip signature verification failed error. Ive tried twrp 3.5 as well as 3.5. As long as thread search isnt available I just scrolled through few pages and havent find this problem :(

Update 1: My bad, Ive just realized I can turn it off :D

Update 2: I was able to fit nano gapps :)
[ONE Android Development] Tomoms:
Well, there should be no need to turn off signature verification. "Verification failed" could mean that the zip was corrupted during the download. Were you trying to install 17.1 or 18.1?
[ONE Android Development] dankovac1999:
I've turned that off and everything seems working fine. I've downloaded 17.1. It says the same with official build as well. But it doesn't with another unofficial. I will try to download it again. Thanks for your time!
[ONE Android Development] Tomoms:
If you kept the file after installing it, check whether the md5sum is '6a7c67d5fcc7e747d457cfa12c7ad225' (valid for 17.1, 2020-01-12 build). If it's not, redownload, recheck and reflash (no wipes needed, obviously) :)
[ONE Android Development] dankovac1999:
It's the same, what a mystery 😅 but hey it works, so I don't really care about it. Who knows what it wrong.
[ONE Android Development] Tomoms:
If it's the same md5sum, then there's nothing wrong. The recovery misbehaved and I don't know why, but let's not care about it.
[ONE Android Development] Tomoms:
A new 18.1 build is available! It brings some improvements and optimizations under the hood (both for the Android RunTime and for the sqlite & zlib libraries), and the latest updates from the LineageOS team. This build also supports my OTA updates: you'll be able to update to the next one via the Updater (right now, if you search for updates, you'll probably see an error, it's normal - it'll be fixed when the new build comes).

Starting from the next build, 18.1 will feature my custom kernel as well.
[ONE Android Development] PercevalSA:
Hello Nulligton,

I have the same issue. Did you manage to fix it?
[ONE Android Development] harvey186:
Hi, I want build it for my own. So could you please let me know which vendor sources you have used ??

thx
[ONE Android Development] Tomoms:
Hello! I've released a new 17.1 build because I've managed to fix manual mobile network search!

I plan to upload the fix to the official device tree soon :)

The Muppets'.
[ONE Android Development] indhimaga:
Anyone camera worked with latest 17.1?
[ONE Android Development] Gold Ribbed:
Mine worked after a restart
[ONE Android Development] capt.ron:
Mine is working
[ONE Android Development] Djiban:
Hello, thanks for the hard work. Do you mean that January 21st build is just waiting for the next builds to be available online, or the first next build will be the first one to really support OTA ?

Any idea of the date of next LOS 18.1 build uploads from you? So I'll tell you if OTA works fine for me.
[ONE Android Development] Tomoms:
Manual network search will be fixed in the next 18.1 build as well, and the fix has been merged into the official repos, so starting from the next official nightly it'll be working for everybody!

Exactly. If you install this Jan. 21st build, as soon as the new one comes out, you'll be able to update via the OTA Updater. I don't know when the next build will come, probably in 3 to 5 days. Keep an eye on this thread and you'll be up-to-date :)
[ONE Android Development] nullington:
Google play services did not work for me after dirty flashing to the 22. jan build. I flashed gapps manually and reinstalled some google apps to get my phone into a good state.
[ONE Android Development] nullington:
I did not.

I found a reddit post about a similar problem from more than 2 years ago and tried different modems/basebands as suggested there, but it still happens, perhaps less frequently though.

OnePlus One Baseband Report

Modems/basebands:

https://xdaforums.com/t/ref-radio-oneplus-one-modem-collection.2858734/

https://xdaforums.com/t/firmware-modem-all-in-one-zip-oneplus-one.3462214/
[ONE Android Development] Djiban:
thx for the fast answer !
[ONE Android Development] mrhamed:
How to fix ACCESS_BACKGROUND_LOCATION issue (not checked in microg of magisk) ?
[ONE Android Development] capt.ron:
Having same issue (latest 17.1)
[ONE Android Development] capt.ron:
This is the issue
[ONE Android Development] Djiban:
Did you plan to try other fix method, or no idea at the moment?
[ONE Android Development] altromass:
Hi. Is tethering working for you?
[ONE Android Development] Tomoms:
18.1 right? Tethering is broken but it'll be fixed in the next build, which is coming later today or tomorrow!
[ONE Android Development] greatestandroidfan:
On lineage-18.1-20210121-UNOFFICIAL-Tom-bacon-signed. Boot loop after enabling encryption. Tried /data with both ext4 and f2fs format. Any ideas?
[ONE Android Development] capt.ron:
Probably just let it go and hopefully it won't be a problem with 18.1 when I decide to update. Thanks
[ONE Android Development] Tomoms:
Hmm... I've never had issues with location permissions when using MicroG, maybe you can try these commands: https://xdaforums.com/t/rom-10-unof...dkey-fdroid-and-microg.4086371/#post-82401769

Replacing ACCESS_FINE_LOCATION with ACCESS_BACKGROUND_LOCATION...

Nope, sorry, but I'll get back to you with some debugging ideas. Maybe you were hit by these bugs: https://gitlab.com/LineageOS/issues/android/-/issues/2682 https://gitlab.com/LineageOS/issues/android/-/issues/2044
[ONE Android Development] Android-4-Life:
Currently, I am unable to get my OnePlus One 64GB working with the latest build of the LineageOS 18.1 ROM here. If I flash the ROM in TWRP either as just the ROM itself (no GApps) or with BiTGApps, the phone will boot into a blank black screen (I can still access the power menu to shut down or restart, access the emergency dialer screen, and I can see the volume pop-up if I press the volume buttons, but I can't use or access anything else); if I flash the ROM with the unofficial OpenGApps Android 11 pico package provided, my OnePlus One stays stuck on the white "Just a sec" screen with the spinning blue circle after selecting the language on the first screen.

So far, I have completely wiped my phone with TWRP (system, data, cache, internal storage), tried both EXT4 and F2FS file systems, updated from TWRP 3.3.1.0 to 3.5.0_9-0, have downloaded the ROM using two different computers on two separate Internet connections, have used two different known-working Micro USB cables to transfer the ROM onto the phone, done a clean reflash of the ROM in TWRP multiple times (completely wiping the phone each time before flashing), tried flashing older versions of the 18.1 ROM, and have restarted the phone multiple times after it boots; all without success in getting my OnePlus One to properly load this LineageOS 18.1 ROM.

Is there something that I'm missing here, perhaps? Is there anything else I should do or try to get this LineageOS 18.1 ROM working on my OnePlus One? Please note that before I tried flashing this ROM, my OnePlus One was working perfectly without issue on LineageOS 17.1. Also, I have never used any encryption on my OnePlus One.
[ONE Android Development] Tomoms:
Unfortunately I have to delay the new build a little bit. I hadn't got time to finish all the stuff I wanted to do before building. I guess the new update will come tomorrow or on Wednesday.

Hmm, this is very strange. I'd say, just wait for the new build, which is coming very soon, and try again.
[ONE Android Development] LonelyHarp:
@Tomoms could you please take a look at the last comment here

https://github.com/Pittvandewitt/Wavelet/issues/3
[ONE Android Development] Tomoms:
I think my LineageOS 16.0 ROM had got that commit. Now my 17.1 hasn't got it anymore IIRC, but Viper4Android FX is working totally fine for me, if you follow the link I put in the 2nd post of the thread. Are you facing any problem?
[ONE Android Development] LonelyHarp:
yes, im trying to use wavelett app and get this error. would it be possible to get this commit in 17.1?
[ONE Android Development] Tomoms:
Oh sorry, I saw the name "Pittvandewitt" and immediately associated it with Viper! Didn't realize you were talking about a different app :)

Sure thing, next 17.1 and 18.1 builds will come out very soon with this patch included :)
[ONE Android Development] LonelyHarp:
thanks! love this rom, keep up the good work!
[ONE Android Development] Android-4-Life:
Interestingly, I just tried two of your 2020 18.1 builds available on MEGA (20201221 and 20201229) and they work great on my OnePlus One as far as booting into LineageOS goes. If I do a dirty flash from a 2020 18.1 build to either 2021 18.1 build (20210106 or 20210121), I'll get stuck on "Phone is starting..." after going through the lock screen, and end up booting into a black screen as I previously described if I then use TWRP to wipe cache/dalvik. Looks like there's something with those two 2021 builds that my phone does not like, maybe the lock screen fix? (just a pure guess)

Anyways, thank you for responding! I look forward to trying out the new build, hopefully it'll work well. Also, thank you so much for continuing to support this legacy smartphone into the 2020s!
[ONE Android Development] Tomoms:
New 17.1 build is available, with that Dynamic processing library included. Please test it and let me know if it works.

18.1 is coming soon as well.
[ONE Android Development] Tomoms:
I've released a new 18.1 build with some interesting stuff. First of all, it brings all the features I've included in today's 17.1 build (F-Droid privileged extension and the Dynamic processing audio library). It also features my kernel, please test it and let me know how well it works for you (I'll move to 18.1 in a few days). The update should be available via OTA right now :)

@altromass tethering should work now.
[ONE Android Development] tpuserhp:
I tried ota update and also clean flashed just only 18.1 20210202 rom, but it always went to boot loops. I'd appreciate if you could try and see if this happens to you too. Thanks.
[ONE Android Development] sumitinhome:
new 18.1 build boot looped hard. dirty flash or clean flash it just bootloops.
[ONE Android Development] Tomoms:
I'm very sorry. I'll look into the issue in a few hours and I plan to release a fix later today.
[ONE Android Development] LonelyHarp:
it works, thanks
[ONE Android Development] Tomoms:
New build available, it works fine!

Nice :)
[ONE Android Development] hystrix65:
To me also 17.1 boot looped hard after dirt upgrade, i had to do a clean install. It's the first time it happens to me
[ONE Android Development] Tomoms:
This did not happen to me. All 17.1 builds have always worked perfectly, I've always dirty-flashed them. Unfortunately, reporting such bugs without adequate logs is useless, I cannot understand what went wrong.
[ONE Android Development] Pap0ose:
@Tomoms ..Merci pour la 18.1 qui fonctionne très bien ... ;)
[ONE Android Development] altromass:
Hi. I get a "signature verification" error. Can I install from ADB and ignore it?
[ONE Android Development] Tomoms:
Sure thing. You can disable the signature check in TWRP's settings as well.
[ONE Android Development] Tomoms:
What kind of bootloop do you experience? Are you stuck on the boot animation forever, or does the device reboot automatically after some time?
[ONE Android Development] greatestandroidfan:
Phone starts, LineageOS appears for ~20s, then reboots, loops forever
[ONE Android Development] Tomoms:
Please start up your phone, and when you feel it is about to reboot, press the Volume Down button and keep it pressed, so that the phone reboots to recovery instead. Then grab a copy of /proc/last_kmsg via adb. Then share that file here.