Updated the modem firmware tot the latest release, but that didn’t fix the issue.
I have no problem whatsoever with WiFi at home or at work.
I’m no WiFi expert, but I guess we need some input here for troubleshooting. For a start …
Well I don’t expect any problems with my WiFi network, I can honestly say that I know quite a bit about wireless networking.
- Ubiquiti Edgerouter X SFP
- 2x Ubiquiti UniFi AP-AC LITE
- 1x Ubiquiti UniFi AP-AC LR
- Both 2.4 and 5 GHz on channels with low interference with neighboring networks (band steering to 5Ghz)
The problem with the WiFi on my FP2 happend directly after updating to the newest release of LineageOS.
Oh, so upgrading from 15.1 to 16.0 triggered the issue? I didn’t get that, sorry.
Did you upgrade leaving data and Apps in place, or did you delete everything to install from scratch?
Almost correct ;-). Updating my 16.0 installation to the newest release triggered the issue.
You do realize there are daily (or better: nightly) releases for LineageOS 16.0? Hence my confusion.
The newest release is yesterday’s release, if not today’s, depending on the hour .
But in this case: Which build triggered the issue for you?
Around that date, many wifi security fixes were added Lineage 16 - wifi
Maybe this broke something. @StevenHachel reported it fixes Apple router support (at least that’s what I understood)
I have no problems with WiFi so far.
Connections are stable and establishing a connection works without problems.
I use the LOS version from 11.07.2019 at the moment.
@WoBoW can you try to narrow down the problems? Use only 2.4 GHz for example, or channel width.
Can you also provide logcat and dmesg output when it happens?
Something different: in the past I checked the changelog to see which update included the monthly security patches. It used to be sufficient to search for “bump security string to XXX” or something similar.
The last couple of months that has changed and I don’t know how to identify which update is the one with the security patches.
Does anyone know how to find out nowadays?
That actually leaves me more confused than before.
It shows a timestamp of “by on 12:01AM - 14 May 19 UTC”
How can the July security patch be committed in May?!?
It might sound stupid, but it also doesn’t answer any of the following questions I’m gonna ask myself next month when I want to know which update will contain the August patch
- Starting at https://download.lineageos.org/FP2/changes/, how do I find out which release contains the commit “Update Security String to 2019-08-05”
- Or the other way round: how do I find the commit that says “Update Security String to 2019-08-05” (ok, maybe checking https://github.com/LineageOS/android_build/blob/lineage-16.0/core/version_defaults.mk every day starting from 5th of August)
- and once I know the commit, how to find out which release it will be part of (maybe the next day? the day after that?)
I tried to upgrade from LoS 15.1 with TWRP 3.2.3-0 by formatting /system and installing zip lineage-16.0-20190713-nightly-FP2-signed.zip.
After reboot I’m getting
Fehler bei der Verschlüsselung. Das von dir eingegebene Passwort ist korrekt, aber deine Daten sind beschädigt. Damit du dein Spartphone weiterhin verwenden kannst, musst du es auf die Werkseinstellung zurücksetzen…
I gess their is a problem because my card is encrypted!?
LineageOS 15.1 did still work with encryption already done with LineageOS 14.1.
LineageOS 16.0 doesn’t anymore, and this is the message you get in this case.
I can’t find an option to decrpyt my phone. Do I have to format all data?
If you want to have 16.0, yes.
If you don’t have a backup of your important data yet, TWRP 3.2.3 should be able to access the data partition with the old encryption, and you could backup Internal Storage via USB and the rest of the data partition via TWRP backup (which doesn’t include Internal Storage).
Or perhaps an install of 15.1 without wiping anything could get you back to a working Android, but I don’t know myself whether that works.