It only works at me MI Music and YouTube.Are you using the stock music app? Try pi music player or vlc.
Edit: even the stock music player works on my mi 10
Sent from my MI 9 using Tapatalk
It only works at me MI Music and YouTube.Are you using the stock music app? Try pi music player or vlc.
Edit: even the stock music player works on my mi 10
It's already mentioned many times, that people should also try deleting the "data/system/package_cache" folder from twrp too. Give it a try, it may work.just updated my MI10 umi, but randomly when i open/use an app, it reboot. I entered in the new twrp 3.5 and wiped cache and dalvik but the problem is still there
For me it works for mi music, pi music player and vlc.It only works at me MI Music and YouTube.
Sent from my MI 9 using Tapatalk
Try to use E164 format like +4412345678I have a problem that I cannot solve, the filter to block unwanted calls only blocks mobile numbers in the Blacklist does not block landline numbers. So I keep getting calls from landline numbers that I have blocked.
What can it depend on?
i have a poco F2 Pro with latest rom xiaomi.eu weekly
Inviato dal mio Redmi K30 Pro utilizzando Tapatalk
I have already tried with +39 since I live in Italy but it didn't helpTry to use E164 format like +4412345678
Sent from my MI 8 Explorer Edition using Tapatalk
Just in case anyone hasn't noticed: the "tool" to open the SIM drawer is essentially a bent paperclip; I always use an actual paperclip rather than finding the "tool", both with Xiaomi and other phones with a SIM drawer.... I don't have the tool with me atm to swap the SIM cards over ...
Lol, be careful though not to put the tool/clip on a mic or speaker hole like me... When I first got my phone I almost pierced the secondary mic (I realized it wasn't the ejection hole soon though, phew..).Just in case anyone hasn't noticed: the "tool" to open the SIM drawer is essentially a bent paperclip; I always use an actual paperclip rather than finding the "tool", both with Xiaomi and other phones with a SIM drawer.
Before switching to magisk 22, I saw that people have problems with updating it, so before the next weekly update I completely removed magisk by magisk manager.Problems with Magisk 22 (recent RN7 ROMs)
I am using a rooted Redmi Note 7/lavender, with OrangeFox recovery and Magisk root. Until Magisk 21.4 I would install a new ROM and the current Magisk in a single operation (from OrangeFox, not the Updater app), and everything was hunky-dory. With Magisk 22 I made a copy of the .apk with .zip extension and found that nothing worked, I ended up without root, either trying to install from the app or installing from recovery. Worse, if I uninstalled Magisk then installed the previous 21.4 and the Manager I still didn't have root.
I Have a similar problem with my cas (mi 10 ultra)I have an issue that was present on 21.2.24 as well as still exists on 21.3.3. The SIM card I have in slot 2 is compatible with 5G, but suddenly the 'Prefer 5G" option is missing under preferred network type.
The SIM card I have in slot 1 has the option 'Prefer 5G', however the carrier for that SIM doesn't yet offer 5G in my area.
So I have a 5G SIM in slot 2 but I can't select it, and a 4G SIM in slot 1 that offers me the option but the carrier doesn't provide it. Initially 5G in slot 2 was working fine, even on 21.2.24 but something happened in the last few days that stopped it.
Anyone seen this before?
Deleted the folder but problem not solved. Can i try a downgrade with previous rom or this can cause other problems?It's already mentioned many times, that people should also try deleting the "data/system/package_cache" folder from twrp too. Give it a try, it may work.
Eh, the previous one has the other twrp, you might run into twrp incompatibility issues. Try to reflash the same rom instead. (Yesterday I tried to redtorr a nandroid backup of the previous rom on this one and if you see yesterday posts here, you'll probably understand what I mean...)Deleted the folder but problem not solved. Can i try a downgrade with previous rom or this can cause other problems?
Inviato dal mio Mi 10 utilizzando Tapatalk
I've just done a TWRP backup. I tried ticking all of the boxes, but quite a few of them unticked themselves when starting the backup.[Edit: turns out there was a difference on how twrp and my file manager calcuate data, peobably the -byte/bit difference.. There's ~no problem with the new twrp.]
Umm, has the new twrp for mi 10 given more options to backup (like more partitions to backup)? A little before I had upgraded to this rom I made a backup with ~25gb (using the previous twrp). Now making a new backup with the new rom and twrp and it takes about 35gb.. What exactly has happened? The rom zip was about the same size as before (though unzipped the difference might was bigger). Is there some kind of an issue? Anybody who can create a backup eith the new twrp to check it?
I think it's just that different programs mean different things with "MB"; I think in binary, mb has a different size than what people commonly think (just like a 1tb drive is actually ~900gb on windows explorer).I've just done a TWRP backup. I tried ticking all of the boxes, but quite a few of them unticked themselves when starting the backup.
I also noticed that the backup demanded over 31Gb of free memory. It would not start until that memory was actually free - which is annoying because I had to start removing some of my music!
I created enough space and have done the backup, and backed it up onto my PC. It turns out that even though it demanded over 31Gb free space, the actual backup is only 22.5Gb - only about 0.5Gb more than the previous TWRP. (This is only an estimate because I have only taken one backup so far).
So I am going to have to start managing my memory a bit better now!
This is exactly one of the main concerns that I mentioned in one of my previous posts. I would really recommend avoiding a downgrade to a previous ROM, if at all possible. Even having a full backup of everything would probably not even make a restore straight forward.Eh, the previous one has the other twrp, you might run into twrp incompatibility issues. Try to reflash the same rom instead. (Yesterday I tried to redtorr a nandroid backup of the previous rom on this one and if you see yesterday posts here, you'll probably understand what I mean...)
I'm not sure about this because having done the backup, I have 7.5Gb free. Which calculates more or less correctly. So the backup is demanding a lot more memory than it actually uses, which the previous TWRPs did not.I think it's just that different programs mean different things with "MB"; I think in binary, mb has a different size than what people commonly think (just like a 1tb drive is actually ~900gb on windows explorer).
My backup again was about 27gb, so I don't think there was an increase for me (maybe ~1-2gb).I'm not sure about this because having done the backup, I have 7.5Gb free. Which calculates more or less correctly. So the backup is demanding a lot more memory than it actually uses, which the previous TWRPs did not.
Hello,Hello, do you know why some icon look weird in xiaomi.eu? and what can i do?
Problem with cache is solved. Tnx.With some phones, deleting the /data/system/package_cache folder helps remove the lagging. And if you have not already done so, clear the Dalvik and cache.
Yes just go to twrp and install the zipI'm using version 21.2.24, to upgrade to 21.3.3 / 5 just go to TWRP and install the zip? Need to give some wipe or form a date?
It might need temporary working space as well as the space used for the final backup.it demanded over 31Gb free space, the actual backup is only 22.5Gb
We use essential cookies to make this site work, and optional cookies to enhance your experience. Cookies are also used for ads personalisation