Sync sometimes never finishes/is very slow
Steps to reproduce
- Don't use Element for a while
- Open Element
- Wait for it to sync
- Wait for it to sync
- Wait for it to sync
- It has taken several minutes
Outcome
What did you expect?
The sync to be very quick
What happened instead?
It took several minutes
Your phone model
M2004J19C; Moto G7 plus
Operating system version
11 (API 30) V12.5.5.0.RJCEUXM-REL; 10 (API 29) fac4a-REL
Application version and app store
1.4.13
Homeserver
matrix.org; element.io
Will you send logs?
Yes
In my case I've waited for 20 minutes without any progress.
Workaround is to unsubscribe from all the channels you don't actively participate in, then kill and start the app again.
I too believe this is probably a regression, as I'm primarily using Element from desktop and only occasionally launch it on the phone to send a pic.
Previously the android app synced within reasonable timeframe.
does the sync eventually start and complete?
does the sync eventually start and complete?
It quite certainly starts but I am not sure if it ever ends - when this happens I tend to just kill the app and start it again, the sync status then shows a decreased number of rooms to process and then finishes
Ok, so I think it does finish but it can take up to several minutes to do that
Is there any more info I could provide?
I don't see such delay in sync for iOS. In iOS they have recently also further improved by updating the Realm framework. Seems it has improved the decryption tasks performance.
https://github.com/vector-im/element-ios/issues/6239
When I receive a notification, and I tap it to view, and when the application is not used for a long , it starts syncs for around 1 to 1.5 min , before I can read the message. And user interface is little confusing, as when user expects to see the new message immediately. Can be better if at there is a progress indication for the Sync.
I increased the severity to treat this issue as a P1. We will check the issue after the completion of https://github.com/vector-im/element-android/issues/6498 and https://github.com/vector-im/element-android/issues/5842 that will change the threading model. ElementR-Android that will use the Rust crypto module will also have an impact in, hopefully, the good way.
I increased the severity to treat this issue as a P1. We will check the issue after the completion of #6498 and #5842 that will change the threading model. ElementR-Android that will use the Rust crypto module will also have an impact in, hopefully, the good way.
Do you have a rough time estimate for that?