Google(!) recommends that you back up your phone to the cloud.
My phone has 256GB of internal storage plus a 256GB SD card.
Internal storage has 102.5 GB used.
External storage has 34.3 GB used.
Google provides 5GB of storage free.
-u1.59 a month provides 100GB of storage which would just about do if I backed up some data to the PC and deleted it from the phone.
Does anyone pay monthly to Google for backup capability?
If not, what strategy do you use?
Google(!) recommends that you back up your phone to the cloud.
My phone has 256GB of internal storage plus a 256GB SD card.
Internal storage has 102.5 GB used.
External storage has 34.3 GB used.
Google provides 5GB of storage free.
-u1.59 a month provides 100GB of storage which would just about do if I backed up some data to the PC and deleted it from the phone.
Does anyone pay monthly to Google for backup capability?
If not, what strategy do you use?I let the phone backup its "data" contacts, photos, calendar, sms, call-history etc to google's cloud.
Google(!) recommends that you back up your phone to the cloud.
My phone has 256GB of internal storage plus a 256GB SD card.
Internal storage has 102.5 GB used.
External storage has 34.3 GB used.
Google provides 5GB of storage free.
-u1.59 a month provides 100GB of storage which would just about do if I backed up some data to the PC and deleted it from the phone.
Does anyone pay monthly to Google for backup capability?
If not, what strategy do you use?
Cheers
Dave R
Google(!) recommends that you back up your phone to the cloud.I connect the phone to a PC and just copy all the contents visible
My phone has 256GB of internal storage plus a 256GB SD card.
Internal storage has 102.5 GB used.
External storage has 34.3 GB used.
Google provides 5GB of storage free.
-u1.59 a month provides 100GB of storage which would just about do if I backed up some data to the PC and deleted it from the phone.
Does anyone pay monthly to Google for backup capability?
If not, what strategy do you use?
David <wibble@btinternet.com> wrote:<snip>
Google(!) recommends that you back up your phone to the cloud.
My phone has 256GB of internal storage plus a 256GB SD card.
Internal storage has 102.5 GB used.
External storage has 34.3 GB used.
Google provides 5GB of storage free.
-u1.59 a month provides 100GB of storage which would just about do if I
backed up some data to the PC and deleted it from the phone.
Does anyone pay monthly to Google for backup capability?
If not, what strategy do you use?
Finally, try and keep a list of the apps you've added to your phone.
Much of the storage used is probably apps and there's no point in
backing them up, you can download and install them again. You just need
some sort of record so you don't have to go through the pain of choosing which apps you need again.
u1.59 a month provides 100GB of storage which would just about do if I
backed up some data to the PC and deleted it from the phone.
Does anyone pay monthly to Google for backup capability?
Finally, try and keep a list of the apps you've added to your phone.
Much of the storage used is probably apps and there's no point in
backing them up, you can download and install them again. You just need
some sort of record so you don't have to go through the pain of choosing
which apps you need again.
I have a large number of Apps on my phone, so I wouldn't want to spend a long time re-installing them all.
There is also the data associated with the Apps.
I am looking for a way of transferring the configuration to another phone, or restoring to the original in the event of a catastrophe of some sort.
To my mind that is what backups are for.
If not, what strategy do you use?I let the phone backup its "data" contacts, photos, calendar, sms, call-history etc to google's cloud.
Does anyone pay monthly to Google for backup capability?I connect the phone to a PC and just copy all the contents visible
If not, what strategy do you use?
thereby to a sub-directory on the PC, and from there it's backed up to
my NAS.
This isn't UK telecom related, but how do you backup/restore your apps?
And your app data?
On 2026-08-03 14:22, David wrote:
Google(!) recommends that you back up your phone to the cloud.
My phone has 256GB of internal storage plus a 256GB SD card.
Internal storage has 102.5 GB used.
External storage has 34.3 GB used.
Google provides 5GB of storage free.
-u1.59 a month provides 100GB of storage which would just about do if I
backed up some data to the PC and deleted it from the phone.
Does anyone pay monthly to Google for backup capability?
If not, what strategy do you use?
I connect the phone to a PC and just copy all the contents visible
thereby to a sub-directory on the PC, and from there it's backed up to
my NAS.
It's more that I let Play Store remember the list of apps I have
installed ... when a screen went faulty on a phone and I swapped it in-store, it installed all the right apps.
And your app data?
Again mostly through apps making use of Backup&Restore or BackupAgent
onto to google cloud, I know a couple of my apps don't use that
facility, so I have to manually export settings for them (Thunderbird
being one, I don't need to export the actual emails as that's IMAP).
Did you get your original home screen back when it swapped the apps?
Thanks. App data is the hardest thing, nowadays, to ensure gets recovered. Mainly due to modern restrictions on /data/data but also due to sheer size.
Even the Google Play mechanisms won't allow more than 25MB per app.
It's my understanding that they don't allow more than 50MB per phone.
Did you get your original home screen back when it swapped the apps?
I think I got an icon for every app installed ...
Even the Google Play mechanisms won't allow more than 25MB per app.
It's my understanding that they don't allow more than 50MB per phone.
I knew it was 25MB per app, and that it doesn't count towards *my* cloud usage, wasn't aware of a 50MB per phone limit?
Again mostly through apps making use of Backup&Restore or BackupAgent
onto to google cloud, I know a couple of my apps don't use that
facility, so I have to manually export settings for them (Thunderbird being one, I don't need to export the actual emails as that's IMAP).
Thanks. App data is the hardest thing, nowadays, to ensure gets recovered. Mainly due to modern restrictions on /data/data but also due to sheer size.
David wrote:
Finally, try and keep a list of the apps you've added to your phone.
Much of the storage used is probably apps and there's no point in
backing them up, you can download and install them again. You just need
some sort of record so you don't have to go through the pain of choosing >>> which apps you need again.
I have a large number of Apps on my phone, so I wouldn't want to spend a
long time re-installing them all.
There is also the data associated with the Apps.
I am looking for a way of transferring the configuration to another phone, >> or restoring to the original in the event of a catastrophe of some sort.
To my mind that is what backups are for.
I'm not sure what this thread has to do with UK telecom, but in an exact >mirror of this topic on the operating system newsgroups (win,linux,macos), >we've been discussing the "perfect backup" solution for a few days now.
Newsgroups:
comp.mobile.android,alt.comp.os.windows-10,alt.os.linux,comp.sys.mac.apps
Subject: PSA: Script to archive working APK & APK bundles from Android to
the desktop
Date: Sat, 1 Aug 2026 11:10:31 -0800
Message-ID: <114lgb8$d6p$1@nnrp.usenet.blueworldhosting.com>
Regarding archiving all apps and their data, we have to understand that >almost everything people "think" about Apple/Google solutions, is wrong.
Unless you know what you're doing (which one out of a million people do), >you will *never* get the app backed up by either the Apple or Google highly >marketed methods, simply because both get the app from their App Stores.
a. So if the sub version you want isn't available, you lose
b. Worse, if the app is no longer on the App Store, you lose
There are ways on both platforms to back up and restore the *actual* app >(which I've posted to the Apple & Android newsgroups in the past), but my >main point is to ensure people know that the app is *never* backed up using >the conventional methods that both Google and Apple marketing promote.
Even the app data has quirks, e.g., Google limits app data to 25MB per app.
Basically, while almost the whole world uses the marketing-driven >Apple/Google backup/restore methods, they both suck for a bunch of reasons.
As for what we've been discussing for a few days now on the OS newsgroups, >IMHO, this is a much better backup/restore for Android apps and their data.
<https://github.com/mrrfv/open-android-backup>
this is a much better backup/restore for Android apps and their data.
<https://github.com/mrrfv/open-android-backup>
this is a much better backup/restore for Android apps and their data.
<https://github.com/mrrfv/open-android-backup>
Interesting ... surprised it doesn't need root on the phone?
IMHO, this is a much better backup/restore for Android apps and their data. >> <https://github.com/mrrfv/open-android-backup>
Interesting. Can it be used to setup a new Android phone? Or does it
require the original phone?
Does it recognise where the app came from eg FDroid, PlayStore etc?
for when updates are needed if restoring/re-installing to a new phone?
I've just setup a new phone and made a list of my apps with
AppListBackup and then re-installed. Possibly no bad thing because
the phone is a later version of Android and some better apps were then available.
this is a much better backup/restore for Android apps and their data.
<https://github.com/mrrfv/open-android-backup>
Interesting ... surprised it doesn't need root on the phone?
Hi Andy,
The FOSS open-android-backup x-platform tool does need root (for data). Nothing but root can bypass /data/data app-data sandboxing (AFAIK).
Maria Sophia wrote:
this is a much better backup/restore for Android apps and their data.
<https://github.com/mrrfv/open-android-backup>
Interesting ... surprised it doesn't need root on the phone?
Hi Andy,
The FOSS open-android-backup x-platform tool does need root (for data).
Nothing but root can bypass /data/data app-data sandboxing (AFAIK).
Actually, I looked deeper. I don't see any overt evidence that root will change how either Open Android Backup or the Google Backup mechanisms
work.
Root really matters mainly for the full-backup solutions that NeoBackup
or SwiftBackup perform, and not so much for OAB or for Google Backup
methods.
AnthonyL wrote:
IMHO, this is a much better backup/restore for Android apps and their data. >>> <https://github.com/mrrfv/open-android-backup>
Interesting. Can it be used to setup a new Android phone? Or does it
require the original phone?
Does it recognise where the app came from eg FDroid, PlayStore etc?
for when updates are needed if restoring/re-installing to a new phone?
I've just setup a new phone and made a list of my apps with
AppListBackup and then re-installed. Possibly no bad thing because
the phone is a later version of Android and some better apps were then
available.
Good questions! Good observations. You used a good process too.
a. Enumerate all apps on the device
b. Back them up from the old phone to the desktop
c. Restore them to the new phone from the desktop
To answer your question, yes, Open Android backup can be used to set up a
new phone based on the apps that are on the old phone, and, if you copy
over the homescreen (which is only a single file), you get the new apps in >the exact same placement on the new phone as they were on the old phone.
With respect to the query of where apps came from (e.g., F-Droid, Github, >Play Store, developer web site, etc.) Open Android Backup doesn't care 'cuz >Android is unique among operating systems in how it saves installers.
To understand why Open Android Backup doesn't need to care where an app
came from, think about a situation which is becoming common on desktops.
On Windows, there are some "portable apps" which themselves, are the actual >executable (as opposed to being an installer which creates the executable).
Right?
Well, on Android, every app (even system apps!) is a portable executable.
So all Open Android Backup needs to do is collect all those executables.
If an app is installed on the phone, then the installer is *always* there!
So, Open Android Backup doesn't care where the original APK came from.
If they're on the phone, they're backed up. And they can be re-installed.
Here's a short list of what Open Android Backup backs up sans root:
a. Photos, Videos, Documents, Downloads, etc.
b. App-created files stored in or exported to /sdcard
c. Accessible app data such as contacts & chats (if exported to /sdcard)
d. Backs up SMS/Call logs (for viewing, not for restoring)
Note that root doesn't gain Open Android Backup anything special.
Just like root doesn't gain a Google Backup anything special.
But root gains NeoBackup or Swift Backup a lot.
a. Root gains cloning of the app on the new phone, and,
b. Root gains all the app data backed up to the new phone.
c. And root gains the same app system state on the new phone.
Hardware limits accepted.
When we compare an unrooted backup above with Google Backup, the methods
are completely different (e.g., Google never backs up the APKs), but Google >Backup does bring over stuff like contacts, SMS, call logs, wi-fi
passwords, bluetooth pairings, launcher layout, Google & Samsung accounts, >app permissions & notification settings, system settings, etc.
So all three methods are fundamentally different in critical ways.
A. Open Android Backup is really about archiving apps to the desktop
B. Swift/NeoBackup are really about full backup/restore when rooted
C. Google Backup is really more about bringing over the same setup
As always, anything I say can be wrong (and probably is), so please
fix where I err or omit so that we end up with more knowledge overall.
Very useful information.
I might just try restoring a not too old phone to an older (but not
too old) redundant phone. No doubt some apps won't run but it'll be a
very handy learning process if ever I need to do it again. Bearing in
mind I'm entering my 80th year and have just replaced my 8yr old phone
so I met get away with not having to bother.
Root really matters mainly for the full-backup solutions that NeoBackup
or SwiftBackup perform, and not so much for OAB or for Google Backup
methods.
Thanks to all for the helpful information.
Maria Sophia wrote:
Thanks. App data is the hardest thing, nowadays, to ensure gets recovered. >> Mainly due to modern restrictions on /data/data but also due to sheer size. >>
Even the Google Play mechanisms won't allow more than 25MB per app.
It's my understanding that they don't allow more than 50MB per phone.
I knew it was 25MB per app, and that it doesn't count towards *my* cloud usage, wasn't aware of a 50MB per phone limit?
On Andoid (and I guess IOS) app configuration and data is stored
(mostly) by the app in its own private space, often not even directly accessible by the user.
adb backup -f novadata.ab -noapk com.teslacoilsw.launcherWARNING: adb backup is deprecated and may be removed in a future release
java -jar abe-38fd634.jar unpack novadata.ab backup.tar [passwd]0% 1% 2% 3% 4% 5% 6% 7% 8% 9% 10% 11% 12% 13% 14% 15% 16% 17%
As my entire life is not on my phone I only back it up monthly or when
there is something important on it such as new photos etc.
# -------------------------------------------------------------------
# apkhome.py
# Replicates Android homescreen panes/folders/apps/apk(s) on the PC
# Usage: python apkhome.py
# -------------------------------------------------------------------
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 58:16:31 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
4 files (9,632K bytes) |
| Messages: | 285,959 |