cancel
Showing results for 
Search instead for 
Did you mean: 

[Bug Report] Low Memory Killer/RAM Management issue in .119 update

Lambaste
Rising Star I
My phone has been facing debilitating RAM management issues after the latest Android 10 update (QP1A.190711.005 17.1810.2001.119-0). Inspecting the logs seem to indicate that it is primarily a RAM management issue. I have not ascertained the circumstances that trigger this behaviour but have been able to confirm the following given my own testing:
Once a certain amount of time passes after a system reboot, usually ranging from 18-24 hours, a memory leak presumably develops in a system component.
This increases the OS' memory pressure significantly.
The increased memory pressure causes the Android OS' low-memory-killer-daemon to kill background processes and services.
After the first batch of memory pressure events, the LMK daemon starts to kill background system processes very aggressively.
This causes dependent processes to crash, triggering the OS to re-launch/re-init these processes.
The re-init consequently increases memory pressure again and the LMK daemon attempts to kill even more processes, even those that were just initialized. A lot of signal 9 events occur during this period.
This cycle of allocation-deallocation adversely affects the system responsiveness. UI interactions lag by several seconds, all app activities end up getting evicted from memory (if they don't get killed outright) leading to constant redraws, battery consumption increases noticeably.
Eventually, the phone becomes so unresponsive that unlocking it takes several seconds before the launcher is shown.
Throughout this process, the system memory viewer (in Settings > System >Developer Settings) shows that of teh 5.8GB of available RAM, 1.6GB is free. The average RAM use (over a period of 3, 6 and 24 hours) shows up as ~70% (on my phone).
Finally, the phone has to be restarted. And then the entire cycle repeats itself.

The provided logs should corroborate my thesis. I have been able to reproduce this on the following:
An updated phone (updated from .110 to .119).
A phone that was factory-reset after the .110 update.
The installed apps have no discernible effect on this behaviour - It occurs even after a fresh factory-reset with no new apps installed. If you need more information, please let me know. The phone is unusable in its current state.

@Anders_ASUS
11 REPLIES 11

Lambaste
Rising Star I
_jis_

https://zentalk.asus.com/en/discussion/comment/42646#Comment_42646

You mean WW_17.1810.2001.119, so test then on WW_17.1810.2001.121 which is already available to download.


View post
Not for me, unfortunately. I have the EU (German) SKU, and the link to the update on the phone's German support page explicitly excludes the EU SKU. So, I'm stuck waiting for the OTA.

Ever since Android 9 .194, OTA have been arriving rather delayed to my phone for whatever reason.

_jis_
Zen Master III

Lambaste
Rising Star I
_jis_

@Lambaste

Do you really have EU and not WW?

https://zentalk.asus.com/en/discussion/comment/12664/#Comment_12664


View post
Looking at the model number specified in the bug report, I think so (EU_I01WD).

In any event, I guess I shouldn't have flashed the .119 update manually over .110, for which I had received an OTA update.

_jis_
Zen Master III
Don't be fooled. Read the thread I referenced again. I also have Product = EU_I01WD, but I regularly get WW firmware updates via OTA.
ZS630KL software Image:WW_17.1810.2001.121 for WW/IN/JP/RU/EU sku only

Lambaste
Rising Star I
_jis_

Don't be fooled. Read the thread I referenced again. I also have Product = EU_I01WD, but I regularly get WW firmware updates via OTA.

ZS630KL software Image:WW_17.1810.2001.121 for WW/IN/JP/RU/EU sku only


View post
I see. Do you have a link to the latest .121 OTA/update? The one found here (https://www.asus.com/de/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/) has the following note: *Special notice: This upgrade patch only allows to upgrade from Android P 16.1220.1909.194 version to Android Q. The other firmware version can't use this patch file to upgrade.