• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][OFFICIAL][R] LineageOS 18.1 for Xiaomi Mi 10T / Mi 10T Pro / Redmi K30S Ultra [apollo/apollopro]

Search This thread

qilujiuliu

Member
Oct 24, 2017
6
0
Just to update everyone here. I wanted to tweak my phone a bit + update to the latest LineageOS so i did things step by step.

1) Changed my recovery to TWRP (https://forum.xda-developers.com/t/...r-mi-10t-mi-10t-pro-redmi-k30s-ultra.4319809/) instead of the Lineage Recovery - No issue, just that decrypting is slow...

2) Updated my firmware to the latest V12.5.4.0.RJDMIXM - After booting into the system, i keep getting connection drops, video lags, whole phone keeps hanging every now and then.

3) Updated to the latest Lineage OS 9 October - everything smooth sailing, no lags no hanging no crashing no random reboots. Have been using it the past 3 days. Except for "MAYBE" increased battery drain by a bit... But most likely because i've been playing a new game... I guess.
Hi, I got a little confused about the version of firmware to flash , if I'm going to flash the Lineage OS 10.16 build , should I flash the latest stable build of 12.5.5 for my k30s ultra or other version?
 

monsieurazizx

Member
Feb 2, 2015
37
2
How long should the first boot be? It's been going for 10 mins. It isn't bootlooping but it's been stuck on the boot animation.

I flashed Lineage Recovery 2021.10.16, updated to latest firmware V12.5.4.0.RJDMIXM, flashed Lineage OS ROM thru ADB sideload.

EDIT: It fixed itself. I rebooted back into recovery, formatted system partition again and found out that there was a problem with it, rebooted again and somehow was able to format system this time. Re-flashed the ROM and it worked. Very weird sequence of events.
 
Last edited:

_Fidor_

Member
Dec 13, 2014
23
1
I'm having weird issue. In case of incoming HD voice call sometimes there is no voice. Speaker act as it was muted. When switching to loudspeaker and then back to normal speaker then everything's is back to normal and I can hear remote person correctly.
Disabling wifi calling, volte does not help.
Anyone has encountered similar behavior?
 

laolang_cool

Senior Member
I'm having weird issue. In case of incoming HD voice call sometimes there is no voice. Speaker act as it was muted. When switching to loudspeaker and then back to normal speaker then everything's is back to normal and I can hear remote person correctly.
Disabling wifi calling, volte does not help.
Anyone has encountered similar behavior?
Same issue here. Are you using the latest LOS?
 

wiz.wiz

Senior Member
Oct 29, 2013
236
25
Toulouse
www.tournoidesdieux.fr
Hi, is someone using the latest build ? I am very late in updates...
Someone using the EU baseband ? Which version with that latest ROM ?
And are volte and vowifi working for you ?
thanks for your feedback
 

_Fidor_

Member
Dec 13, 2014
23
1
Hi, is someone using the latest build ? I am very late in updates...
Someone using the EU baseband ? Which version with that latest ROM ?
And are volte and vowifi working for you ?
thanks for your feedback
Yes,
Orange PL,
Volte/Vowifi works.
LOS from 23-X-2021
Baseband: c7-3033.23-0518_2104_59eed87dc7 (latest from 2021 Sep/Oct for EU)
 

wiz.wiz

