- Oct 6, 2016
- 9,511
- 322
Nothing I can do about that, new System UI on Android 11 isn't in a fully stable state right now. You should report to Xiaomi, it's the same on official ROMs. I saw this glitch multiple times myself. Seems random.
[INFO] Known Issues (Weekly) & FAQ
- Thread starter Igor Eisberg
- Start date
sweetxtooth
Members
- Jun 13, 2020
- 25
- 15
Akaigetsu
Members
- Oct 25, 2020
- 6
- 15
Is the problem mentioned in the following threads also a problem on official ROM or will this be added as a known issue?
Hiding app notifications is not working. Problem with Android 11. Stable android 10 version works correctly as well.
Phone Mi 10 Lite Zoom
Phone Mi 10 Lite Zoom
- Oct 6, 2016
- 9,511
- 322
I can't confirm this issue on Mi 10 (20.12.10), bubbles are shown correctly, no gray overlay, so best we can do is wait until it's fixed officially.
I'm using mi10 ultra 512gb version. Originally Chinese rom but flashed to 20.12.10 miui beta. When in full screen I can pull down notifications section I can not pull it back up. But control center I can not pull back up. I have to swipe from the wife (back function) to pull it back. This only happens in horizontal orientation
@Igor Eisberg
@ingbrzy
For Apollo device (HMK3SUltra_MI10T) we have incorrect vbmeta, so after flashing ROM there is a bootloop in TWRP.
We are forced to flash vbmeta through the PC (in fastboot mode) to boot into the system.
This is several weekly releases already.
Here is the correct vbmeta in the archive.
@ingbrzy
For Apollo device (HMK3SUltra_MI10T) we have incorrect vbmeta, so after flashing ROM there is a bootloop in TWRP.
We are forced to flash vbmeta through the PC (in fastboot mode) to boot into the system.
This is several weekly releases already.
Here is the correct vbmeta in the archive.
Last edited:
- Feb 11, 2012
- 11,552
- 322
seems you are only one reporting bootloop issue on apollo.. please install our ROM according our installation guide.. Updater - select zip - reboot
1. Downloading the ROM.
2. Manually reboot into TWRP
3. Installing firmware from TWRP.
4. Loading into the system -> bootloop for Apollo.
I have been doing 1-3 steps for several years now (I install all weekly ROMs ones as a translator for checking).
But only with firmware for Apollo there is a problem.
This problem is not only for me, but for many on 4pda (russian community).
- Feb 11, 2012
- 11,552
- 322
Then it may be your TWRP issue.. Patched vbmeta is already part of our ROM.. Seems your TWRP is not able to flash vbmeta.img during ROM installation..
Thanks for the tip.
What recovery do you recommend and where can I get it separately?
@ingbrzy
I tried 2 TWRPs:
First recovery: TWRP_apollo_3.4.0_10_whyle.img
Second recovery: recovery-TWRP-3.4.2B-1206-REDMI_K30S_ULTRA-CN-wzsx150.img
Both give a bootloop.
In the stock ROM vbmeta size 8 kb and 4 kb.
When in the xiaomi.eu ROM I replace the vbmeta with the stock one,
after flashing the ROMs in both TWRPs, loading into the system goes without problems.
What TWRP should be used to flash xiaomi.eu ROM without any problems?
I tried 2 TWRPs:
First recovery: TWRP_apollo_3.4.0_10_whyle.img
Second recovery: recovery-TWRP-3.4.2B-1206-REDMI_K30S_ULTRA-CN-wzsx150.img
Both give a bootloop.
In the stock ROM vbmeta size 8 kb and 4 kb.
When in the xiaomi.eu ROM I replace the vbmeta with the stock one,
after flashing the ROMs in both TWRPs, loading into the system goes without problems.
What TWRP should be used to flash xiaomi.eu ROM without any problems?
Last edited:
My K30, camera app crashes after taking 1 picture in auto mode.. And also Macro and UW camera modes are just main camera, except if i go to Pro mode I can use the other cameras on build 20.12.10
Sent from my Redmi K30 using Tapatalk
Sent from my Redmi K30 using Tapatalk
- Oct 6, 2016
- 9,511
- 322
Unable to reproduce on Mi 10 Weekly 20.12.10. Chat bubbles work here alright.Bubbles feature working improperly on the Poco F2 Pro.
Sent from my POCO F2 Pro using Tapatalk
Akaigetsu
Members
- Oct 25, 2020
- 6
- 15
Can you tell us (those with the bubble issue) what your settings are?
• Light/Dark theme?
• Default launcher?
I tried both default launcher and light theme (my usual is Nova Launcher + Dark theme) and this didn't solve it for me but maybe there're some settings we can toggle to prevent this issue.
dng2007
Members
- Jun 27, 2020
- 5
- 13
You may try these to turn on your VOLTE function manually..
1. To check IMS status: open your phone app and dial *#*#4636#*#*
2. To unlock VoLTE: open your phone app and dial *#*#86583#*#*
3. To unlock VoWifi: open your phone app and dial *#*#869434#*#*
Attachments
sweetxtooth
Members
- Jun 13, 2020
- 25
- 15
Thanks i already try this same issue even my friends with this update they had the issue
@Igor Eisberg
Battery drain on 20.12.9 (Appollo)
-20% per night
Battery drain on 20.12.9 (Appollo)
-20% per night
Code:
================
Kernel Wakelocks
================
usb (*api*): 9 h 7 m 57 s Cnt:(c/wc/ec)0/0/0 100,0%
c440000.qcom,spmi:qcom,pm8150b@2:qpnp,fg (*api*): 2 h 31 m 52 s Cnt:(c/wc/ec)27891337/0/0 27,7%
qcom-step-chg (*api*): 42 m 15 s Cnt:(c/wc/ec)2825773/0/0 7,7%
998000.qcom,qup_uart (*api*): 33 m Cnt:(c/wc/ec)4018/0/0 6,0%
hal_bluetooth_lock (*api*): 32 m 54 s Cnt:(c/wc/ec)2182/0/0 6,0%
PowerManagerService.WakeLocks (*api*): 17 m 36 s Cnt:(c/wc/ec)1355/0/0 3,2%
...- Oct 6, 2016
- 9,511
- 322
Since Last update, 20/12/10,i cant use volte.
Already enable and disable menu tru e *#*#86583#*#*, and cant enable it. Also says that volte it is not supported by my operator.
Already call to my operator, and volte its funcional.
By the code, Only can enable/disable sim 2,but i have no sim on it
Already enable and disable menu tru e *#*#86583#*#*, and cant enable it. Also says that volte it is not supported by my operator.
Already call to my operator, and volte its funcional.
By the code, Only can enable/disable sim 2,but i have no sim on it
Attachments
ElDavo
Members
- Jun 30, 2020
- 74
- 30
@Igor Eisberg
After replacing the kernel from 20.12.9 with one from 20.12.2, the battery drain has left and the device sleeps normally.
So this it China's issue.
Code:
Level lost [%]: Bat.: -7%(81% to 74%) [0,8%/h]
Voltage lost [mV]: (4170-4096) [8,7%/h]
Deep Sleep (): 7 h 3 m 46 s 83,2%
...
alarmtimer (*api*): 29 m 27 s Cnt:(c/wc/ec)877/0/0 5,8%
998000.qcom,qup_uart (*api*): 24 m 13 s Cnt:(c/wc/ec)3778/0/0 4,8%
hal_bluetooth_lock (*api*): 23 m 36 s Cnt:(c/wc/ec)1979/0/0 4,6%
PowerManagerService.WakeLocks (*api*): 14 m 54 s Cnt:(c/wc/ec)1570/0/0 2,9%- Oct 6, 2016
- 9,511
- 322
Good to know, hardly surprises me. The issues introduced by China ROM we have to fix ourselves are countless.
