Mod-edit: it’s unnecessary for other user to attempt this procedure below because it was already clarified that this is not a regression introduced in V1.7.
If you believe that this is a regression of 1.7.x and your are willing to do some work you can:
Bit of a delay because I just saw this now. I tried installing 1.6.7, and I was surprised to find that it also took a long time to load (about 2 minutes). Is there a caching mechanism that gets built slowly over time using the app? This would explain the load time discrepancies between now and when I used 1.6.x prior to a few weeks ago. More explicitly, depending on the amount of time it takes to run, either:
If this cache building mechanism exists, is there a way to “bring it to the foreground” and force it to run to completion at once? Continuing to use the 1.6.7 version over a few days will also help me disambiguate these possibilities.
Here are my debug info blocks:
SYSTEM INFO:
Operating system: android 14 (samsung SM-S918U1)
Obsidian version: 1.7.5 (168)
API version: v1.7.5
Login status: not logged in
Language: en
Live preview: off
Base theme: dark
Community theme: none
Snippets enabled: 0
Restricted mode: on
RECOMMENDATIONS:
none
SYSTEM INFO:
Operating system: android 14 (samsung SM-S918U1)
Obsidian version: 1.6.7 (149)
API version: v1.6.6
Login status: not logged in
Live preview: off
Base theme: dark
Community theme: none
Snippets enabled: 0
Restricted mode: on
RECOMMENDATIONS:
none
I am glad we ruled out regressions.
The cache building mostly happens after obsidian has started/is in a usable state. You’ll see “Obsidian is indexing your vault” notification and it’ll run when you have obsidian open.
There is some disk activity at lunch, when obsidian checks which files are present.
I can’t reproduce your problem on my Pixel 6a.
Is it possible that your specific phone vendor (Samsung) posted some android update that severely impacted the speed at which obsidian can read from disk?
When you install 1.7.4, can you post a screen recording of you whole loading sequence? thanks.
If any developers happens to have this problem, can you provide us a performance profile of app during startup By reloading the app after it loads through the connected console or using the reload without saving command.
Start Obsidian so I can use it
The same vault loads fine on Windoze
Not sure if it happened since the most recent Insider Release
I also downgraded to 1.6.7 and this still happens.
I also downgraded and still it needs minutes to load… - should I maybe factory reset my Phone? … what else could I try?
I don’t think there’s any need to downgrade anymore. I just suggested it because some of you had the doubt that this was a regression introduced by 1.7.x.
Doing a factory reset of your phone is quite traumatic and, if this is caused by a system update, the problem will manifest it’s again.
In these two posts you suppose, that some internal process of the android system is slowing down the file reading process of obsidian.
Do you have any idea how I could investigate that? For example which apps I could deactivate, which settings I could check, which system checks I could do?
In Chrome, I got a log of the console activity during reload, as well as a trace (with Web Developer options I think)- is this what you were looking for? I can DM you a link to download them since I’m not sure if the trace contains information from my vault, and it is fairly large.
yes, thanks. please DM me the link.
