[ROM][DISCONTINUED] LineageOS 17.1 for Xiaomi Mi MIX 2S

Search This thread
Broken Xiaomi Mi Mix 2S 2021-01-08 Update

Hello, just installed latest update lineage-17.1-20210108-nightly-polaris which broke up my microphone and speaker.
Yeah, I confirm too. Makes the main reason for having a phone kinda useless lol
also no sound here, not from speaker or through bluetooth.
Yup, same here, no sound in our out after lineage-17.1-20210108-nightly-polaris.
Same here .I went back to 20210101 and got my sound back
Yeah, downgrading worked for me as well.

Thanks for the reports guys. :cool: 👍

I wonder if the maintainer of the Xiaomi Mi Mix 2S polaris @bgcngm is aware of those reports?
***

Edit: All LineageOS build 20210108 were removed from the LineageOS servers. Thank you devs!
***
 
Last edited:

hathlife

New member
Apr 6, 2017
3
0
It seems that Jan 9 update not just break the sound, accurately there's something that nuked the whole media decoding component, you can only watch 720p quality on YouTube since the HW decoder is also broken. And I saw something relate to media decoding in the changelog. Maybe a regression?
 

cos4

Member
Feb 11, 2019
9
1
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?
 

ioto

Senior Member
Mar 4, 2013
55
6
Excuse me for my ignorance, so It doesn't really matter for LineageOS to have updated MIUI blobs to the latest one available from Xiaomi? Being that either V12.0.3.0.QDGMIXM or V12.0.2.0.QDGCNXM vs V11.0.5.0.QDGMIXM @bgcngm

P.S: Nevermind I just found out you updated them a month ago.
 
Last edited:

m0d

Senior Member
Nov 3, 2010
1,096
436
P.S: Nevermind I just found out you updated them a month ago.

That is for 18.1 branch not 17.1.



The other thread:





# Device proprietary files - from polaris' MIUI package V11.0.5.0.QDGMIXM global stable version
 

habsnurker

New member
Jan 9, 2021
3
1
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?
 

pquinqu

Senior Member
May 7, 2007
108
118
Paris
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 :
02-10 17:57:23.548 16650 16650 W BluetoothAdapter: getBluetoothService() called with no BluetoothManagerCallback
02-10 17:57:23.549 3084 3851 I bt_stack: [INFO:port_api.cc(123)] RFCOMM_CreateConnection BDA: ff:ff:ff:ff:ff:ff
02-10 17:57:23.552 16650 16650 W DeviceManager: Failed to connect to GoogleApiClient: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null, message=null}
02-10 17:57:23.562 16650 16701 E ThirdPartyChatAppSvc: ThirdPartyChatAppService: Intent { act=com.google.android.wearable.SYNC_ALL_3P_MESSAGING_APP_INFO cmp=com.google.android.wearable.app/com.google.android.clockwork.companion.messaging.ThirdPartyChatAppService }
02-10 17:57:23.563 16650 16650 W PermissionChecker: Need contacts permissions to register ContactsObserver.
02-10 17:57:23.564 16650 16650 W PermissionChecker: already checking this permission periodically
02-10 17:57:23.566 1343 3940 W ActivityManager: Unable to start service Intent { act=com.google.android.gms.wearable.BIND pkg=com.google.android.gms } U=0: not found
02-10 17:57:23.566 1343 3940 W ActivityManager: Unbind failed: could not find connection for android.os.BinderProxy@e688200
02-10 17:57:23.567 16627 16703 E GmsClient: unable to connect to service: com.google.android.gms.wearable.BIND on com.google.android.gms
02-10 17:57:23.579 1343 6213 W ActivityManager: Unable to start service Intent { act=com.google.android.gms.wearable.BIND pkg=com.google.android.gms } U=0: not found
02-10 17:57:23.580 1343 3217 W ActivityManager: Unbind failed: could not find connection for android.os.BinderProxy@fd3be2c
02-10 17:57:23.580 16627 16706 E GmsClient: unable to connect to service: com.google.android.gms.wearable.BIND on com.google.android.gms
02-10 17:57:23.589 1343 6213 W ActivityManager: Unable to start service Intent { act=com.google.android.gms.wearable.BIND pkg=com.google.android.gms } U=0: not found
02-10 17:57:23.589 1343 3217 W ActivityManager: Unbind failed: could not find connection for android.os.BinderProxy@7a06b30
02-10 17:57:23.590 16627 16699 E GmsClient: unable to connect to service: com.google.android.gms.wearable.BIND on com.google.android.gms
02-10 17:57:23.590 1343 3217 W ActivityManager: Unable to start service Intent { act=com.google.android.gms.wearable.BIND pkg=com.google.android.gms } U=0: not found
02-10 17:57:23.590 1343 6213 W ActivityManager: Unbind failed: could not find connection for android.os.BinderProxy@71673a9
02-10 17:57:23.590 16627 16703 E GmsClient: unable to connect to service: com.google.android.gms.wearable.BIND on com.google.android.gms
02-10 17:57:23.595 16627 16627 D Esim.Test: Parsing from file: /storage/emulated/0/Android/data/com.google.android.wearable.app/files/testConfig.json
02-10 17:57:23.596 16627 16627 E Esim.Test: Unable to read from file.
02-10 17:57:23.596 16627 16627 E Esim.Test: java.io.FileNotFoundException: /storage/emulated/0/Android/data/com.google.android.wearable.app/files/testConfig.json: open failed: ENOENT (No such file or directory)
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.
 

krischan941

Member
Feb 16, 2018
12
2
My magisk has vanished after updating to latest build. But installing magisk again works and so Adaway and my Bank trading app. 02-19-2021 rom
 

lixda

New member
Sep 8, 2009
4
1
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. )
 

Top Liked Posts

  • There are no posts matching your filters.
  • 36
    2okPze5.png

    LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), 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. 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.

    GPL compliance:
    yG18r6g.png
    Working:
    • Camera (and flashlight)
    • WiFi
    • NFC
    • Bluetooth
    • Telephony (Calls and Data)
    • IMS (VoLTE and WiFi Calling)
    • Audio (Record and Playback)
    • Video Playback
    • Sensors
    • GPS
    • Encryption (FBE)

    Broken:
    • Nothing (?)

    Compatibility:
    Compatible with all Xiaomi Mi MIX 2S variants.​
    Builds are based off the Xiaomi's Android 10 firmware with proprietary blobs from MIUI v11.0.5.0 global stable package.​

    Downloads:

    Notice:
    • No custom kernels are supported in this thread. Only stock kernel and official builds will be supported. No bug reports if that's not the case.

    Installation:
    • Reboot to recovery (TWRP recovery for Mi MIX 2S)
    • Format /system, /data and /cache
    • Install LineageOS zip package
    • Install [optional] a Google Apps package of your choice (Open GApps is advisable, but stock and super variants are not recommended!!!)
    Important notes:
    • * Required * firmware version must be based on MIUI Q-based builds.
    • GApps can only be flashed on clean installs.
    • Formatting data (all user data is wiped, including internal storage) is a must if MIUI was previously installed and device was encrypted.

    Credits & collaborations:
    All LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!​

    Device wiki:
    24
    New build is up, with January's ASB patches included.
    15
    Just for your info, I have just uploaded a new build that contains the boot image that fixes the deep sleep issues.
    13
    A new build is up, with a couple more features and this month's ASB merged.