[ROM][OFFICIAL] LineageOS 17.1 weeklies for Xiaomi Mi MIX 2S

lixda

New member
Sep 8, 2009
4
1
23
Hi all, strange behaviour fount on lineageOS17.1 weeklies after the friday nov 13.

It seems that wearables like the WearOS application can't start and block on the splash screen.
I tried 2 builds, the 1st January one and the latest with the same behavior.
opengapps of 0210 build.

The result is that my fossil carlyle cant' connect to the phone.
Tried to reset the watch, factory reset the phone and do a clean flash with only LOS and the open gapps : same behavior.

Installed the 1113 LOS with 1113 open gapps : working.

My configuration : LOS17.1 - Magisk - OpenGapps.

logcat report such strange things like :

Strange isn't it. Seems to be related to changes made in the bt stack between mid november and 1st january. Or maybe related to opengapps.
Any idea ? Thanks.
I think there is something with opengapps. I have Xiaomi Redmi Note 5 Pro (whyred), last build 17.1 lineage-17.1-20210222-nightly-whyred, open_gapps-arm64-10.0-nano-20210220(20210213) and the same errors.
I installed opengapps 20210206, updated it from the market and the WearOS application starts. And right now connected a smartwatch. )
 

toxico914

Member
Aug 25, 2018
7
0
1
[QUOTE = "ioto, publicación: 84542295, miembro: 5155993"]
Utilizo el módulo Fullscreen / Immersive Gesture con Magisk para eliminarlo.
[/CITA]
GRAMOThanks, it worked perfectly.
 

XeeV

Member
May 29, 2011
8
0
21
Got the same bahaviour moving from 0115 to 0219. Moving back didn't help. I didn't wiped the data, did wipe the system only and flashed the recent gaps.

I did a ota update with rom lineage-17.1-20210122-nightly-polaris-signed.zip and i got a bootloop, after the lineageos logo, it went back to recovery (TWRP 3.3.1-1).

side loaded rom 20210115 (witch i came from), also boot loop..

then i f'ed up (reset to factory settings) instead of a wipe
wiped data and system
sideloaded 20210115 again
sideloaded gapps nano

restart system > after this i got a warning no os installed do u want to continue?
no problem after this.

now reconfigurating my phone, settings, reroot etc.


anybody got the same problems?
 

toxico914

Member
Aug 25, 2018
7
0
1
[QUOTE = "XeeV, publicación: 84545333, miembro: 4115696"]
Conseguí el mismo comportamiento moviéndome de 0115 a 0219. Retroceder no ayudó. No borré los datos, solo borré el sistema y mostré las brechas recientes.
[/CITA]
U Use the recovery from orange Fox, or the recovery from Linage if you want to avoid these problems after updating via OTA
 

quantuser

Member
May 5, 2017
26
19
3
I'm still on LOS 16 and finally want to upgrade. The wiki does not mention wiping anything just flashing the upgrade via TWRP or adb. Is that still fine (a year after release) or should I wipe some partitions?
I am also a bit late for the LOS 17.1 party and have the same question. Any recommendation on how to move from 16.0 (22Feb2020) to 17.1 with the least trouble?
 

pquinqu

Senior Member
May 7, 2007
108
118
83
Paris
I think there is something with opengapps. I have Xiaomi Redmi Note 5 Pro (whyred), last build 17.1 lineage-17.1-20210222-nightly-whyred, open_gapps-arm64-10.0-nano-20210220(20210213) and the same errors.
I installed opengapps 20210206, updated it from the market and the WearOS application starts. And right now connected a smartwatch. )
Agree. There's definitely something wrong with some OpenGapps packages. Installed the latest linageos build with an old known working opengapps package and, ... working. Thanks for the tip.
 

krischan941

Member
Feb 16, 2018
7
1
3
After latest Rom Update (2020-02-26) Lineage OS runs into bootloop and after that boots in twrp. Installing any previous version now gets the same behavior :/ Anyone else too?
 
Last edited: