[ROM][OFFICIAL][enchilada][12] LineageOS 19

Search This thread

mm-privacy

Member
Aug 26, 2021
12
2
Hello - WiFi not working

any idea why my OP6 with LOS 18.1 and 19.1. (as well as /e/) has a problem with the WiFi. every time when I want to switch WiFi on, the button jumps back a couple of seconds later.

I have tried different methods to install LOS but without success.

Usually I go back to stock rom with msmdownloadtool, installing the latest (and last) version of OOS. Of course, now WiFi is working:-(

Any idea what I can do?
 

lm089

Senior Member
No idea really; just a very wild guess since I don't know how you started in the first place: could it be that your firmware is not correctly installed? Maybe (re-) check these firmware installation instructions. Also be sure to observe any warnings in there.
Or - if you want to start from scratch (maybe to be recommended) make sure latest OOS V11 is flashed to *both* slots, then go on flashing LOS. Never forget to wipe data. Comprehensive instructions can be found all over this thread here as well as in the LOS instruction pages.
Good luck!
 

al1024

New member
Jan 17, 2016
1
0
Hi,
Is this version include OMAPI ?
OnePlus remove OMAPI functionality from their Android 11 Stock ROM.
 

Spaceoid

Senior Member
Mar 29, 2013
348
120
Dortmund
A second comment on the recently new behaviour of the stock gallery app. It's a minor 'issue' though.
I like to change my background images frequently. Up till two weeks ago, I could do so by just opening an image in the stock gallery app, entering the top right menu and selecting "Set as..." and "Nova background image" (I use Nova launcher).
For two weeks now the menu option has completely vanished. I have to enter the LOS settings, go down to the Design, Wallpaper menu, click "Change wallpaper", and then I have to search for the image file in the file browser. If I select the system gallery for image selection instead, my background image is shifted to the complete right, no matter which part of the image I select as a wallpaper.

I assume this is due to a new gallery app version? I wonder though why the gallery devs (I assume the AOSP devs) would remove the option to set a wallpaper. Anybody here experiencing similar behaviour or knowing a better workaround? 🤔
Just to end this topic - I checked LOS patch notes of the two recent weeks, and it seems Gallery2 function "Set as" was dropped intentionally due to a bug. So I assume to replicate the possibility to change wallpaper through gallery, one needs a different gallery now.
 

mm-privacy

Member
Aug 26, 2021
12
2
No idea really; just a very wild guess since I don't know how you started in the first place: could it be that your firmware is not correctly installed? Maybe (re-) check these firmware installation instructions. Also be sure to observe any warnings in there.
Or - if you want to start from scratch (maybe to be recommended) make sure latest OOS V11 is flashed to *both* slots, then go on flashing LOS. Never forget to wipe data. Comprehensive instructions can be found all over this thread here as well as in the LOS instruction pages.
Good luck!
Hello,

followed the firmware installation instruction but :

>sudo fastboot flash --slot=all abl abl.img
fastboot: error: Could not check if partition abl has slot all

>sudo fastboot flash --slot=b abl abl.img
Warning: abl does not support slots, and slot b was requested.
Sending 'abl' (2132 KB) OKAY [ 0.067s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed

>sudo astboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.001s
>sudo fastboot flashing unlock_critical
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed


Well, no luck.

I also installed OOS with twrp to make sure both slots have been updated (is there any way to check this?). Afterwards I installed /e/ (lineage fork) but with the same result - WiFi is not working.

Any other idea?
 

lm089

Senior Member
Sorry, no idea what is going wrong with the LOS-way to re-install firmware. It's a while that I last tried that, but back then it worked fine. But be aware that these instructions where written for LOS itself, other ROMs may have different layouts and partitions.
And: no clue what type of fork ("/e/") you mean. "fork" means a branched-off version of this LOS build here, right? just did a quick search on "/e/", apparently it's a LOS fork (started 4 years ago? At first glance I didn't find anything younger than 2018...). So apparently you're *not* using this build here >> LOS 19.1. Maybe you have more luck finding a solution in a different ("/e/" related) thread / forum / telegram group / whatever?

I also installed OOS with twrp to make sure both slots have been updated (is there any way to check this?).
basic idea is to boot into recovery (TWRP if you like) then flash OOS, make sure you still have the same recovery available, then reboot to recovery and repeat the above steps incl reboot to recovery. After each "flash" > "rebbot" sequence the slot should have changed, that's how you know that OOS was flashed to the now-active slot. Only after that you proceed with wiping and flashing your ROM etc.
There are numerous posts in this and other related threads describing the procedure; here's how I proceed: https://forum.xda-developers.com/t/...12-lineageos-19.4437321/page-16#post-87010019
 
Last edited:

mm-privacy

Member
Aug 26, 2021
12
2
Sorry, no idea what is going wrong with the LOS-way to re-install firmware. It's a while that I last tried that, but back then it worked fine. But be aware that these instructions where written for LOS itself, other ROMs may have different layouts and partitions.
And: no clue what type of fork ("/e/") you mean. "fork" means a branched-off version of this LOS build here, right? just did a quick search on "/e/", apparently it's a LOS fork (started 4 years ago? At first glance I didn't find anything younger than 2018...). So apparently you're *not* using this build here >> LOS 19.1. Maybe you have more luck finding a solution in a different ("/e/" related) thread / forum / telegram group / whatever?