Senior Member
Oct 29, 2013
236
25
Toulouse
www.tournoidesdieux.fr
Thanks !
I upgraded to :
FW EU : V12.5.7.0.RJDEUXM (latest, october)
LOS : 2021-10-30
Still no Vowifi :(
Is there a particular app/process to check ? permissions to allow to particular processes ?
(can't test VoLTE as I don't have 4G where I am now)
thanks !
 

_Fidor_

Member
Dec 13, 2014
23
1
Aside from enabling voWiFi is LOS settings (Advanced options in Mobile operator settings) I did nothing to get voWiFi working.
 

wiz.wiz

Senior Member
Oct 29, 2013
236
25
Toulouse
www.tournoidesdieux.fr
doing a "'logcat" I see the following :

process 2375 is org.codeaurora.ims


when desactivating:
11-04 18:47:12.570 2459 2917 I ImsCallbackAM [0]: Local callback added: [email protected]
11-04 18:47:12.594 2459 2917 I ImsCallbackAM [1]: Local callback added: [email protected]
11-04 18:47:16.651 2375 2405 W QImsService: ImsConfigImpl : VoWiFi mode: config update is done only when mode preference is changed or when sim is loaded
11-04 18:47:16.651 2375 2405 D ImsConfigImplBase: Set provision value of 27 to 1 failed with error code 1
11-04 18:47:16.651 2375 2405 W QImsService: ImsConfigImpl : Ignore VoWiFi Roaming enable/disable
11-04 18:47:16.651 2375 2405 D ImsConfigImplBase: Set provision value of 26 to 0 failed with error code 1
11-04 18:47:16.652 2375 5164 I QImsService: ImsRadioUtils : buildServiceStatusInfo srvType = 0 rat = 19 enabled = 0
11-04 18:47:16.652 2375 5164 I QImsService: ImsSenderRxr : [0252]> REQUEST_SET_SERVICE_STATUS [SUB0]
11-04 18:47:16.652 2375 5164 I QImsService: ImsSenderRxr : REQUEST_SET_SERVICE_STATUS to ImsRadio: token -252 RestrictCause:0
11-04 18:47:16.692 2375 3034 I QImsService: ImsRadioResponse : SetServiceStatus response received.
11-04 18:47:16.693 2375 3034 I QImsService: ImsSenderRxr : [0252]< REQUEST_SET_SERVICE_STATUS [ 1 1 0][SUB0]
11-04 18:47:16.693 2375 3036 I QImsService: ImsConfigImplHandler : Message received: what = 2


when activating:
11-04 18:48:08.071 2459 2917 I ImsCallbackAM [0]: Local callback removed: [email protected]
11-04 18:48:08.073 2459 2917 I ImsCallbackAM [1]: Local callback removed: [email protected]
11-04 18:48:08.134 2375 2405 W QImsService: ImsConfigImpl : VoWiFi mode: config update is done only when mode preference is changed or when sim is loaded
11-04 18:48:08.134 2375 2405 D ImsConfigImplBase: Set provision value of 27 to 2 failed with error code 1
11-04 18:48:08.135 2375 5164 I QImsService: ImsRadioUtils : buildServiceStatusInfo srvType = 0 rat = 19 enabled = 2
11-04 18:48:08.135 2375 5164 I QImsService: ImsSenderRxr : [0253]> REQUEST_SET_SERVICE_STATUS [SUB0]
11-04 18:48:08.135 2375 5164 I QImsService: ImsSenderRxr : REQUEST_SET_SERVICE_STATUS to ImsRadio: token -253 RestrictCause:0
11-04 18:48:08.136 2375 5164 W QImsService: ImsConfigImpl : Ignore VoWiFi Roaming enable/disable
11-04 18:48:08.136 2375 5164 D ImsConfigImplBase: Set provision value of 26 to 0 failed with error code 1
11-04 18:48:08.136 2375 5164 I QImsService: ImsService : enableIms :: slotId=0
11-04 18:48:08.136 2375 5164 I QImsService: ImsSenderRxr : [0254]> REQUEST_IMS_REG_STATE_CHANGE [SUB0]
11-04 18:48:08.136 2375 5164 I QImsService: ImsSenderRxr : REQUEST_IMS_REG_STATE_CHANGE request to ImsRadio - token:254 RegState1
11-04 18:48:08.137 2375 2405 I QImsService: ImsService : enableIms :: slotId=0
11-04 18:48:08.137 2375 2405 I QImsService: ImsSenderRxr : [0255]> REQUEST_IMS_REG_STATE_CHANGE [SUB0]
11-04 18:48:08.137 2375 2405 I QImsService: ImsSenderRxr : REQUEST_IMS_REG_STATE_CHANGE request to ImsRadio - token:255 RegState1
11-04 18:48:08.168 2459 2917 I ImsCallbackAM [0]: Local callback added: [email protected]
11-04 18:48:08.178 2375 3034 I QImsService: ImsRadioResponse : SetServiceStatus response received.
11-04 18:48:08.178 2375 3034 I QImsService: ImsSenderRxr : [0253]< REQUEST_SET_SERVICE_STATUS [ 1 1 1][SUB0]
11-04 18:48:08.178 2375 3036 I QImsService: ImsConfigImplHandler : Message received: what = 2
11-04 18:48:08.180 2375 3034 I QImsService: ImsRadioResponse : Got registration change response from ImsRadio.
11-04 18:48:08.180 2375 3034 I QImsService: ImsSenderRxr : [0254]< REQUEST_IMS_REG_STATE_CHANGE [SUB0]
11-04 18:48:08.181 2375 2375 I QImsService: ImsServiceSubHandler : Message received: what = 9
11-04 18:48:08.184 2375 3034 I QImsService: ImsRadioResponse : Got registration change response from ImsRadio.
11-04 18:48:08.185 2375 3034 I QImsService: ImsSenderRxr : [0255]< REQUEST_IMS_REG_STATE_CHANGE [SUB0]
11-04 18:48:08.185 2459 2917 I ImsCallbackAM [1]: Local callback added: [email protected]
11-04 18:48:08.185 2375 2375 I QImsService: ImsServiceSubHandler : Message received: what = 9
 

_Fidor_

Member
Dec 13, 2014
23
1
Just a wild guess: Are You passing Safety Net?

I'm using Magisk and I had to change fingerprint to emulate 10MiT (instruction are in thread).

Or Your operator does not support voWiFi?
 

wiz.wiz

Senior Member
Oct 29, 2013
236
25
Toulouse
www.tournoidesdieux.fr
Just a wild guess: Are You passing Safety Net?
In play store I see the phone is certified. I am assuming that is ok for safety net. Is that right ?
Otherwise how do I check ?
I'm using Magisk and I had to change fingerprint to emulate 10MiT (instruction are in thread).
I don't understand what you mean.
I am using Magisk and the phone is rooted.
I followed the description some pages ago to have the phone certified on google play.

Or Your operator does not support voWiFi?
My operator supports VoWifi, I tested the sim card in a "realme 8 pro" and right after I activated the feature, the phone was connected over wifi.
It really seems related to the phone SW

I see we do not have the same BB. I have c7-0177.2-1007_1958_b02d50f27d
 

Top Liked Posts

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


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

    Maintainers
    - Ramisky
    - SebaUbuntu

    Recommended firmware
    V12.1.3.0.RJDMIXM

    Downloads
    Here

    Flashing instructions
    Here

    Sources
    LineageOS

    Happy modding!
    8
    prosby přidat game turbo a herní centrum :)
    can't you write in English ?
    If everyone uses its native language it is going to be a huge mess...
    5
    Hello. Running the latest build on my Mi 10T Pro and everything is smooth as heck. Way better than any custom ROM I've tried and even better than Xiaomi.EU.
    But my only issue with it is that in the Play Store > Settings > About > Play Protect certification, it's listed as "Device is not certified". Because of this, I can't download some of my banking apps via the Play Store and some other apps. I don't want to sideload APKs. I contacted Play Store support about it and they couldn't help me. My Google Services Framework Android ID has already been registered so I should be certified.
    Do yours indicate the same and how have you been able to resolve this? Much help would be appreciated. Thanks.View attachment 5362653
    This basically means your device currently doesn't pass safetynet.

    Fortunately this is quite easy to fix. Follow these steps:
    1. FIrst of all you need to root using Magisk.
    2. Then you need to install Magisk module "Universal SafetyNet Fix" and "MagiskHide Props Config".
    3. Install any Terminal of your choice from the Google Play store.
    4. Open Terminal, type "su" (without quotes), grant SuperUser permissions.
    5. Type "props" (again without quotes), select "1 - Edit device fingerprint".
    6. Select "f - Pick a certified fingerprint".
    7. Select "30 - Xiaomi"
    8. Select either "27 or 30" (which is either 10t or 10t pro).

    Follow the onscreen instructions then reboot, make sure that google play services is currently checked in Magisk hide and you should be golden.

    Enjoy!
    4
    Already tried it and it still was only at 90hz show me a screenshot or get outta my posts
    Quit it. You're just embarrassing yourself. At least have some decency. There was absolutely no need for you to be rude especially not randomly 😂
    Screenshot_20210726-204109_Settings.png
    4
    And obviously I wouldn't use force 90hz you sound so dumb and take me for a fool?
    And yet it works just fine for all of us but you.. :LOL: