MIUI 13 MIUI 13 STABLE RELEASE


K

Kolor

Members
May 22, 2017
41
20
I kindly ask you @Igor Eisberg and to the other developers to fix the problem of installing the Xiaomi Wear application in the ROMs of this forum.
I realize that it is a very boring job but, like me, there are other users who have a Xiaomi Watch S1 Active stopped because there are no ROM updates.
As there are no ROM updates for our devices, we cannot "Downgrade of MI Fitness to Health".

In my case, I have a Xiaomi 12 Pro and I have a Xiaomi Watch S1 Active.
As the last update for my Xiaomi 12 Pro was 1 month ago, I have my new smartwatch stopped for over 1 month.

On my old smartphone the Mi10 I managed to install the Xiaomi Wear application because on my Mi10 I use Weekly ROM. And I did the process that they explain in the article "Downgrade of MI Fitness to Health".
But I no longer use the Mi 10 as my daily phone.

I also know that, y'all have nothing to do with the lack of updates. But if you could help us with this problem, that would be great!
 
J

Jaffi

Members
Jan 7, 2022
7
15
I'm currently on Android 12 (MIUI 13) and no matter what custom DNS (say nextdns) I'm using, the phone is losing connection to certain apps and services when leaving my wifi and switching to mobile network. Weird thing is that it's only for certain apps and can be fixed by turning custom DNS off and on again.

Any ideas for what could be the culprit here?
 
moskito99

moskito99

Members
Oct 4, 2021
156
40
Stefanlong said:
+1
Same here with the first "xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.12.0.SKACNXM_v13-12-fastboot"....
no selection brings a change whether "video","photo" or "none" is selected - very strange You have already reported using the rebuild version but nothing has improved...
CORRECT !?
Click to expand...
Handling of burst mode has changed.

you need to slide the shutter button to left or right to start burst mode.

I still would prefer option to simply hold the shutter button for burst mode as before because burst mode pictures by sliding shutter button might make pictures less stable. Video below

photos.app.goo.gl

New video by Jan

photos.app.goo.gl photos.app.goo.gl
 
Last edited:
  • Like
Reactions: Tecalote and Stefanlong
Stefanlong

Stefanlong

Members
Feb 28, 2022
38
20
moskito99 said:
Handling of burst mode has changed.

you need to slide the shutter button to left or right to start burst mode.

I still would prefer option to simply hold the shutter button for burst mode as before because burst mode pictures by sliding shutter button might make pictures less stable. Video below

photos.app.goo.gl

New video by Jan

photos.app.goo.gl photos.app.goo.gl
Click to expand...
THX - Super worked very well.... ✌
 
Last edited by a moderator:
  • Like
Reactions: Tecalote and moskito99
TuxLin

TuxLin

Members
May 15, 2022
7
5
Jaffi said:
I'm currently on Android 12 (MIUI 13) and no matter what custom DNS (say nextdns) I'm using, the phone is losing connection to certain apps and services when leaving my wifi and switching to mobile network. Weird thing is that it's only for certain apps and can be fixed by turning custom DNS off and on again.
Any ideas for what could be the culprit here?
Click to expand...
I think it might be an issue unrelated to your DNS.
There is a setting in the "Developer Options" which keeps the mobile connection active when you turn on WiFi.
Maybe you could try this.
 
  • Like
Reactions: Jaffi
R

RSBG1

Members
Apr 29, 2022
5
3
Hi All,

Please accept my apologies if this topic has been discussed before - I just can't find anything about. Briefly: After MIUI 13.0.10 update, wireless charging stopped working. Is that a bug or just a matter of settings? Thanks in advance for your kind support!
Xiaomi Mi 11 pro
 
L

LiamJ74

Members
Jul 11, 2021
2
13
Bug found on Xiaomi mi 11. Just updated yesterday, and wired controller not working (was working fine on MIUI 12.5), especially gamesir X2. working on another phone with A12 inside.
 
Stefanlong

Stefanlong

Members
Feb 28, 2022
38
20
RSBG1 said:
Hi All,

Please accept my apologies if this topic has been discussed before - I just can't find anything about. Briefly: After MIUI 13.0.10 update, wireless charging stopped working. Is that a bug or just a matter of settings? Thanks in advance for your kind support!
Xiaomi Mi 11 pro
Click to expand...
MI 11pro 13.0.10, 13.0.12 first release and 13.0.12 final worked fine for me - no bug ...
 
L

lidicoxe

Members
Oct 27, 2019
8
13
I have a Redmi Note 11 with Xiaomi.eu 13.0.9, which I flashed over a month ago.
Checking the latest version today, I see its the "V13.0.7.0"

Should I "update"? Can I update without losing data, considering its a fastboot rom?
 
zsoltip

zsoltip

Members
Mar 9, 2022
2
3
Hello Forum Members!
I would like to sum up some recent issues on which I still have not made progress, and I would ask for your help.
I'm on Mi Note 10, MIUI 13.0.1 stabil ROM.

1.) "Can't use this folder. To protect your privacy, choose another folder."
I want to save the Download folder as the default folder for the Canon scanner, which has gone so far. Now, clean MIUI 13.0.1 ROM after installation, seems more thing has changed.
What's the solution to this folder story?
Wothout root, if possible.

2.) Also a protection function, which has been experienced in previous versions, but is still unchanged: Show the example
Its off status is indicated by the status of the "Settings, Developer Options," Notify about high risk feature "switch, but they still pop up at some settings. How do I turn it off?

