Right you are (fresh install of Arrow 11) - will post in their thread once I've gathered more information.
General Poco X3 Pro - Known issues and solutions
- Thread starter TioCareca
- Start date
might tone down after 1-2 days.
When i first got the phone it took around 3 days to fully settle....
Duration / Realtime: 67h16m40.176s
Code:
Aggregated Checkin Stats:
Metric | Value
Screen Off Discharge Rate (%/hr) | 0.37 (Discharged: 23%)
Screen On Discharge Rate (%/hr) | 8.81 (Discharged: 48%)
Screen On Time | 5h26m45.548s
Screen Off Uptime | 3h40m0.136s
Userspace Wakelock Time | 2h0m8.932s
Sync Activity | 55.961s (54 times)
JobScheduler Activity | 46m30.148s (1975 times)
App Wakeup Alarms | 1105 times
CPU Usage | 5h8m40.861s user time, 4h52m17.405s system time
Kernel Overhead Time | 1h39m51.204s
Kernel Wakelocks | 1h54m49.462s (804940 times)
Wakeup Reasons | 1h12m25.447s (6622 times)
Mobile KBs/hr | 2674.69
WiFi KBs/hr | 7270.63
Total WiFi Scan Activity | 3m41.132s (59 times)
Total WiFi Full Lock Activity | 0
Mobile Active Time | 6h39m36.076s
Signal Scanning Time | 0
Full Wakelock Time | 49m5.534s
Interactive Time | 5h27m37.676s
Phone Call Time | 1m38.031s
Device Idle Mode Enabled Time | 30h47m16.92s
Device Idling Time | 31h0m38.672s
Total GPS Use | 0 (0 times)
Wifi Power Usage | 0.00%/hr, 0.00% total
Wifi Transfer Time | 0
Wifi Idle Time | 0
Bluetooth Power Usage | 0.00%/hr, 0.00% total
Bluetooth Transfer Time | 0
Bluetooth Idle Time | 0
Camera Use | 4m47.95s (17 times)
Flashlight Time | 0 (0 times)
Modem Transfer Time | 0
Modem Idle Time | 0
Device's Power Estimates:
Ranking | Name | Uid | Battery Percentage Consumed
0 | OVERCOUNTED | 0 | 12.64%
1 | CELL | 0 | 13.80%
2 | SCREEN | 0 | 12.69%
3 | org.mozilla.firefox | 10292 | 11.51%
4 | ANDROID_SYSTEM | 1000 | 8.00%
5 | GOOGLE_SERVICES | 10190 | 6.51%
6 | org.thoughtcrime.securesms | 10296 | 4.81%
7 | ROOT | 0 | 3.57%
8 | com.xiaomi.xmsf | 10144 | 3.16%
9 | com.miui.msa.global | 10146 | 2.64%
Userspace Wakelocks:
Ranking | Name | Uid | Duration / Hr | Count / Hr | Total Duration | Total Count
0 | com.maxmpz.audioplayer : AudioMix AudioOut_1D1085 | 10308 | 1m4s798ms | 0.09 | 1h15m5.193s | 6
1 | ANDROID_SYSTEM : *job*/android/com.android.server.MountServiceIdler | 1000 | 7s450ms | 0.33 | 13m48.442s | 22
2 | ANDROID_SYSTEM : deviceidle_maint | 1000 | 5s709ms | 0.89 | 10m25.886s | 60
3 | com.miui.cleaner : *job*/com.miui.cleaner/com.miui.optimizecenter.timed.TimedUpdateCleanUpDbJobService | 10093 | 3s86ms | 0.03 | 7m9.188s | 2
4 | org.mozilla.firefox : audio-playing | 10292 | 2s694ms | 0.00 | 6m9.203s | 0
5 | org.mozilla.firefox : AudioMix AudioOut_1D1085 | 10292 | 2s569ms | 0.00 | 5m50.439s | 0
6 | ANDROID_SYSTEM : ActivityManager-Sleep | 1000 | 4s90ms | 1.16 | 5m49.633s | 78
7 | ANDROID_SYSTEM : AnyMotionDetector | 1000 | 3s134ms | 0.33 | 3m41.506s | 22
8 | BLUETOOTH : StartingObexPbapTransaction | 1002 | 1s456ms | 0.09 | 3m22.268s | 6
9 | AUDIOSERVER : AudioMix AudioOut_D1085 | 1041 | 1s32ms | 0.77 | 2m13.485s | 52
Kernel Wakesources:
Ranking | Name | Duration / Hr | Count / Hr | Total Duration | Total Count
0 | hal_bluetooth_lock | 1m13s905ms | 10.70 | 1h22m52.194s | 720
1 | IdleMaint | 11s883ms | 0.65 | 13m19.5s | 44
2 | NETLINK-hvdcp_opti | 3s981ms | 2142.41 | 4m27.872s | 144137
3 | NETLINK-batterysecret | 3s895ms | 2177.11 | 4m22.1s | 146471
4 | PowerManager.SuspendLockout | 1s747ms | 1.68 | 1m57.59s | 113
5 | PowerManagerService.Display | 1s747ms | 1.49 | 1m57.558s | 100
6 | bluetooth_timer | 1s637ms | 34.68 | 1m50.151s | 2333
7 | sthal_transit_wake_lock | 957ms | 0.18 | 1m4.441s | 12
8 | SensorService_wakelock | 599ms | 8.47 | 40.361s | 570
9 | PowerManagerService.Broadcasts | 382ms | 3.54 | 25.745s | 238
10 | netmgr_wl | 342ms | 32.76 | 23.037s | 2204
11 | batteryd | 171ms | 1341.87 | 11.569s | 90278
12 | -hvdcp_opti | 154ms | 237.76 | 10.413s | 15996
13 | qcril | 151ms | 70.87 | 10.195s | 4768
14 | CHG_PLCY_MAIN_WL | 137ms | 1339.24 | 9.232s | 90101
15 | CHG_PLCY_HVDCP2_WL | 112ms | 135.29 | 7.563s | 9102
16 | ApmAudio | 104ms | 20.11 | 7.01s | 1353
17 | ApmOutput | 53ms | 12.41 | 3.583s | 835
18 | CHG_PLCY_SOH_WL | 50ms | 113.47 | 3.417s | 7634
19 | event0-InputReader | 41ms | 3.15 | 2.776s | 212
20 | event2-InputReader | 39ms | 7.65 | 2.675s | 515
21 | CHG_PLCY_HVDCP_WL | 37ms | 123.84 | 2.497s | 8332
22 | cne_wl_ | 34ms | 0.03 | 2.312s | 2
23 | DIAG_WS | 33ms | 301.90 | 2.272s | 20311
24 | CHG_PLCY_STD_PD_WL | 33ms | 119.44 | 2.258s | 8036
Kernel Wakeup Reasons:
Ranking | Name | Duration / Hr | Count / Hr | Total Duration | Total Count | Show Count vs Time
0 | Abort:Wakeup IRQ detected during suspend: 556 qpnp_rtc_alarm | 6s420ms | 21.48 | 7m11.981s | 1445 |
1 | 667:glink-native_modem | 4s752ms | 18.28 | 5m19.712s | 1230 |
2 | Abort:Callback failed on alarmtimer in platform_pm_suspend+0x0/0x4c returned -16 | 33s75ms | 16.20 | 37m5.254s | 1090 |
3 | Abort:Last active Wakeup Source: qrtr_0, handle process swapper/0 | 7s316ms | 12.43 | 8m12.238s | 836 |
4 | Abort:Wakeup IRQ detected during suspend: 175 WLAN_CE_2 | 3s555ms | 10.37 | 3m59.175s | 698 |
5 | Abort:Wakeup IRQ detected during suspend: 171 ipa | 1s120ms | 4.06 | 1m15.366s | 273 |
6 | Abort:Last active Wakeup Source: qrtr_0, handle process Binder:728_2 | 1s803ms | 3.02 | 2m1.309s | 203 |
7 | 419:smp2p:634:glink-native_slpi | 295ms | 1.96 | 19.867s | 132 |
8 | Abort:Last active Wakeup Source: c440000.qcom,spmi:qcom,[email protected]:qpnp,fg, handle process mi_thermald | 1s553ms | 1.89 | 1m44.519s | 127 |
9 | Abort:Pending Wakeup Sources: qcom_rx_wakelock, handle process cds_ol_rx_threa | 542ms | 1.17 | 36.477s | 79 |
10 | Abort:Callback failed on 18800000.qcom,icnss in icnss_pm_suspend_noirq+0x0/0x11c returned -11 | 518ms | 1.03 | 34.856s | 69 |
11 | Abort:Wakeup IRQ detected during suspend: 301 gf | 476ms | 0.55 | 32.089s | 37 |
12 | Abort:Wakeup IRQ detected during suspend: 560 msoc-delta | 137ms | 0.49 | 9.283s | 33 |
13 | Abort:Last active Wakeup Source: qrtr_0, handle process netmgrd | 334ms | 0.45 | 22.488s | 30 |
14 | Abort:Pending Wakeup Sources: IPA_CLIENT_APPS_LAN_CONS, handle process swapper/0IPA_WS, handle process swapper/0 | 218ms | 0.43 | 14.686s | 29 |
15 | Abort:Wakeup IRQ detected during suspend: 57 pon_kpdpwr_status | 0ms | 0.28 | 59ms | 19 |
16 | Abort:Pending Wakeup Sources: IPA_CLIENT_APPS_LAN_CONS, handle process Binder:728_2IPA_WS, handle process Binder:728_2 | 154ms | 0.27 | 10.415s | 18 |
17 | Abort:Wakeup IRQ detected during suspend: 570 batt-temp-delta | 101ms | 0.25 | 6.838s | 17 |
18 | Abort:Wakeup IRQ detected during suspend: 225 hs_uart_wakeup | 266ms | 0.22 | 17.944s | 15 |
19 | Abort:Wakeup IRQ detected during suspend: 576 dma-grant | 90ms | 0.21 | 6.114s | 14 |
20 | Abort:Last active Wakeup Source: c440000.qcom,spmi:qcom,[email protected]:qpnp,fg, handle process kworker/0:1 | 109ms | 0.16 | 7.391s | 11 |
21 | Abort:Last active Wakeup Source: c440000.qcom,spmi:qcom,[email protected]:qpnp,fg, handle process kworker/0:0 | 92ms | 0.13 | 6.201s | 9 |
22 | Abort:Last active Wakeup Source: c440000.qcom,spmi:qcom,[email protected]:qpnp,fg, handle process kworker/0:2 | 123ms | 0.13 | 8.31s | 9 |
23 | Abort:Pending Wakeup Sources: NETLINK-batterysecret, handle process kworker/0:5NETLINK-hvdcp_opti, handle process kworker/0:5 | 54ms | 0.13 | 3.693s | 9 |
24 | Abort:Last active Wakeup Source: IPA_CLIENT_APPS_WAN_CONS, handle process swapper/0 | 165ms | 0.12 | 11.105s | 8 |
App Wakeup Alarms:
Ranking | Name | Uid | Frequency (count/hr) | Count
0 | ANDROID_SYSTEM | 1000 | 6.11 | 411
1 | com.xiaomi.xmsf | 10144 | 5.53 | 372
2 | GOOGLE_SERVICES | 10190 | 4.34 | 292
3 | com.android.deskclock | 10164 | 0.19 | 13
4 | BLUETOOTH | 1002 | 0.09 | 6
5 | com.google.android.apps.wellbeing | 10195 | 0.06 | 4
6 | com.miui.weather2 | 10089 | 0.03 | 2
7 | org.thoughtcrime.securesms | 10296 | 0.03 | 2
8 | com.xiaomi.finddevice | 9810 | 0.03 | 2
9 | com.google.android.apps.messaging | 10217 | 0.01 | 1667:glink-native_modem is not missconfigured. And as expected only works when not in WiFi network.
@Haldi4803 - thanks for sharing - are you on the stock MIUI ROM?
I've moved my issue to the Arrow OS thread - my issues might be related to the ROM.
I've moved my issue to the Arrow OS thread - my issues might be related to the ROM.
Latest Miui update 12.5.4 actually botlooped for me when t successfully installed via OTA install on a EEA (EU) model Poco X3 Pro, rebooted into recovery everytime, until i picked Safe mode there, then it rebooted once into recovery again, where picking regular reboot booted it into safe mode finally. Fro there a regular reboot fixed it..
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
2Its Plastic back cover that.... yes, you gusset it. It move as every plastic, and when you drop some weird loud bass, loudspeaker gonna push lots of air around it...
Not to mention that Im sure it not really back cover, but just speakers them self that make noise, as we need to admit Poco X3 Pro have nice powerful speakers so it have some punch.
Honestly almost every phone loudspeaker gonna get distorted sound when you max out sound... Not to mention that all depend on sound source.
If you Listen to music on phone speakers... well.... you probably annoy everyone else around you anyway as no normal person listen to FULL VOLUME music on phone... Not to mention movies...
And as ringtone? its loud enough even at 70-80%, + you have vibration, notification led, and most of people today use smartband/smartwatch so its hard to miss a call. For anything else, just use BT or wired headphones.2For me:
1- I don't find it issue I'm okay.
2- You can reduce volume of call audio during the call.
3- Didn't notice this issue.
5- I got "Tianma" brand with 256/8 variant global. Didn't get ghost touch issue.
So I'm lucky
Regards1Issues:
1. If the volume is high the back vibrates/trembles a bit.
2. When on a call, people around you may listen to the person you're having a call with because the earpiece is quite loud.
3. Some people complain about screen flickering/blinking on lowest brightness.
4. Audio is distorted/choppy on video recordings.
5. Some people complain about touch issues. More precisely, long swipes + holding = jitter (not stable) and some long swipes stop midway.
Solutions - fixes:
1. It can be fixed in MIUI by enabling dev settings, searching for mono audio and changing audio balance to the right which reduces the volume from the left speaker / earpiece. In AOSP ROMs the option is in Settings > Accessibility > Audio balance. Personally, I got used to it and haven't changed anything. It gives a bass feeling. And it's not that noticeable when using a case.
2. It can be improved by doing the same as #1. For a more efficient solution, wait for a fix in custom ROMs.
3. It only happens on the lowest brightness: 1%. So just turn the brightness slider to >=2%. Poco X3 Pro's screen can go so dim that it almost goes completely off. This is really useful for people who use their phones in total darkness. Some custom ROMs have increased the minimum brightness value a bit.
4. It was fixed in 12.0.5.0 EEA and 12.0.6.0 Global stock MIUI and MIUI based custom ROMs. If you're on an older version, please update.
5. Check which display you have. According to dozens of reports so far, 9/10 of 8/256 vayu variants have Huaxing, 9/10 of 6/128 vayu variants have Tianma and all bhima variants have Tianma.
If you have Huaxing, you're fine. If you have Tianma, most units should be fine: no swipe issues and no jitter at all. But even if you're among the unlucky ones, everything can be improved or even be completely fixed by using lybkernel TS-MOD variant which has tweakable touch sysfs.1I have a Poco X3 Pro 6/128 and it has a Huaxing panel. So far, I haven't experienced any issues aside from the overheating. It's not really "that hot" but it's just a bit hotter than my old phone (Honor Play) with casual use. If I play graphic intensive games like Genshin Impact, it does get hot.
New posts
-
How to check lcd panel maker and other info?
- Latest: BrittanyMillems
-
-