basic idea is to boot into recovery (TWRP if you like) then flash OOS, make sure you still have the same recovery available, then reboot to recovery and repeat the above steps incl reboot to recovery. After each "flash" > "rebbot" sequence the slot should have changed, that's how you know that OOS was flashed to the now-active slot. Only after that you proceed with wiping and flashing your ROM etc.
There are numerous posts in this and other related threads describing the procedure; here's how I proceed: https://forum.xda-developers.com/t/...12-lineageos-19.4437321/page-16#post-87010019
Hello again,

thank you.

Of course I followed your link and made sure to install OOS in both slots. I have used the SW versions you have used. LOS 19.1 (nightly) is up and running (with twrp and magisk) BUT again without wifi... after trying to activate wifi, it takes a while and sometime the error message appears: system-ui is not responding, close app or wait... it does not matter what you click, wifi is off afterwards.

Besides installing OOS (11.1.2.2) in both slots - is there another way to check the firmware version in both slots? Somehow this is currently my last idea, because the wifi HW is working with OOS but not with LOS...

:-(
 
Last edited:
Jan 8, 2014
43
13
From what preivious version did you start?
Are you sure you're really in fastboot(d) mode?
Are your android tools (adb, fastboot) up to date?

sudo should not be necessary at all.

I just did the update from latest 18.1 using adb/fastboot at version 29.0.6.
Worked as expected.
 

lm089

Senior Member
Somehow this is currently my last idea, because the wifi HW is working with OOS but not with LOS...
Sorry, I'm lost in that case is as well. Only idea coming to my mind is that probably something went wrong somewhere during the entire process. Just to be sure let me repeat:

1. boot to twrp, check current slot (let's say you currently are in A), flash OOS, flash current twrp then reboot to recovery
2. back in twrp check current slot again, you should be in B now (or in A if before you were in B). Now again flash OOS; no need to flash current twrp again, instead reboot to recovery
3. you should now be in LOS recovery which allows you to do a proper factory reset / format data etc. (current twrp versions apparently cannot do this, at least it never worked on my OP6)
4. from LOS recovery follow instructions to flash current LOS 19.1. After that reboot to recovery again
5. back in LOS recovery flash some gapps solution (MindTheGapps is recommended; I flashed NikGapps but that apparently has some minor issues with LOS; you decide).
6. Now it's time to boot to system. You now should now do a basic LOS setup. Make sure you don't set any screen locking (pattern, pin whatever) yet; do that as the very last step.
7. After that check whether you have Wifi. >> if Wifi is still giving you trouble I'm out, no more ideas

Else you can continue like this:

8. In case you now are having proper Wifi and everything else you can think of,reboot to *bootloader* then start *fastboot* on your PC and boot into TWRP (in case you want TWRP instead of LOS recovery):
Code:
fastboot boot twrp.img
Once you're in TWRP recovery you can set that up. Go to "Advanced" and choose "flash current twrp", then reboot to recovery. That should be TWRP now, and you should have unencrypted access to data
9. reboot to system and continue setting up

Good luck once again
 

mm-privacy

Member
Aug 26, 2021
12
2
From what preivious version did you start?
Are you sure you're really in fastboot(d) mode?
Are your android tools (adb, fastboot) up to date?

sudo should not be necessary at all.

I just did the update from latest 18.1 using adb/fastboot at version 29.0.6.
Worked as expected.
Hello,

1) from what previous version - I have to admit I am not sure, I think it was 18.1
2) really in fastboot - yes, I always check with fastboot devices before I start
3) android tool - it is version:
Android Debug Bridge version 1.0.41
Version 32.0.0-8006631
Hope this version has no issues with OP6?