3.) The Screen sharing / Wireless display option has been added to the quick access shortcut icons on a previous system. (No, I don't mean Cast.)
How can this be achieved?
""Go to developer options and enable wireless display certification.
Than go to "connection and sharing"/"wireless display and enable wireless display.
Now you see some stuff. Go to "operating channel" and change from auto to 6 or 11.""
This button was an easier way to go to this settings point.


Thanks
zsoltip
 
Last edited:
Igor Eisberg

Igor Eisberg

Developer
Staff member
Oct 6, 2016
7,316
322
  • Like
Reactions: hector.dv and elvisaloha
H

hellfreezover

Members
Aug 29, 2015
486
52
Hi,
Thanks fkr the Miui 13 foe Mi Note 10 lite.
Overall runs pretty cool.
I noticed the mi fitness app, replaces mi health.
The pre-installed version, is of ckurse "talking" in Chinese..
Additionally, there is a newer version on Goggle play, but can't be installed over the pre-installed one, without rooting a d deleting it...
Since I can't root, as i need to keep the security level high enough, i was wondering if it will be possible either to update the app with latest or allow the user to uninstall it, and install the google play one.
Thanks
H

Sent from my Mi 9 SE using Tapatalk
 
moskito99

moskito99

Members
Oct 4, 2021
156
40
On latest stable with Mi11 pro.

How is it possible that I did not get any notification on a message and missed video call from LINE messenger (like whatsapp, used in Asia/Thailand a lot) even I have no restrictions on power saving on the LINE app, autostart ON and notifications activated?

I saw both notifications just now ( 5 hours later) when I accessed the LINE app.

Thanks!
 
C

Casper99

Members
Jun 24, 2021
6
15
Hi,
I'm trying to update my Mi 11 @ 13.0.6 to 13.0.8 on my Mac. I copied the platform-tools contents into the 13.0.8 library and ran the updating script.

Code: 
Waiting for device...
##################################################################
Please wait. The device will reboot when installation is finished.
##################################################################
Setting current slot to 'a'                        OKAY [  0.040s]
Finished. Total time: 0.041s
Sending 'dsp_a' (65536 KB)                         OKAY [  1.688s]
Writing 'dsp_a'                                    OKAY [  0.130s]
Finished. Total time: 1.825s
Sending 'dsp_b' (65536 KB)                         OKAY [  1.618s]
Writing 'dsp_b'                                    OKAY [  0.165s]
Finished. Total time: 1.790s
Sending 'xbl_config_a' (216 KB)                    OKAY [  0.007s]
Writing 'xbl_config_a'                             OKAY [  0.002s]
Finished. Total time: 0.019s
Sending 'xbl_config_b' (216 KB)                    OKAY [  0.007s]
Writing 'xbl_config_b'                             OKAY [  0.002s]
Finished. Total time: 0.017s
Sending 'boot_a' (196608 KB)                       OKAY [  5.063s]
Writing 'boot_a'                                   OKAY [  0.439s]
Finished. Total time: 5.513s
Sending 'boot_b' (196608 KB)                       OKAY [  4.758s]
Writing 'boot_b'                                   OKAY [  0.406s]
Finished. Total time: 5.172s
Sending 'modem_a' (249180 KB)                      OKAY [  6.575s]
Writing 'modem_a'                                  OKAY [  0.546s]
Finished. Total time: 7.129s
Sending 'modem_b' (249180 KB)                      OKAY [  6.339s]
Writing 'modem_b'                                  OKAY [  0.513s]
Finished. Total time: 6.859s
Sending 'vbmeta_system_a' (4 KB)                   OKAY [  0.002s]
Writing 'vbmeta_system_a'                          OKAY [  0.001s]
Finished. Total time: 0.011s
Sending 'vbmeta_system_b' (4 KB)                   OKAY [  0.002s]
Writing 'vbmeta_system_b'                          OKAY [  0.001s]
Finished. Total time: 0.011s
Sending 'tz_a' (3680 KB)                           OKAY [  0.097s]
Writing 'tz_a'                                     OKAY [  0.009s]
Finished. Total time: 0.113s
Sending 'tz_b' (3680 KB)                           OKAY [  0.093s]
Writing 'tz_b'                                     OKAY [  0.009s]
Finished. Total time: 0.109s
Sending 'vbmeta_a' (4 KB)                          OKAY [  0.002s]
Writing 'vbmeta_a'                                 OKAY [  0.001s]
Finished. Total time: 0.010s
Sending 'vbmeta_b' (4 KB)                          OKAY [  0.002s]
Writing 'vbmeta_b'                                 OKAY [  0.001s]
Finished. Total time: 0.010s
Sending 'bluetooth_a' (1116 KB)                    OKAY [  0.030s]
Writing 'bluetooth_a'                              OKAY [  0.004s]
Finished. Total time: 0.043s
Sending 'bluetooth_b' (1116 KB)                    OKAY [  0.029s]
Writing 'bluetooth_b'                              OKAY [  0.004s]
Finished. Total time: 0.041s
Sending 'abl_a' (204 KB)                           OKAY [  0.007s]
Writing 'abl_a'                                    OKAY [  0.003s]
Finished. Total time: 0.017s
Sending 'abl_b' (204 KB)                           OKAY [  0.007s]
Writing 'abl_b'                                    OKAY [  0.003s]
Finished. Total time: 0.016s
Sending 'cpucp_a' (104 KB)                         OKAY [  0.004s]
Writing 'cpucp_a'                                  OKAY [  0.002s]
Finished. Total time: 0.014s
Sending 'cpucp_b' (104 KB)                         OKAY [  0.004s]
Writing 'cpucp_b'                                  OKAY [  0.003s]
Finished. Total time: 0.013s
Sending 'dtbo_a' (16384 KB)                        OKAY [  0.425s]
Writing 'dtbo_a'                                   OKAY [  0.037s]
Finished. Total time: 0.469s
Sending 'dtbo_b' (16384 KB)                        OKAY [  0.397s]
Writing 'dtbo_b'                                   OKAY [  0.044s]
Finished. Total time: 0.447s
Sending 'featenabler_a' (88 KB)                    OKAY [  0.004s]
Writing 'featenabler_a'                            OKAY [  0.003s]
Finished. Total time: 0.016s
Sending 'featenabler_b' (88 KB)                    OKAY [  0.004s]
Writing 'featenabler_b'                            OKAY [  0.003s]
Finished. Total time: 0.015s
Sending 'vendor_boot_a' (5888 KB)                  OKAY [  0.154s]
Writing 'vendor_boot_a'                            OKAY [  0.016s]
Finished. Total time: 0.178s
Sending 'vendor_boot_b' (5888 KB)                  OKAY [  0.146s]
Writing 'vendor_boot_b'                            OKAY [  0.016s]
Finished. Total time: 0.170s
Sending 'keymaster_a' (276 KB)                     OKAY [  0.008s]
Writing 'keymaster_a'                              OKAY [  0.003s]
Finished. Total time: 0.020s
Sending 'keymaster_b' (276 KB)                     OKAY [  0.008s]
Writing 'keymaster_b'                              OKAY [  0.003s]
Finished. Total time: 0.019s
Sending 'uefisecapp_a' (124 KB)                    OKAY [  0.005s]
Writing 'uefisecapp_a'                             OKAY [  0.003s]
Finished. Total time: 0.017s
Sending 'uefisecapp_b' (124 KB)                    OKAY [  0.005s]
Writing 'uefisecapp_b'                             OKAY [  0.003s]
Finished. Total time: 0.016s
Sending 'qupfw_a' (56 KB)                          OKAY [  0.003s]
Writing 'qupfw_a'                                  OKAY [  0.001s]
Finished. Total time: 0.012s
Sending 'qupfw_b' (56 KB)                          OKAY [  0.003s]
Writing 'qupfw_b'                                  OKAY [  0.001s]
Finished. Total time: 0.011s
Sending 'xbl_a' (3608 KB)                          OKAY [  0.094s]
Writing 'xbl_a'                                    OKAY [  0.006s]
Finished. Total time: 0.107s
Sending 'xbl_b' (3608 KB)                          OKAY [  0.088s]
Writing 'xbl_b'                                    OKAY [  0.006s]
Finished. Total time: 0.101s
Sending 'devcfg_a' (52 KB)                         OKAY [  0.003s]
Writing 'devcfg_a'                                 OKAY [  0.001s]
Finished. Total time: 0.011s
Sending 'devcfg_b' (52 KB)                         OKAY [  0.003s]
Writing 'devcfg_b'                                 OKAY [  0.001s]
Finished. Total time: 0.011s
Sending 'hyp_a' (3616 KB)                          OKAY [  0.092s]
Writing 'hyp_a'                                    OKAY [  0.011s]
Finished. Total time: 0.110s
Sending 'hyp_b' (3616 KB)                          OKAY [  0.087s]
Writing 'hyp_b'                                    OKAY [  0.011s]
Finished. Total time: 0.105s
Sending 'imagefv_a' (2048 KB)                      OKAY [  0.056s]
Writing 'imagefv_a'                                OKAY [  0.007s]
Finished. Total time: 0.071s
Sending 'imagefv_b' (2048 KB)                      OKAY [  0.055s]
Writing 'imagefv_b'                                OKAY [  0.007s]
Finished. Total time: 0.070s
Sending 'shrm_a' (48 KB)                           OKAY [  0.003s]
Writing 'shrm_a'                                   OKAY [  0.001s]
Finished. Total time: 0.011s
Sending 'shrm_b' (48 KB)                           OKAY [  0.003s]
Writing 'shrm_b'                                   OKAY [  0.001s]
Finished. Total time: 0.011s
Sending 'aop_a' (240 KB)                           OKAY [  0.008s]
Writing 'aop_a'                                    OKAY [  0.003s]
Finished. Total time: 0.017s
Sending 'aop_b' (240 KB)                           OKAY [  0.007s]
Writing 'aop_b'                                    OKAY [  0.003s]
Finished. Total time: 0.017s
Sending 'cust' (415132 KB)                         OKAY [ 11.090s]
Writing 'cust'                                     OKAY [  0.004s]
Finished. Total time: 11.103s
Sending sparse 'super' 1/9 (738592 KB)             OKAY [ 20.136s]
Writing 'super'                                    OKAY [  0.008s]
Sending sparse 'super' 2/9 (735128 KB)             OKAY [ 19.928s]
Writing 'super'                                    OKAY [  0.010s]
Sending sparse 'super' 3/9 (754584 KB)

It's been stuck on this line, 'super' 3/9, for 30 minutes. What to do, do I keep waiting? Will my device be bricked if I interrupt the installation? This has never happened to me before.
 
F

Franch

Members
Jan 21, 2022
44
20
Casper99 said:
Hi,
I'm trying to update my Mi 11 @ 13.0.6 to 13.0.8 on my Mac. I copied the platform-tools contents into the 13.0.8 library and ran the updating script.

Code: 
Waiting for device...
##################################################################
Please wait. The device will reboot when installation is finished.
##################################################################
Setting current slot to 'a'                        OKAY [  0.040s]
Finished. Total time: 0.041s
Sending 'dsp_a' (65536 KB)                         OKAY [  1.688s]
Writing 'dsp_a'                                    OKAY [  0.130s]
Finished. Total time: 1.825s
Sending 'dsp_b' (65536 KB)                         OKAY [  1.618s]
Writing 'dsp_b'                                    OKAY [  0.165s]
Finished. Total time: 1.790s
Sending 'xbl_config_a' (216 KB)                    OKAY [  0.007s]
Writing 'xbl_config_a'                             OKAY [  0.002s]
Finished. Total time: 0.019s
Sending 'xbl_config_b' (216 KB)                    OKAY [  0.007s]
Writing 'xbl_config_b'                             OKAY [  0.002s]
Finished. Total time: 0.017s
Sending 'boot_a' (196608 KB)                       OKAY [  5.063s]
Writing 'boot_a'                                   OKAY [  0.439s]
Finished. Total time: 5.513s
Sending 'boot_b' (196608 KB)                       OKAY [  4.758s]
Writing 'boot_b'                                   OKAY [  0.406s]
Finished. Total time: 5.172s
Sending 'modem_a' (249180 KB)                      OKAY [  6.575s]
Writing 'modem_a'                                  OKAY [  0.546s]
Finished. Total time: 7.129s
Sending 'modem_b' (249180 KB)                      OKAY [  6.339s]
Writing 'modem_b'                                  OKAY [  0.513s]
Finished. Total time: 6.859s
Sending 'vbmeta_system_a' (4 KB)                   OKAY [  0.002s]
Writing 'vbmeta_system_a'                          OKAY [  0.001s]
Finished. Total time: 0.011s
Sending 'vbmeta_system_b' (4 KB)                   OKAY [  0.002s]
Writing 'vbmeta_system_b'                          OKAY [  0.001s]
Finished. Total time: 0.011s
Sending 'tz_a' (3680 KB)                           OKAY [  0.097s]
Writing 'tz_a'                                     OKAY [  0.009s]
Finished. Total time: 0.113s
Sending 'tz_b' (3680 KB)                           OKAY [  0.093s]
Writing 'tz_b'                                     OKAY [  0.009s]
Finished. Total time: 0.109s
Sending 'vbmeta_a' (4 KB)                          OKAY [  0.002s]
Writing 'vbmeta_a'                                 OKAY [  0.001s]
Finished. Total time: 0.010s
Sending 'vbmeta_b' (4 KB)                          OKAY [  0.002s]
Writing 'vbmeta_b'                                 OKAY [  0.001s]
Finished. Total time: 0.010s
Sending 'bluetooth_a' (1116 KB)                    OKAY [  0.030s]
Writing 'bluetooth_a'                              OKAY [  0.004s]
Finished. Total time: 0.043s
Sending 'bluetooth_b' (1116 KB)                    OKAY [  0.029s]
Writing 'bluetooth_b'                              OKAY [  0.004s]
Finished. Total time: 0.041s
Sending 'abl_a' (204 KB)                           OKAY [  0.007s]
Writing 'abl_a'                                    OKAY [  0.003s]
Finished. Total time: 0.017s
Sending 'abl_b' (204 KB)                           OKAY [  0.007s]
Writing 'abl_b'                                    OKAY [  0.003s]
Finished. Total time: 0.016s
Sending 'cpucp_a' (104 KB)                         OKAY [  0.004s]
Writing 'cpucp_a'                                  OKAY [  0.002s]
Finished. Total time: 0.014s
Sending 'cpucp_b' (104 KB)                         OKAY [  0.004s]
Writing 'cpucp_b'                                  OKAY [  0.003s]
Finished. Total time: 0.013s
Sending 'dtbo_a' (16384 KB)                        OKAY [  0.425s]
Writing 'dtbo_a'                                   OKAY [  0.037s]
Finished. Total time: 0.469s
Sending 'dtbo_b' (16384 KB)                        OKAY [  0.397s]
Writing 'dtbo_b'                                   OKAY [  0.044s]
Finished. Total time: 0.447s
Sending 'featenabler_a' (88 KB)                    OKAY [  0.004s]
Writing 'featenabler_a'                            OKAY [  0.003s]
Finished. Total time: 0.016s
Sending 'featenabler_b' (88 KB)                    OKAY [  0.004s]
Writing 'featenabler_b'                            OKAY [  0.003s]
Finished. Total time: 0.015s
Sending 'vendor_boot_a' (5888 KB)                  OKAY [  0.154s]
Writing 'vendor_boot_a'                            OKAY [  0.016s]
Finished. Total time: 0.178s
Sending 'vendor_boot_b' (5888 KB)                  OKAY [  0.146s]
Writing 'vendor_boot_b'                            OKAY [  0.016s]
Finished. Total time: 0.170s
Sending 'keymaster_a' (276 KB)                     OKAY [  0.008s]
Writing 'keymaster_a'                              OKAY [  0.003s]
Finished. Total time: 0.020s
Sending 'keymaster_b' (276 KB)                     OKAY [  0.008s]
Writing 'keymaster_b'                              OKAY [  0.003s]
Finished. Total time: 0.019s
Sending 'uefisecapp_a' (124 KB)                    OKAY [  0.005s]
Writing 'uefisecapp_a'                             OKAY [  0.003s]
Finished. Total time: 0.017s
Sending 'uefisecapp_b' (124 KB)                    OKAY [  0.005s]
Writing 'uefisecapp_b'                             OKAY [  0.003s]
Finished. Total time: 0.016s
Sending 'qupfw_a' (56 KB)                          OKAY [  0.003s]
Writing 'qupfw_a'                                  OKAY [  0.001s]
Finished. Total time: 0.012s
Sending 'qupfw_b' (56 KB)                          OKAY [  0.003s]
Writing 'qupfw_b'                                  OKAY [  0.001s]
Finished. Total time: 0.011s
Sending 'xbl_a' (3608 KB)                          OKAY [  0.094s]
Writing 'xbl_a'                                    OKAY [  0.006s]
Finished. Total time: 0.107s
Sending 'xbl_b' (3608 KB)                          OKAY [  0.088s]
Writing 'xbl_b'                                    OKAY [  0.006s]
Finished. Total time: 0.101s
Sending 'devcfg_a' (52 KB)                         OKAY [  0.003s]
Writing 'devcfg_a'                                 OKAY [  0.001s]
Finished. Total time: 0.011s
Sending 'devcfg_b' (52 KB)                         OKAY [  0.003s]
Writing 'devcfg_b'                                 OKAY [  0.001s]
Finished. Total time: 0.011s
Sending 'hyp_a' (3616 KB)                          OKAY [  0.092s]
Writing 'hyp_a'                                    OKAY [  0.011s]
Finished. Total time: 0.110s
Sending 'hyp_b' (3616 KB)                          OKAY [  0.087s]
Writing 'hyp_b'                                    OKAY [  0.011s]
Finished. Total time: 0.105s
Sending 'imagefv_a' (2048 KB)                      OKAY [  0.056s]
Writing 'imagefv_a'                                OKAY [  0.007s]
Finished. Total time: 0.071s
Sending 'imagefv_b' (2048 KB)                      OKAY [  0.055s]
Writing 'imagefv_b'                                OKAY [  0.007s]
Finished. Total time: 0.070s
Sending 'shrm_a' (48 KB)                           OKAY [  0.003s]
Writing 'shrm_a'                                   OKAY [  0.001s]
Finished. Total time: 0.011s
Sending 'shrm_b' (48 KB)                           OKAY [  0.003s]
Writing 'shrm_b'                                   OKAY [  0.001s]
Finished. Total time: 0.011s
Sending 'aop_a' (240 KB)                           OKAY [  0.008s]
Writing 'aop_a'                                    OKAY [  0.003s]
Finished. Total time: 0.017s
Sending 'aop_b' (240 KB)                           OKAY [  0.007s]
Writing 'aop_b'                                    OKAY [  0.003s]
Finished. Total time: 0.017s
Sending 'cust' (415132 KB)                         OKAY [ 11.090s]
Writing 'cust'                                     OKAY [  0.004s]
Finished. Total time: 11.103s
Sending sparse 'super' 1/9 (738592 KB)             OKAY [ 20.136s]
Writing 'super'                                    OKAY [  0.008s]
Sending sparse 'super' 2/9 (735128 KB)             OKAY [ 19.928s]
Writing 'super'                                    OKAY [  0.010s]
Sending sparse 'super' 3/9 (754584 KB)

It's been stuck on this line, 'super' 3/9, for 30 minutes. What to do, do I keep waiting? Will my device be bricked if I interrupt the installation? This has never happened to me before.
Click to expand...
Don't worry, it is a common problem. Reboot phone and try again with another USB port and/or another USB cable.
 
  • Like
Reactions: Casper99
C

claw88

Members
Jan 2, 2020
140
40
With last rom from Xiaomi 12 (cupid) Google assistant not working anymore if I clear recent apps. If I say "ok google" assistant not working, until I open the Google app or some other such Chrome. Any advice for this?
 
E

edugam

Members
Oct 5, 2021
9
15
good evening I want to ask, install Rom 13.0.7 on my redmi note 10 pro, and it flows very well, the only thing that is happening to me is that in whastapp, it deletes my contacts until I update in the same app, it seems again, you would know how can i fix that? Thank you very much in advance for sharing your work. excuse my english but i'm translating it
 
katerpanne

katerpanne

Members
Apr 19, 2014
2,634
332
edugam said:
good evening I want to ask, install Rom 13.0.7 on my redmi note 10 pro, and it flows very well, the only thing that is happening to me is that in whastapp, it deletes my contacts until I update in the same app, it seems again, you would know how can i fix that? Thank you very much in advance for sharing your work. excuse my english but i'm translating it
Click to expand...
there are some workarounds…
1st change contact permissions to "Always allow" in whatsapp
- Modify and delete contacts
- Read your contacts
2nd you have to "clear data / cache" on the Permissions app
 
  • Like
Reactions: kyj8100, Frackme and JiaiJ
You must log in or register to reply here.

Similar threads

ingbrzy
  • Locked
MIUI 13 22.6.22
Replies
401
Views
61K
MIUI 13
Karpfenhai
Karpfenhai
ingbrzy
  • Locked
MIUI 13 22.6.15
Replies
177
Views
42K
MIUI 13
lpzceduardo
L
ingbrzy
  • Locked
MIUI 13 22.5.25
Replies
107
Views
43K
MIUI 13
Pho3nX
P
ingbrzy
  • Locked
MIUI 13 22.5.18
Replies
146
Views
47K
MIUI 13
kaziTuHiN
kaziTuHiN
ingbrzy
  • Locked
MIUI 13 22.5.11
Replies
224
Views
54K
MIUI 13
vatis24
V
Top Bottom