Strange scheduling data

[elem089]

recently changed the scedule from "daily" to "every 3 days".
looking at the interface now it says that the last backup ran ~6 hrs ago, which I can confirm. Accoring to the app the next backup is scheduled in ~23 hrs.
Setting still says "every 3 days" I'll see whether it really runs tomorrow; I'll post an update then

Current version is 14-4.0, running with LineageOS 21 on OnePlus 6

[grote]

What happens after you change it to daily and then back to three days? If it stays at in ~23h, can you export the logcat form expert settings?

[elem089]

Just wanted to write an update:
found out that the backup again ran this morning. Set it to "once a week" then back to 3 days. Let's see what happens.
BTW: there's also a discussion going on at one of the OnePlus 6 threads (https://xdaforums.com/t/rom-official-enchilada-14-lineageos-21.4656607/page-13) from post #251 onwards which might be related: last week I observed that the backup would end up in an endless loop trying again and again to baackup a set of APKs while the device was hooked up to the charger. The device was thus heating up. As soon as I unplugged the charger the backup stopped and the heat was going back to normal. This happened for quite a few days in a row, and as far as I remember it started with on of the May Lienage-OS updates (Unfortunately I can't exactly say when)
In that thread others are reporting that as well.
Since I disabled then re-enabled the backup-Mgr through shell commands this has not happened again.
Should it re-appear I will open a separate issue here, but I wanted to mention it anyways

[grote]

If something like this happens, please export logs immediately, so we can investigate.

[grote]

Set it to "once a week" then back to 3 days. Let's see what happens.

What is shown in the UI for the next estimated run time?

[elem089]

Set it to "once a week" then back to 3 days. Let's see what happens.

What is shown in the UI for the next estimated run time?

right now it says "in 3 days" which would exactly be what I set it to. Hopefully I managed to properly reset the config data. I'll post an update

[elem089]

If something like this happens, please export logs immediately, so we can investigate.

I absolutely would have done so if I had thought about looking for this repository. Too late now.
But I can ask one of the other users at XDA if they still have that. Hopefully they can grab a log before they themselves manage to reset the app

[elem089]

Update on the schedule:
Scheduler is still set to "every 3 days". According to the settings next estimated backup should take place early Sunday morning (CEST timezone), and this is what it says since 2 days ago (see 2 posts up from here).
But last night (at ~23:50 CEST, i.e. ~11 hrs ago) a backup was written.
So apparently Seedvault simply neglects the scheduling settings, it takes backups ~once a day here
I took a snaphot from the logs this morning, but this (of course) started way after the last backup ran (at ~07:50).
If you think it might be of any use to you let me know

BTW: let's forget about the looping / heating problem. I'll open a new issue ticket should this re-appear

[grote]

Thanks for the report. Could you give me the output of adb shell dumpsys jobscheduler | grep -B 6 -A 33 "Service: com.steve" please?

[elem089]

sorry, been away from my desk yesterday.
Before I post the dumpsys result one more observation:
before I ran the shell command I had one more look at the current settings of Seedvault. It was telling me something like "will start as soon as one of the prerequisites were fullfilled". Which is exactly my impression: I'm having 2 options active: backup every 3 days AND only backup if being charged. I feel that the backup starts as soon as one of the options is TRUE.

20240626_dumpsys_elem089_oneplus6_LOS21.txt

[grote]

I'm having 2 options active: backup every 3 days AND only backup if being charged. I feel that the backup starts as soon as one of the options is TRUE.

No this shouldn't be it.

The last line in your textfile says: Run time: earliest=+2d23h56m, so it shouldn't run earlier than this.

Also note: Unsatisfied constraints: CHARGING TIMING_DELAY [0x80000001]

Timing delay means that the earliest run time hasn't arrived, yet. Charging means that even if the time has come, it still will wait until you charge the device.

before I ran the shell command I had one more look at the current settings of Seedvault. It was telling me something like "will start as soon as one of the prerequisites were fullfilled".

Yes the earliest next runtime is roughly 3 days, so it indicates that the previous run has just happened, maybe because you connected a cable for adb.

This looks all as expected here. Did you still notice anything off?

[elem089]

"This looks all as expected here. Did you still notice anything off?"
not really "off". But yesterday morning I ran the latest OTA (lineage 21.0 build 20240626), after that rebooted one more time for some other reason.
Phone was on the charger twice since since I pulled that sys dump, i.e. since last backup. SeedVault says last update was "day before yesterday", i.e. 2024-06-26. Which is also the most recent time stamp I see in the backup files. And it keeps telling me next backup would be tomorrow.
So there is a chance that something adjusted. Probably through something that came with the latest OTA? I'll keep an eye on it