nextcloud / nextcloud/android

Automatic backup for Whatsapp

Open
#13,485 2 comments 11 reactions 0 assignees View on GitHub
enhancement
Dominant language
Kotlin
Stars
5.6k
Forks
2k
Avg merge
2d 18h
Merged PRs (30d)
92

Description

PROBLEM
NC does not offer a backup solution out of the box for all Whatsapp data.

Considering new Google policy about Whatsapp backup weight on disk storage,
could be very helpful to EXTEND the "automatic backup" feature already implemented for photos & screenshot, ALSO to Whatsapp backup folders (messages and backups)
Considering Whtastapp is used by more than 5bilions android users (not counting Ios user...), could be a HIGH interest feature

At present time, from what it seems to me, the proposed preset backup folders regard only Whatsap/Images, Whatsapp/video, .... and NOT the main Whtatsapp directory structure required for a working backup&restore.

SOLUTION
IF the function code is similar to the one used for "just" Whatsapp Photos/videos/documents folders, it could be just one more URL to add in the code the **parent* Whatsapp Folder, with ALL the backups, messages, data ,…

the main function (extended instant upload) is already in NC [nextcloud/android#797](https://github.com/nextcloud/android/pull/797)

PROPOSAL
Maybe a better initial setup could be to preset in NC a "root" Watshapp folder (not the single Imates/videos ones) , to backup the whole thing (daily message backup, AND multimedia &documents attachment.... )
IF this is correct, the action could just be realized in a different preconfigured Whatsapp Folder (ready to be used as a backup solution)

FIX NEEDED
**I've configured NC to backup /storage/emulated/0/Android/data/com.whatsapp**
It seems to work except for a annoying "event"..

One more fix could be the syncronization between the phone and the cloud.
Each day at 2:00, tWhasup performs a backup, overwriting the eldest backup file (in a round robin idea)
The problem arise each morning with NC asking which file to keep, (the local file or the server one ?)
An approach could be to have the local file (newest backup) be automatically the one to keep.

What do you think ?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.