Ever since my (not-rooted inventory Android) Nokia 6.1 cellphone was upgraded to Android 10, final January, I’ve a efficiency subject with it: A few instances per day it turns into close to or utterly unusable, typically completely till a tough restart. Additionally this causes excessive battery utilization.
Nonetheless, utilizing a battery evaluation app did not flip up any particular suspect.
Not too long ago I found
adb shell, and when the cellphone begins behaving badly,
highconfirmed me that the CPU-hogging course of at such moments is
Duties: 681 complete, 1 working, 680 sleeping, Zero stopped, Zero zombie Mem: 2.6G complete, 2.4G used, 198M free, 11M buffers Swap: 1.0G complete, 1.0G used, 112Okay free, 311M cached 800%cpu 38%person 10%good 52%sys 684%idle 10%iow 2percentirq 4percentsirq 0percenthost PID USER PR NI VIRT RES SHR S[%CPU] %MEM TIME+ ARGS 1739 system 18 -2 7.9G 144M 47M S 12.3 5.2 13:37.24 system_server 148 root 20 0 0 0 Zero S 8.6 0.0 3:50.15 [kswapd0] 564 logd 30 10 168M 10M 0.9M S 7.3 0.3 1:11.69 logd 28119 shell 20 0 35M 3.1M 1.7M R 5.0 0.1 0:00.45 high 705 root 20 Zero 5.1G 44M 24M S 5.0 1.6 0:54.88 zygote64
high -s 6(kinds by reminiscence use,
RES) confirmed me that the primary memory-using course of at such moments is
com.android.merchandising(= Google Play Retailer).
Duties: 690 complete, 1 working, 689 sleeping, Zero stopped, Zero zombie Mem: 2.6G complete, 2.4G used, 180M free, 17M buffers Swap: 1.0G complete, 0.9G used, 2.1M free, 412M cached 800%cpu 9percentuser 3percentnice 13%sys 772%idle 1percentiow 2percentirq 1percentsirq 0percenthost PID USER PR NI VIRT [RES] SHR S %CPU %MEM TIME+ ARGS 5296 u0_a105 20 Zero 2.1G 472M 24M S 0.0 17.2 1:18.80 com.android.merchandising 1739 system 18 -2 7.9G 150M 53M S 3.0 5.4 13:12.22 system_server 2233 u0_a111 20 Zero 6.1G 108M 56M S 0.6 3.9 2:03.84 com.android.systemui 7120 u0_a161 20 Zero 7.7G 93M 45M S 0.6 3.4 8:22.83 com.google.android.youtube 2931 u0_a90 20 Zero 5.9G 83M 36M S 0.0 3.0 3:05.21 com.google.android.gms.persistent 26244 u0_a90 20 Zero 5.2G 74M 39M S 0.0 2.7 0:02.38 com.google.android.gms.ui
[Side note. That seems to explain why battery analysis didn’t help: Presumably
kswapd CPU usage is ascribed to general kernel processing, not to this specific app.]
And that app is actually the trigger: Stopping that Google Play Retailer course of (e.g., utilizing
am force-stop com.android.merchandising) rapidly brings efficiency again to regular ranges.
As a workaround, I attempted to disable automated updates in Google Play Retailer, and that appears to have improved issues a little bit, however the subject is certainly nonetheless there.
So now, as one other workaround, a few instances per day I hard-stop that utility, which helps to stop it often.
My obscure query is: The right way to I get additional with this subject?
- Is that this a identified subject that has already been reported someplace? Is the trigger identified? (E.g., is that this triggered by the Google Play Retailer app detecting updates?)
- Can I report it to Nokia in some bug tracker? Can I report it to Google someplace?
- What sort of extra data/dumps/logs would assist to analyze this additional?
- Are there every other/higher workarounds? (Disable some function, return to an older model of Google Play Retailer, clear some cache or drive one thing to be regenerated, no matter…)
- Is there some technique to automate the workaround I presently have? (I am already utilizing Automate for another issues, however any automated resolution apparently requires my machine to be rooted.)
(Be aware that my machine shouldn’t be rooted, and I want to attempt to maintain it that approach. However I’ll take into account rooting it, if there some form of resolution or workaround that requires that.
If it helps, cellphone mannequin is TA-1043, presently working construct quantity 00WW_4_10C_SP04.)