Android subsystem "AlienDalvik" reports isLowRamDevice() to apps

[ExTechOp]

REPRODUCIBILITY (% or how often): 100%
BUILD ID = OS VERSION (Settings > About product): 4.1.0.24 (Kvarken)
HARDWARE (XA2, Xperia 10…): XA2 Ultra
UI LANGUAGE: English
REGRESSION: (compared to previous public release: Yes, No, ?): ?

DESCRIPTION:

Android subsystem reports device as “low RAM”, ie. there isn’t much memory available:

ActivityManager  |  Android Developers

This will affect some Android software adversely, since they disable memory-intensive features.

PRECONDITIONS:

Unknown.

STEPS TO REPRODUCE:

1. Install Android application which uses isLowRamDevice() to determine its behavior, eg. Signal
2. Run the application

EXPECTED RESULT:

Application works normally in the Android subsystem.

ACTUAL RESULT:

Application is told it is running in a “low RAM” system, and disables parts of the UI in an effort to conserve memory. For example, Signal will only send images in very low 768×432 resolution and not even display a image quality selector tool.

ADDITIONAL INFORMATION:

Could this be related to the issue with memory level reported by Mode Control Entity?

[4.1.0.24][Xperia 10 II] Unknown memory level reported by MCE

REPRODUCIBILITY: always OS VERSION: 4.1.0.24 HARDWARE: Xperia 10 II UI LANGUAGE: cz REGRESSION: no (on this device) DESCRIPTION: I am using memory level reported by MCE daemon for controlling application caches to avoid attention low-memory-killer. But on Xperia X II, MCE always reports “unknown” level. By wiki page Mce - SailfishOS Documentation , it may happen when kernel subsystem memnotify is missing. It is correct, device /dev/memnotify is not present on the device (but it exists on o…

[Se]

I have the same Bug. The Same Hard- and Software version as ExTechOp.
My IU Language is German

[abranson]

The Android system image is intentionally built with an Android Go configuration to reduce its memory footprint, as its usual flagrant RAM consumption isn’t appropriate for a guest OS. Perhaps we could see if we could limit that to system components so that apps wouldn’t do this sort of thing.

[ExTechOp]

Verified still to be the situation with SFOS 4.2.0.19 Verla.

[shults]

Is this.issue connected with the disabled option for android apps to show over other apps?
This was disabled since android 10 was updated before it was ok.

[olf]

@abranson

The Android system image is intentionally built with an Android Go configuration to reduce its memory footprint, as its usual flagrant RAM consumption isn’t appropriate for a guest OS. Perhaps we could see if we could limit that to system components so that apps wouldn’t do this sort of thing.

That would be great, because numerous Android apps limit themselves functionally (in various ways), when isLowRamDevice() is indicated to them.
Which is exactly what is intended (according to the documentation): This is mostly intended to be used by apps to determine whether they should turn off certain features that require more RAM.

Thus, while configuring the Android Runtime Environment “AlienDalvik” to limit its RAM usage is fine, exposing isLowRamDevice() to apps is not, IMO.

[ExTechOp]

Just loaded SFOS 4.3.0.12 (Suomenlinna) and I suspect this issue has now been corrected, as a selector for photo quality showed with Signal 5.25.7 and I was able to send a 3072×2304 picture with it.

[abranson]

Yeah we found other ways to save RAM and managed to drop that lowram flag.

[Se]

Great work, thank you.