Hi, I am a joplin user. Plan to make a patch to let joplin do background sync in android. I plan to use HeadlessJS of React Native to achive this purpose. The code size will be quite big. Per guild in source, I need to start discussion in this forum. So I created this topic. If you have any question about it, please ask it. Regards, Chen Yang

Thanks to Chen for this fantastic improvement. Just coming from Evernote I am actually baffled at what Joplin can do. Background syncing is also for me a missing feature. Not because Evernote could do it (it does not) but because sync on Joplin is longer (in spite of the fact I use Joplin Cloud) and particularly so with encryption (which Evernote can also not do) Any chance that this background sync makes the main distribution? Is the non iOS readiness a show stopper for a full deployment?

Still using it daily? Any downsides? I'm tempted to try it out. Will I need to rebuild the resources/database at the first sync? Is it better to uninstall the official Joplin apk first, with all its data/cache? Also, does it drain the battery a lot when not in use? Thanks for this great addition

Oh @Chen you're amazing! Would you mind creating a Pull Request for this after putting it behind a beta option? There were already other settings like that: [image] Maybe Lauren would consider merging it then. Thank you so much for your work! I was waiting for this since ages!

[image] alexanderadam: Oh @Chen you're amazing! Would you mind creating a Pull Request for this after putting it behind a beta option? There were already other settings like that: [image] Maybe Lauren would consider merging it then. Thank you so much for your work! I was waiting for this since ages! It's good to see that my message was helpful for you. Unfortunately, @Chen 's application is not working. When the synchronization button is pressed, the application freezes.

Hi, Sorry for later reply. What a busy april! My application was just a prototype, it contains some bug. As far as I observed, sometime, it will block phone to sleep. Still try to find time to debug it. I can merge the latest change when I have time. Hope I can finish it next month. Thanks, Chen Yang

Hello @Chen , I hope everything is going well for you in April. You're doing an amazing job, truly. Thank you so much. It's wonderful to read your message again. Know that there are followers eagerly awaiting your work.

Hi @Chen, would you happen to have any updates on implementing background sync?

I am also eagerly following the topic of mobile background syncing as my wife does not “follow the rules” to make mobile syncing work so I end up having to sync her phone manually all the time and resolve conflicts (as she expects it to “just work” - we transitioned from OneNote where syncing wasn’t always perfect but at least she didn’t have to open the app - sync it - make the changes - then sync it again before closing). this would be a giant improvement in my quality of life to have this working! @Chen I am hoping you will pick up this work again and save us all from our sync problems! If nothing else - I wanted to bump this topic and keep it open in the hopes someone will pick it up and get at least Android syncing in the background.

I had another look into the topic. It’s been a while since I followed discussions on background sync, but the PR which was rejected due to ‘reliability reasons’ implemented a background service, for which the Android OS enforces some strict limitations. However I don’t recall if anyone has ever proposed implementing a foreground service (as an Android only solution, probably not applicable to iOS). Supposedly this should not be too difficult to implement for a React Native app (see 🚀 Implementing Foreground Services in React Native for Android 🚀🚀 - DEV Community ) A foreground service requires a persistant notification to remain active, but as far as I can tell they have less restrictions compared to a background service. It would require writing some native Android code, and I’m guessing the only thing which may not be straightforward to implement would be to allow the user to opt out of the background sync (if they don’t want to have the persistent notification and additional battery usage), which may require writing a UI to toggle this in native Android code, as I’m not sure the node code would be able to have access to this configuration EDIT: Looking at the code in the linked article, it seems you can start and stop the service from js code, so likely you can use the existing setting screens to toggle whether to use the service

Background sync in android

Features

Chen 1 October 2024 16:58 31

Too many activities in this summer. Hope to find time at the end of the year.

Topic		Replies	Views
Android (background) sync interval Support	61	5590	17 August 2025
Sync in background Features	10	1211	15 May 2024
Sync issues Support	11	375	23 April 2026
The Inability of the Mobile Joplin Application to Perform Background Synchronization Support	2	389	17 April 2024
Joplin Android App Synchronization Support	3	683	3 August 2021

Background sync in android

Related topics