Warning: mysqli::__construct(): (HY000/1203): User howardkn already has more than 'max_user_connections' active connections in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\includes\artfuncs.php on line 21
Failed to connect to MySQL: (1203) User howardkn already has more than 'max_user_connections' active connections
Warning: mysqli::query(): Couldn't fetch mysqli in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\index.php on line 66
Article <lrmpmdFbgjbU2@mid.individual.net>
Deutsch   English   Français   Italiano  
<lrmpmdFbgjbU2@mid.individual.net>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Arno Welzel <usenet@arnowelzel.de>
Newsgroups: comp.mobile.android
Subject: Re: What is your experience with Samsung "RAM Plus" virtual memory
 expansion?
Date: Mon, 9 Dec 2024 00:50:36 +0100
Lines: 41
Message-ID: <lrmpmdFbgjbU2@mid.individual.net>
References: <virg1h$eif$1@nnrp.usenet.blueworldhosting.com>
 <viu7ob$26lh3$1@dont-email.me> <lrfpj4F77p6U1@mid.individual.net>
 <vius10.17o.1@ID-201911.user.individual.net>
 <lriun1Fmn2pU3@mid.individual.net>
 <vj1l7i.1to.1@ID-201911.user.individual.net>
 <lrj30vFnapjU3@mid.individual.net>
 <vj2006.g08.1@ID-201911.user.individual.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Trace: individual.net ifbjGm4QysWeeDPtROe2bwfFSEgF7VgIGqq+Io0V2LlCAJ+xEm
Cancel-Lock: sha1:XpdHfDuYso6WKJIeRht+WdTcI5g= sha256:1HyJHk9vLk7mvfJWSFeZutPT7XRdGxJDaIxgO3YnwhU=
Content-Language: de-DE
In-Reply-To: <vj2006.g08.1@ID-201911.user.individual.net>
Bytes: 2807

Frank Slootweg, 2024-12-07 17:18:

> Andy Burns <usenet@andyburns.uk> wrote:
>> Frank Slootweg wrote:
>>
>>>    My/the point is that not all appscan be designed that way. It might
>>> be that if they can be designed that way, they must be designed that
>>> way. But an app developer can not be required to do the impossible.
>>>
>>>    Note that I specifically mentioned external data or/and state. If an
>>> app is killed, external data or/and state might/will be lost and the app
>>> cannot recover when restarted. Examples of such apps are apps which
>>> depend on data from (internal or external sensors or other data
>>> sources).
>>
>> They can save the most recent sensor values as part of their state, so 
>> if they get killed, they can use the saved value rather than re-reading 
>> the value from the sensor.
> 
>   Yes, but they will miss the sensor data that was generated between the
> time the app was killed and when it was restarted. Think tracking/

To keep things running in Android, there are *services* besides apps.
These don't get killed regularly and can be triggered by events like "x
seconds hev passed" or "location has changed at least 10 meters", "IP
packet was recieved" etc. but they may drain the battery if not properly
implemented.

[...]
>   Like I said, if paging/swapping wasn't needed, computers wouldn't have
> those functionalities, because one 'disk'-access (load-only) is faster
> than two (page/swap out and back in).

When paging was invented, it did *not* use regular file I/O but a
dedicated hard disc partition where RAM pages where written directly to
hard disc sectors which is *faster* than reading files.


-- 
Arno Welzel
https://arnowelzel.de