without sudo I do get error messages, but with sudo it seems fine (working on a LMDE5)
 

mm-privacy

Member
Aug 26, 2021
12
2
Sorry, I'm lost in that case is as well. Only idea coming to my mind is that probably something went wrong somewhere during the entire process. Just to be sure let me repeat:
thank you for four support - of course I do it again:
1. boot to twrp, check current slot (let's say you currently are in A), flash OOS, flash current twrp then reboot to recovery
- boot into twrp version 3.6.2_11-0-enchilada
- OOS 22.J.62_OTA_0620_all211125... flashing to inactive slot A
- flash twrp version 3.6.2_11-0-enchilada
- reboot to recovery
2. back in twrp check current slot again, you should be in B now (or in A if before you were in B). Now again flash OOS; no need to flash current twrp again, instead reboot to recovery
- OOS 22.J.62_OTA_0620_all211125... flashing to inactive slot B
- reboot to recovery
3. you should now be in LOS recovery which allows you to do a proper factory reset / format data etc. (current twrp versions apparently cannot do this, at least it never worked on my OP6)
=> Issue - this is OOS recovery !!!
- wipe data/cache - reset system setting (data & cache) - yes
- erase everything - yes
4. from LOS recovery follow instructions to flash current LOS 19.1. After that reboot to recovery again
- from OOS recovery I do not have adb/fastboot access to my OP6

Which steps do you recommend now?


5. back in LOS recovery flash some gapps solution (MindTheGapps is recommended; I flashed NikGapps but that apparently has some minor issues with LOS; you decide).
6. Now it's time to boot to system. You now should now do a basic LOS setup. Make sure you don't set any screen locking (pattern, pin whatever) yet; do that as the very last step
7. After that check whether you have Wifi. >> if Wifi is still giving you trouble I'm out, no more ideas

Else you can continue like this:

8. In case you now are having proper Wifi and everything else you can think of,reboot to *bootloader* then start *fastboot* on your PC and boot into TWRP (in case you want TWRP instead of LOS recovery):
Code:
fastboot boot twrp.img
Once you're in TWRP recovery you can set that up. Go to "Advanced" and choose "flash current twrp", then reboot to recovery. That should be TWRP now, and you should have unencrypted access to data
9. reboot to system and continue setting up

Good luck once again
 

lm089

Senior Member
Which steps do you recommend now?
Ok; can't remember what OOS recovery looks like. You need to get into bootloader. If that's possible from OOS recovers, fine. Else you can reboot to OOS system, from there into bootloader. Then follow LOS instructions: https://wiki.lineageos.org/devices/...rily-booting-a-custom-recovery-using-fastboot. Goal is to flash LOS from LOS recovery. Then as described above

Update:
Just re-read my last post describing what you could try. And some steps are missing there, don't know how that happened. Really sorry for that. Anyways, you need to get into bootloader then use fastboot to temp flash LOS recovery to boot, as described in the LOS instructions, then continue from there. Again check LOS instruction on how to start bootloader if you want to double-check
 
Last edited:

mm-privacy

Member
Aug 26, 2021
12
2
thank you for four support - of course I do it again:

- boot into twrp version 3.6.2_11-0-enchilada
- OOS 22.J.62_OTA_0620_all211125... flashing to inactive slot A
- flash twrp version 3.6.2_11-0-enchilada
- reboot to recovery

- OOS 22.J.62_OTA_0620_all211125... flashing to inactive slot B
- reboot to recovery

=> Issue - this is OOS recovery !!!
- wipe data/cache - reset system setting (data & cache) - yes
- erase everything - yes

- from OOS recovery I do not have adb/fastboot access to my OP6

Which steps do you recommend now?
 

mm-privacy

Member
Aug 26, 2021
12
2
ok, continued:

- reboot into fastboot
- fastboot temp install LOS recovery
- in LOS recovery, format data/factory reset
- in LOS recovery, adb sideload to install LOS nightly
- reboot to LOS recovery, adb sideload to install Mindthegapps
- reboot to system now

LOS with mindthegapps up and running
but no WiFi (same problem, click on wifi button and after a while I get an error message of the button just jumps back to inactive)

Thank you for your time and great support!

I will install OOS again... and I will see what I am doing with my last OP mobile...
 

Chris Kerry

Senior Member
Nov 23, 2010
71
19
Shouldn't be necessary, just use the built-in updater.
What I do after applying an update and before reboot:
1. run Magisk module "Twrp_a_b_retention script" if you want to stick to using twrp
2. from magisk manager app install magisk to unused slot

Some say Magisk is sticky now between updates, but that extra steps is easy enough
The layout of GitHub is confusing for this retention script. Can't find any "download" button to simply get it.
Please could you (or someone else with it) help me by posting the TWRP_A_B_Retention script that you flash after applying OTA updates? Would be very much appreciated!
Thanks.
 
The layout of GitHub is confusing for this retention script. Can't find any "download" button to simply get it.
Please could you (or someone else with it) help me by posting the TWRP_A_B_Retention script that you flash after applying OTA updates? Would be very much appreciated!
Thanks.
Just flash this like any other magisk module before rebooting (and after applying an OTA update).
 

Chris Kerry

Senior Member
Nov 23, 2010
71
19
Just flash this like any other magisk module before rebooting (and after applying an OTA update).
I already have this (used it earlier in the process of setting up LOS19.1). However, it is not the TWRP_A_B_Retention script that is being advised (not just by lm089 but all over the internet).
Can't you just give me the link to download that one, please?
 

lm089

Senior Member
Not sure if I understand what you mean. I'm using a module that is offered by Fox's Magisk Module Manager (as Magisk gave up on having its own Module Manager). Either download latest version, or use a module version from your internal storage if available
 
Last edited:

lm089

Senior Member
ok, continued:

- reboot into fastboot
- fastboot temp install LOS recovery
- in LOS recovery, format data/factory reset
- in LOS recovery, adb sideload to install LOS nightly
- reboot to LOS recovery, adb sideload to install Mindthegapps
- reboot to system now

LOS with mindthegapps up and running
but no WiFi (same problem, click on wifi button and after a while I get an error message of the button just jumps back to inactive)

Thank you for your time and great support!

I will install OOS again... and I will see what I am doing with my last OP mobile...
Sorry to read that, and no big idea what else you could try.
Apparently you are willing to try several things, so maybe you could give this one here a shot:

It's A11 based, apparently a quite stable ROM (I tried it once for a few days). Probably worth trying whether Wifi is available there. But no promise of course...
 

Zys2017

New member
Jul 12, 2022
1
0
I flashed today's version from OOS, no google sync, the most recent version of receiving SMS delays happened to me here, I don't know if it's a problem for me or all of us.
 

Top Liked Posts

  • 1
    Sadly no,Play Store prevent me from install it and said that my device isn't compatible,weird 😶
    Sounds like a PlayStore attestation issue... Maybe check this video here to see if it helps: (Should work the same for Magisk 25)

    1
    Sounds like a PlayStore attestation issue... Maybe check this video here to see if it helps: (Should work the same for Magisk 25)

    Tks,I'll try it
  • 2
    Okay, I managed to restore the backup. I'll post my exact steps for reference, perhaps it'll help someone. Perhaps even future me, when I get into this mess again.

    TL;DR: Keep system installation zip for each backup you wish to be able to restore.

    So, I had two backups, newer based on LOS from 28.06 and older based on LOS 15.06. I had an install zip with LOS version from 15.06, but I didn't have one from 28.06 and it was already gone from LOS download site.

    1. First, I copied everything from internal storage onto my computer. This procedure will wipe data and sdcard so copy your twrp backups and other data to avoid losing it.
    2. Rebooted to fastboot (power+volume up)
    3. Flashed LOS recovery: fastboot flash boot ./lineage-19.1-20220615-recovery-enchilada.img
    4. Booted to recovery (from fastboot)
    5. Used factory reset option (this will wipe your data including internal memory, backup your data)
    6. Flashed the same version of LOS as was in the older backup adb sideload adb sideload ./lineage-19.1-20220615-nightly-enchilada-signed.zip (used install update option)
    7. Rebooted recovery (switches active slot)
    8. Flashed gapps adb sideload ./MindTheGapps-12.1.0-arm64-20220605_112439.zip
    9. Flashed again the same version of LOS as was in the older backup adb sideload adb sideload ./lineage-19.1-20220615-nightly-enchilada-signed.zip (now in the second slot)
    10. Rebooted recovery (switches active slot)
    11. Flashed gapps again adb sideload ./MindTheGapps-12.1.0-arm64-20220605_112439.zip
    12. Went through initial setup in the OS - didn't set any pin
    13. Rebooted to fastboot adb reboot bootloader
    14. Booted TWRP fastboot boot twrp-3.6.2_11-0-enchilada.img
    15. It didn't decrypt data partition
    16. Flashed TWRP: advanced -> flash current TWRP
    17. Rebooted recovery - it decrypted data now
    18. Sideloaded magisk (because I had it in my backup, not sure if that's needed) adb sideload Magisk-v25.0.apk
    19. Downloaded the older backup (with LOS from 15.06) onto the phone adb push ../2022-07-03--19-28-17_lineage_enchilada-userdebug_12_SQ3A22060500/ /sdcard/TWRP
    20. Restoring data alone didn't work (system didn't finish booting)
    21. Restoring boot, system, data worked
    22. Rebooted twice for proper working system
    Now I had a working system with a month old backup, but I wanted to restore the newer backup for which I didn't have the system install zip. I'm sure it worked by an accident but I'll post my steps. They were taken right after I confirmed that a month old backup is restored and is booting properly.
    1. First I switched to the other slot in TWRP.
    2. Made a backup of the key store so that TWRP will be able to decrypt data: adb pull /data/system/recoverablekeystore.db .
    3. Restored only data from the newer backup
    4. Restoring data overwrote the keystore so I backed this one up as well: adb pull /data/system/recoverablekeystore.db ./recoverablekeystore.db.from_backup
    5. Pushed original keystore (AFAICT this enables TWRP to decrypt the data): adb push ./recoverablekeystore.db /data/system/recoverablekeystore.db
    6. Rebooted to system, however it didn't finish booting
    7. Rebooted to recovery (it decrypted the data)
    8. Restored keystore from backup: adb push ./recoverablekeystore.db.from_backup /data/system/recoverablekeystore.db (effectively this is the same as restoring data from backup again at this point)
    9. Restored system and boot from newer backup
    10. Rebooted to system and it booted properly.
    Now, I'm certain that some of these steps are not needed, however I have a working system now and I can't spend any more time to narrow it down. It weird that it worked, since I tried similar steps while first flashing newest LOS (27.07) and when I restored system+boot I got into recovery bootloop.

    For now, it seems that the only working way to restore backup is to first have system installation zip. Perhaps some shenanigans with keystore could work, but I couldn't work that out.

    Thanks to @lm089 and @tabletalker7 for their instructions.
    2
    I've also experienced the notification sound crackling issue, but only on first install.

    The first time I installed (maybe 3-4 builds ago), the OTP, trust, and setup notifications during/after the setup process were all very crackly. I tried calling the phone and sending it messages too, all the notifications crackled. Then I tried a media audio stream (YouTube video in the browser), and it sounded fine. Immediately after that, the notifications started sounding fine too.

    The next day I did another clean flash, and I had the same crackling notifications during the setup process. This time, I didn't try anything else, just started a Swift Backup restore and left my phone for half an hour. When I came back, the notification sounds were perfectly fine. 🤷‍♂️

    Edit: Forgot to mention, I have no problems with notifications now, and I leave my phone on ring mode for most of the day.
    2
    That got me thinking:
    Just tried to use the alert slider every other hour, and voila: No more issues until now.
    Although it's not a perfect solution, it works fine for me.

    Thanks a lot!
    So this evening I let my phone sit in loud mode for around 4 hours and did not notice any sound issue. Might be the time span was too small, or it is somewhat not a general problem...

    Edit: The same evening, I received a SMS without receiving a notification! I just saw it right now after opening the SMS app. First time it happens. As I read further above, this might be a kinda known issue. Still never happened to me before, and I communicate lots via SMS.
    Still, might also be I swiped the notification away by accident. :D

    Edit2: I found this regarding the SMS 'issue', which is quite interesting:
    https://www.reddit.com/r/LineageOS/comments/n5dttk Seems to be a long-known bug with the stock SMS app of LOS. Two different fixes are offered, too, either via ADB command or by switching to a different, third-party messaging app.
    1
    Sounds like a PlayStore attestation issue... Maybe check this video here to see if it helps: (Should work the same for Magisk 25)

    Tks,I'll try it
    1
    Clean flashed from OOS 11.2.2 following instructions from lineage wiki. No custom kernel or mods.

    Fingerprint stops working occasionally and goes back to normal after a reboot.

    Anybody else have this issue ?
    Dirty flashed previously from 18 to 19, applied last update from 26/07, fw 11.1.2.2, fingerprint working normally.
  • 37
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    Instructions :
    Downloads :
    Reporting Bugs
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

    Code:
    What is your--
    LineageOS version:
    LineageOS Download url:
    Gapps version:
    
    Did you--
    wipe:
    restore with titanium backup:
    reboot after having the issue:
    
    Are you using--
    a task killer:
    a non-stock kernel:
    other modifications:
    
    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
    6
    Just did a dirty flash from LOS 18.1 and everything works fine.

    I had to reinstall some Google apps (YouTube, Gmail, Keep, GCam, Photos), as they stopped working after the upgrade (maybe because I accidentally clicked No on the Signature verification failed screen while flashing Gapps and didn't notice, then the OS didn't boot. whoops. So I went back into the recovery and flashed Gapps again. Sure enough, the install went through. So be careful and make sure to click the correct button, lol)

    Everything else seems to work perfectly!

    Thanks again LuK for your work!

    In case anyone with Gapps and Magisk wants to try a dirty flash from 18.1, here are the steps I did:
    (you're on your own if things break! better to do a clean flash! magisk isn't officially supported!)

    1. Restored images in Magisk
    2. Removed PIN and fingerprints
    (Not sure if these first two steps are needed, but did them just in case)
    3. adb reboot sideload
    4. adb sideload lineage-19.1-20220426-nightly-enchilada-signed.zip
    5. Advanced->Reboot to Recovery
    6. Apply Update->Apply from ADB
    7. adb sideload MindTheGapps-12.1.0-arm64-20220416_174313.zip
    8. adb sideload Magisk-v24.3.apk
    9. Back->Reboot system now
    5
    I'm using a single SIM and I see the same thing often. I guess it depends on the amount of icons you have in the status bar. I observed this since the first build
    Change the smallest width to 411 in developer options.
    Before OOS 11 it was set to 411 by default but that changed with OOS11.
    4
    I'm on the May 17th enchilada nightly, and came directly from 18.1. I'd like to use ANT+, but no worky :confused:. Is this a known issue? Are there plans to fix it?

    ANT+ also didn't work when I went from 17.1 to 18.1, but I fixed it by upgrading the firmware. I tried that again on 19, but it didn't fix it this time.

    Here is what the ANT Tester app shows on LOS 19:

    View attachment 5619435
    4
    Question: Will there ever be more stable versions than the "nightlies"? I'm unsure where to put them in terms of quality and stability- should they be considered as "alpha" versions? Or are they even more reliable than "betas"?

    Thanks in advance.
    imo the first 2 nightlies were perfectly stable. No crashes, fc, excessive battery drain, whatever. (y)