Skip to main content

import_step

Function import_step 

Source
fn import_step(
    android: &dyn Android,
    files: &Files,
    seal: &Seal,
    vault: &(PathBuf, [u8; 32]),
    region: Option<&Region>,
    now: i64,
    all: bool,
) -> bool
Expand description

One step of the import (docs/texts.md, “Reading, on the phone: paced”). Every row the phone holds is listed with its date (texts-ids), and those its log lacks are the ones to read, wherever their ids are (the plain texts’ table gives a deleted newest text’s id to the next one; a provider emptied starts again at 1). Rows that appeared since the last step are read at once, on the battery too, oldest first; 500 or more at once are no texts that came but a block of old ones (SMS Backup & Restore restoring a history), read as a first import is: the newest first by date, with all (on the charger) BATCH at a time, else only those newer than the newest text read before and than a day before the history was found, so that a text that comes meanwhile reaches your computers within a minute or two. Media within MEDIA_BATCH bytes, the first always. A step with nothing to read asks Android one listing. Whether anything was written.