Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.mobile.android > #109487 > unrolled thread

Backups

Started byJeff Layman <Jeff@invalid.invalid>
First post2023-11-02 20:23 +0000
Last post2023-11-03 17:36 +0000
Articles 20 on this page of 108 — 17 participants

Back to article view | Back to comp.mobile.android


Contents

  Backups Jeff Layman <Jeff@invalid.invalid> - 2023-11-02 20:23 +0000
    Re: Backups Ed Cryer <ed@somewhere.in.the.uk> - 2023-11-02 21:06 +0000
      Re: Backups Wally J <walterjones@invalid.nospam> - 2023-11-02 17:50 -0400
    Re: Backups Wally J <walterjones@invalid.nospam> - 2023-11-02 17:29 -0400
    Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-03 06:34 +0100
    Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-03 06:38 +0100
      Re: Backups Jeff Layman <Jeff@invalid.invalid> - 2023-11-03 08:27 +0000
        Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-03 10:13 +0100
          Re: Backups Jeff Layman <Jeff@invalid.invalid> - 2023-11-04 08:46 +0000
            Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-04 10:01 +0100
              Re: Backups Jeff Layman <Jeff@invalid.invalid> - 2023-11-04 10:44 +0000
                Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-04 11:53 +0100
                Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-04 11:54 +0100
                Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-04 14:43 +0100
                  Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-04 16:13 +0100
                Re: Backups Wally J <walterjones@invalid.nospam> - 2023-11-04 21:30 -0400
                Re: Backups Theo <theom+news@chiark.greenend.org.uk> - 2023-11-05 14:24 +0000
                  Re: Backups Larry Wolff <larrywolff@larrywolff.net> - 2023-11-06 00:44 +0900
                    Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-05 18:25 +0100
                  Re: Backups Jeff Layman <Jeff@invalid.invalid> - 2023-11-05 15:57 +0000
                    Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-06 01:53 +0100
                      Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-06 11:25 +0000
                        Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-06 14:43 +0000
                          Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-06 18:28 +0100
                          Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-06 17:30 +0000
                            Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-07 15:15 +0000
                              Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-07 21:24 +0100
                        Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-06 18:29 +0100
                          Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-06 17:35 +0000
                            Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-06 18:43 +0100
                              Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-06 19:57 +0000
                                Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-06 21:38 +0100
                                  Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-06 21:08 +0000
                                    Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-06 22:14 +0100
                                    Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-07 21:26 +0100
                                      Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-07 21:35 +0100
                                      Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-07 20:49 +0000
                                        Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-08 14:53 +0000
                                          Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-08 16:12 +0100
                                            Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-08 16:33 +0000
                                              Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-08 19:54 +0100
                                                Re: Backups Kenan ÇOT <kenancot34@gmail.com> - 2023-11-08 11:18 -0800
                                          Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-09 10:17 +0000
                                            Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 12:02 +0100
                                              Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-09 12:45 +0000
                                                Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-09 13:17 +0000
                                                  Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-09 14:05 +0000
                                                    Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-09 15:22 +0000
                                                      Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-09 17:09 +0000
                                                        Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-09 19:04 +0000
                                                          Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-09 20:44 +0000
                                                            Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 21:49 +0100
                                                              Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-09 21:35 +0000
                                                                Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 23:21 +0100
                                                                  Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-10 00:06 +0000
                                                                    Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-10 15:08 +0100
                                                                      Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-10 14:44 +0000
                                                                        Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-10 18:55 +0000
                                                                          Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-10 20:10 +0100
                                                                            Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-10 21:26 +0000
                                                                              Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-10 23:09 +0100
                                                                                Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-10 23:00 +0000
                                                                                  Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-11 00:20 +0100
                                                                                    Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-11 12:55 +0000
                                                                                      Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-11 15:29 +0000
                                                                                    Re: Backups Jim Jackson <jj@franjam.org.uk> - 2023-11-14 13:04 +0000
                                                                                      Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-14 15:44 +0000
                                                                                  Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-11 15:24 +0000
                                                            Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-10 13:51 +0000
                                                              Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-10 14:40 +0000
                                                                Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-10 18:55 +0000
                                                                  Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-10 22:20 +0000
                                                                    Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-11 14:59 +0000
                                                        Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 20:44 +0100
                                                          Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-09 21:17 +0000
                                                            Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 22:38 +0100
                                                              Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-09 23:41 +0000
                                                                Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-10 15:06 +0100
                                                                  Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-10 14:45 +0000
                                                Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 15:22 +0100
                                                  Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-09 17:11 +0000
                      Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-06 17:19 +0100
                    Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-06 17:18 +0100
                  Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-06 01:54 +0100
                    Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-06 17:21 +0100
                      Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-06 18:33 +0100
                        Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-06 19:06 +0100
                          Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-06 19:13 +0100
                          Re: Backups Ed Cryer <ed@somewhere.in.the.uk> - 2023-11-06 18:49 +0000
                      Re: Backups Larry Wolff <larrywolff@larrywolff.net> - 2023-11-25 09:35 -0500
                        Re: Backups Joerg Lorenz <hugybear@gmx.net> - 2023-11-25 16:51 +0100
                          Re: Backups Arno Welzel <usenet@arnowelzel.de> - 2023-12-04 20:44 +0100
            Re: Backups Wally J <walterjones@invalid.nospam> - 2023-11-04 21:29 -0400
              Re: Backups Jeff Layman <Jeff@invalid.invalid> - 2023-11-05 16:03 +0000
        Re: Backups AJL <noemail@none.com> - 2023-11-03 09:01 -0700
    Re: Backups Theo <theom+news@chiark.greenend.org.uk> - 2023-11-03 13:31 +0000
      Re: Backups Adrian <bulleid@ku.gro.lioff> - 2023-11-03 14:25 +0000
        Re: Backups Andy Burns <usenet@andyburns.uk> - 2023-11-03 14:38 +0000
          Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-03 16:38 +0000
            Re: Backups Andy Burns <usenet@andyburns.uk> - 2023-11-03 17:34 +0000
        Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-04 02:52 +0100
          Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-04 11:39 +0000
      Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-03 16:43 +0000
        Re: Backups Theo <theom+news@chiark.greenend.org.uk> - 2023-11-03 21:42 +0000
          Re: Backups Dave Royal<dave@dave123royal.com> - 2023-11-03 22:53 +0000
          Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-04 11:05 +0000
          Re: Backups Wally J <walterjones@invalid.nospam> - 2023-11-04 14:24 -0400
    Re: Backups Andy Burns <usenet@andyburns.uk> - 2023-11-03 17:36 +0000

Page 1 of 6  [1] 2 3 4 5 6  Next page →


#109487 — Backups

FromJeff Layman <Jeff@invalid.invalid>
Date2023-11-02 20:23 +0000
SubjectBackups
Message-ID<ui10fo$2c6a8$1@dont-email.me>
Any views about backing up an Android phone? When I used Windows, I 
regularly backed that up with Acronis or EaseUS Todo to an external 
drive. Now I'm using Linux, I backup data ("Backups") to external USB 
sticks and OS (Timeshift - not strictly a backup) to the internal HD. 
Backing up to an external drive has always been very straightforward, 
but Android seems less accommodating.

I should say that I have very little need to backup my phone, as I don't 
use it for anything important. If I take any photos I want to keep, I'll 
copy them to my laptop within a day. I also never use Cloud storage.

My Xiaomi phone has a built-in backup app, but of course that seems to 
require a Xiaomi account with backup to Xiaomi cloud storage. However, a 
little more digging into "Settings" reveals it can store in The Cloud, 
or locally - either as "Mobile Device - Back up and restore items on 
this device", or "Computer - Back up and restore it". However, the 
"Mobile Device" backup says "This feature allows you to backup and 
restore items using your mobile device and computer. This feature needs 
to connect to the internet and requires the following mandatory 
permissions to work:" There follows a list with accessing contacts and 
call history for backing up, and editing contacts and call history to 
restore, accessing storage for backing up files, and saving items to 
storage for restoring items (what these items are it doesn't specify. 
Are they files?). Finally it needs to access messages to back them up 
(but there's nothing about restoring them). Why does it have to do this 
through the internet, though? I have to agree to this before progressing 
to the next info page, but haven't done so, so don't know exactly how 
the computer is involved.

Looking at other backup apps on Play Store or F-Droid shows how confused 
the picture is. Some backup specifics like apps, contacts, SMS/MMS 
messages, or photos, while others do several. Some state they can't 
backup data as root access is required. Some say they can backup to an 
internal card, and only then copy from that card to an external store.

Why is backing up in Android apparently so complicated? Why can't I do 
as simply as I would with Windows or Linux via USB (or Wi-Fi)? And I 
haven't even looked at the issue of whether or not it is straightforward 
to restore from a backup.

-- 

Jeff

[toc] | [next] | [standalone]


#109490

FromEd Cryer <ed@somewhere.in.the.uk>
Date2023-11-02 21:06 +0000
Message-ID<ui132d$2d4v0$1@dont-email.me>
In reply to#109487
Jeff Layman wrote:
> Any views about backing up an Android phone? When I used Windows, I 
> regularly backed that up with Acronis or EaseUS Todo to an external 
> drive. Now I'm using Linux, I backup data ("Backups") to external USB 
> sticks and OS (Timeshift - not strictly a backup) to the internal HD. 
> Backing up to an external drive has always been very straightforward, 
> but Android seems less accommodating.
> 
> I should say that I have very little need to backup my phone, as I don't 
> use it for anything important. If I take any photos I want to keep, I'll 
> copy them to my laptop within a day. I also never use Cloud storage.
> 
> My Xiaomi phone has a built-in backup app, but of course that seems to 
> require a Xiaomi account with backup to Xiaomi cloud storage. However, a 
> little more digging into "Settings" reveals it can store in The Cloud, 
> or locally - either as "Mobile Device - Back up and restore items on 
> this device", or "Computer - Back up and restore it". However, the 
> "Mobile Device" backup says "This feature allows you to backup and 
> restore items using your mobile device and computer. This feature needs 
> to connect to the internet and requires the following mandatory 
> permissions to work:" There follows a list with accessing contacts and 
> call history for backing up, and editing contacts and call history to 
> restore, accessing storage for backing up files, and saving items to 
> storage for restoring items (what these items are it doesn't specify. 
> Are they files?). Finally it needs to access messages to back them up 
> (but there's nothing about restoring them). Why does it have to do this 
> through the internet, though? I have to agree to this before progressing 
> to the next info page, but haven't done so, so don't know exactly how 
> the computer is involved.
> 
> Looking at other backup apps on Play Store or F-Droid shows how confused 
> the picture is. Some backup specifics like apps, contacts, SMS/MMS 
> messages, or photos, while others do several. Some state they can't 
> backup data as root access is required. Some say they can backup to an 
> internal card, and only then copy from that card to an external store.
> 
> Why is backing up in Android apparently so complicated? Why can't I do 
> as simply as I would with Windows or Linux via USB (or Wi-Fi)? And I 
> haven't even looked at the issue of whether or not it is straightforward 
> to restore from a backup.
> 

All phone companies I've used offer their own backup services; Google, 
Huwaei, Samsung. You find them usually pre-installed on your phone.

I have a feeling, however, that you're a Windows-conditioned-man, and 
are used to independent imaging and cloning software.
If so, I'm on your side. But I don't know where to get it.

Ed

[toc] | [prev] | [next] | [standalone]


#109494

FromWally J <walterjones@invalid.nospam>
Date2023-11-02 17:50 -0400
Message-ID<ui15ib$1l91$1@paganini.bofh.team>
In reply to#109490
Ed Cryer <ed@somewhere.in.the.uk> wrote 

> I have a feeling, however, that you're a Windows-conditioned-man, and 
> are used to independent imaging and cloning software.
> If so, I'm on your side. But I don't know where to get it.

We've discussed backup solutions (e.g., Titanium backup & SMS/MMS backups)
umpteen times on this newsgroup so I have nothing new to offer other than a
summary that backup is so trivial that it happens automatically every day.

For example, all your Android phones are already mounted over your Wi-Fi
LAN as a drive letter on Windows - so why not use Windows backup tools?
 <https://i.postimg.cc/BvJdKWzt/webdav06.jpg> Both sdcards mounted

The entire Android phone is simply a set of files on the Windows filesys.

Why can't you copy your entire Android user storage over to Windows?
(Actually, you'd likely copy it to a 5TB drive hanging off Windows).

Like this:
 <https://i.postimg.cc/zD9P15FX/sdcard11.jpg> OsmAnd~ Windows confirmation
 <https://i.postimg.cc/ZK4pNMTx/sdcard12.jpg> OsmAnd~ Android confirmation

Hence... 

What's to stop you from simply _copying_ the entire Android phone to 
Windows (even if you're not rooted - as most files are read access)?

Even all your APKs are saved to a Windows drive letter upon installation.
 <https://i.postimg.cc/c4PrjSwx/aurora19.jpg> Save all APKs upon install
(Actually, to be clear, they're "not deleted", but that's the same thing.)
 <https://i.postimg.cc/V6tyDpNd/aurora17.jpg> Don't delete APKs postinstall

The point is you can _copy_ Android to Windows even if you don't mount it.
 <https://i.postimg.cc/BvJdKWzt/webdav06.jpg> Both sdcards mounted

For example, let's take the trivial example of copying the HOSTS file
from Android over to Windows (as just the simplest of examples).

On Windows, you run this command - and the HOSTS file is backed up.
 C:\> adb pull /system/etc/hosts .\hosts.txt
      That should copy the hosts file over even if you're unrooted.

Anyway, all this has been covered umpteen times on this newsgroup.
In gory detail.

My main point is that Android _is_ Windows.
The files are the same.

A "copy" of Android to Windows is trivial.

And vice versa (although you wouldn't usually copy Windows to Android
except for when you install your APK from your Windows file system).
 <https://i.postimg.cc/wvsbcNBz/scrcpy05.jpg> Drag APK from Windows


 

[toc] | [prev] | [next] | [standalone]


#109492

FromWally J <walterjones@invalid.nospam>
Date2023-11-02 17:29 -0400
Message-ID<ui14ba$1jco$1@paganini.bofh.team>
In reply to#109487
Jeff Layman <Jeff@invalid.invalid> wrote 

> Any views about backing up an Android phone? 

It's a perennial topic which comes up frequently on this newsgroup.
While backup is trivial, you should plan ahead for a proper backup.

For example, the Android phone and Windows are the same file system.

Every Android phone in your house is mounted to every Windows PC.
 <https://i.postimg.cc/QtbR1GY0/webdav13.jpg> 

Over the WI-Fi Lan. So if you're at home - it's the same file system.
 <https://i.postimg.cc/hjkVFyqJ/scrcpy07.jpg>

Plus the apps can be installed from Windows simply by sliding them.
 <https://i.postimg.cc/wvsbcNBz/scrcpy05.jpg> 

And they can be deleted from Windows simply by running adb commands.
 <https://i.postimg.cc/3xz7Qtrn/adb06.jpg> 

All this stuff has been covered in gory detail on this newsgroup.

Suffice to summarize Android & Windows are exactly the same files.
You can act on Windows files from Android & vice versa all you want.

Meaning backup up Android is no different than backing up Windows.
They're the same files on both systems, in fact. And the same GUI.
 <https://i.postimg.cc/k5gv0yw8/vysor34.jpg> 

> When I used Windows, I 
> regularly backed that up with Acronis or EaseUS Todo to an external 
> drive. Now I'm using Linux, I backup data ("Backups") to external USB 
> sticks and OS (Timeshift - not strictly a backup) to the internal HD. 
> Backing up to an external drive has always been very straightforward, 
> but Android seems less accommodating.

Google makes it pretty easy to back up & restore any Android phone.
So does Samsung.
Not sure about the other OEMs.

It requires an account though.

> I should say that I have very little need to backup my phone, as I don't 
> use it for anything important. If I take any photos I want to keep, I'll 
> copy them to my laptop within a day. I also never use Cloud storage.

Everyone organizes their kitchen utensils differently but everyone
organizes them. Organizing Android is no different than your kitchen.

It looks complex but it's the same in every kitchen where forks go with the
forks & spoons, the pots with the pots & pans, the dishes with the bowls
and saucers, etc. It's not any different with Android.

Most people have the camera set to store the images/videos on the external
sdcard (and if they don't have one, they usually have huge internal storage
because, basically, the only phones without the sd slot are the very high
end phones where people are supposed to pay more for internal storage and
also pay more for the cloud storage to compensate for the loss of the
sdcard slot). IMHO.

> My Xiaomi phone has a built-in backup app, but of course that seems to 
> require a Xiaomi account with backup to Xiaomi cloud storage. 

Most of the apps will require an account. The canonical backup app is
"titanium backup", but it has requirements to (e.g., root access).

> However, a 
> little more digging into "Settings" reveals it can store in The Cloud, 
> or locally - either as "Mobile Device - Back up and restore items on 
> this device", or "Computer - Back up and restore it". However, the 
> "Mobile Device" backup says "This feature allows you to backup and 
> restore items using your mobile device and computer. This feature needs 
> to connect to the internet and requires the following mandatory 
> permissions to work:" There follows a list with accessing contacts and 
> call history for backing up, and editing contacts and call history to 
> restore, accessing storage for backing up files, and saving items to 
> storage for restoring items (what these items are it doesn't specify. 
> Are they files?). Finally it needs to access messages to back them up 
> (but there's nothing about restoring them). Why does it have to do this 
> through the internet, though? I have to agree to this before progressing 
> to the next info page, but haven't done so, so don't know exactly how 
> the computer is involved.

What seems to be happening, at least for me, as I usually get my phones for
free or low cost, is that the expansion cards are vastly bigger than my
internal storage. 

When I had 16GB Androids, I had 32GB expansion cards.
When I had 32GB Androids, I had 64GB expansion cards.
When I had 64GB Androids, I had 128GB expansion cards.

The expansion card can hold more than the internal storage of the phone so
everything I wanted to make a copy of would be saved to the expansion card.

> Looking at other backup apps on Play Store or F-Droid shows how confused 
> the picture is. Some backup specifics like apps, contacts, SMS/MMS 
> messages, or photos, while others do several. Some state they can't 
> backup data as root access is required. Some say they can backup to an 
> internal card, and only then copy from that card to an external store.

Again, we've covered in gory detail all the SMS/MMS backup solutions.
There are many.

> Why is backing up in Android apparently so complicated? 

It's not. It's no more complicated than your kitchen is.

> Why can't I do 
> as simply as I would with Windows or Linux via USB (or Wi-Fi)? And I 
> haven't even looked at the issue of whether or not it is straightforward 
> to restore from a backup.

I do on Windows exactly what I do on Android and it works fine for me.
But I'm organized.

For example, I use the Nova free app launcher which saves the organization
of the homescreen folders and apps, and it backs them up to a file.

That way I can just reload that file into any other phone and all the app
icons in all the app folders in all the same positions is installed.

For my photos I keep them on the (always twice-the-size) external sd card.
Same with all my maps.
And videos.

For my other files, I keep a folder called "0000" on the internal sdcard.
And I keep a folder called "0001" on the external sdcard.

And I put everything I care about there.
That way, those are the only two folders I have to care about copying.

As for the apps, they're automatically backed up to a Windows drive letter
the instant they're installed (as the APK is simply not deleted).

All this would take me a while to re-explain but EVERY SINGLE THING I've
explained above we've covered on this newsgroup already in gory detail.

[toc] | [prev] | [next] | [standalone]


#109498

FromJörg Lorenz <hugybear@gmx.net>
Date2023-11-03 06:34 +0100
Message-ID<ui20ov$2lfsq$2@dont-email.me>
In reply to#109487
Am 02.11.23 um 21:23 schrieb Jeff Layman:
> I also never use Cloud storage.

In this case you are missing the most comfortable and most reliable way 
to backup your Android on the go with Google.

-- 
Gutta cavat lapidem (Ovid)

[toc] | [prev] | [next] | [standalone]


#109499

FromJörg Lorenz <hugybear@gmx.net>
Date2023-11-03 06:38 +0100
Message-ID<ui2103$2lfsq$3@dont-email.me>
In reply to#109487
Am 02.11.23 um 21:23 schrieb Jeff Layman:
> Any views about backing up an Android phone? When I used Windows, I
> regularly backed that up with Acronis or EaseUS Todo to an external
> drive. Now I'm using Linux, I backup data ("Backups") to external USB
> sticks and OS (Timeshift - not strictly a backup) to the internal HD.
> Backing up to an external drive has always been very straightforward,
> but Android seems less accommodating.
> 
> I should say that I have very little need to backup my phone, as I don't
> use it for anything important. If I take any photos I want to keep, I'll
> copy them to my laptop within a day. I also never use Cloud storage.
> 
> My Xiaomi phone has a built-in backup app, but of course that seems to
> require a Xiaomi account with backup to Xiaomi cloud storage. However, a
> little more digging into "Settings" reveals it can store in The Cloud,
> or locally - either as "Mobile Device - Back up and restore items on
> this device", or "Computer - Back up and restore it". However, the
> "Mobile Device" backup says "This feature allows you to backup and
> restore items using your mobile device and computer. This feature needs
> to connect to the internet and requires the following mandatory
> permissions to work:" There follows a list with accessing contacts and
> call history for backing up, and editing contacts and call history to
> restore, accessing storage for backing up files, and saving items to
> storage for restoring items (what these items are it doesn't specify.
> Are they files?). Finally it needs to access messages to back them up
> (but there's nothing about restoring them). Why does it have to do this
> through the internet, though? I have to agree to this before progressing
> to the next info page, but haven't done so, so don't know exactly how
> the computer is involved.
> 
> Looking at other backup apps on Play Store or F-Droid shows how confused
> the picture is. Some backup specifics like apps, contacts, SMS/MMS
> messages, or photos, while others do several. Some state they can't
> backup data as root access is required. Some say they can backup to an
> internal card, and only then copy from that card to an external store.
> 
> Why is backing up in Android apparently so complicated? Why can't I do
> as simply as I would with Windows or Linux via USB (or Wi-Fi)? And I
> haven't even looked at the issue of whether or not it is straightforward
> to restore from a backup.

Very very complicated. Drop your old habits and use Google Cloud.

-- 
Gutta cavat lapidem (Ovid)

[toc] | [prev] | [next] | [standalone]


#109505

FromJeff Layman <Jeff@invalid.invalid>
Date2023-11-03 08:27 +0000
Message-ID<ui2at3$2mqbr$1@dont-email.me>
In reply to#109499
On 03/11/2023 05:38, Jörg Lorenz wrote:
> Am 02.11.23 um 21:23 schrieb Jeff Layman:
>> Any views about backing up an Android phone? When I used Windows, I
>> regularly backed that up with Acronis or EaseUS Todo to an external
>> drive. Now I'm using Linux, I backup data ("Backups") to external USB
>> sticks and OS (Timeshift - not strictly a backup) to the internal HD.
>> Backing up to an external drive has always been very straightforward,
>> but Android seems less accommodating.
>>
>> I should say that I have very little need to backup my phone, as I don't
>> use it for anything important. If I take any photos I want to keep, I'll
>> copy them to my laptop within a day. I also never use Cloud storage.
>>
>> My Xiaomi phone has a built-in backup app, but of course that seems to
>> require a Xiaomi account with backup to Xiaomi cloud storage. However, a
>> little more digging into "Settings" reveals it can store in The Cloud,
>> or locally - either as "Mobile Device - Back up and restore items on
>> this device", or "Computer - Back up and restore it". However, the
>> "Mobile Device" backup says "This feature allows you to backup and
>> restore items using your mobile device and computer. This feature needs
>> to connect to the internet and requires the following mandatory
>> permissions to work:" There follows a list with accessing contacts and
>> call history for backing up, and editing contacts and call history to
>> restore, accessing storage for backing up files, and saving items to
>> storage for restoring items (what these items are it doesn't specify.
>> Are they files?). Finally it needs to access messages to back them up
>> (but there's nothing about restoring them). Why does it have to do this
>> through the internet, though? I have to agree to this before progressing
>> to the next info page, but haven't done so, so don't know exactly how
>> the computer is involved.
>>
>> Looking at other backup apps on Play Store or F-Droid shows how confused
>> the picture is. Some backup specifics like apps, contacts, SMS/MMS
>> messages, or photos, while others do several. Some state they can't
>> backup data as root access is required. Some say they can backup to an
>> internal card, and only then copy from that card to an external store.
>>
>> Why is backing up in Android apparently so complicated? Why can't I do
>> as simply as I would with Windows or Linux via USB (or Wi-Fi)? And I
>> haven't even looked at the issue of whether or not it is straightforward
>> to restore from a backup.
> 
> Very very complicated. Drop your old habits and use Google Cloud.

Nope. Google has enough of my private info without me making it simple 
for them. Do you really believe that Google doesn't scan all the info 
you store on their Cloud servers? From a very recent article at 
<https://www.comparitech.com/blog/information-security/google-drive-secure/#Google_Drive_privacy_issues>:

"Google has, over the years, perfected the art of surveillance 
capitalism—where your data is mined and sold to advertisers, which is 
then used to manipulate or influence your buying behavior."

You might also find it interesting to read the section "Relinquishing 
control".

-- 

Jeff

[toc] | [prev] | [next] | [standalone]


#109507

FromJörg Lorenz <hugybear@gmx.net>
Date2023-11-03 10:13 +0100
Message-ID<ui2dj2$2ndvb$1@dont-email.me>
In reply to#109505
Am 03.11.23 um 09:27 schrieb Jeff Layman:
> On 03/11/2023 05:38, Jörg Lorenz wrote:
>> Very very complicated. Drop your old habits and use Google Cloud.
> 
> Nope. Google has enough of my private info without me making it simple
> for them. Do you really believe that Google doesn't scan all the info
> you store on their Cloud servers? From a very recent article at
> <https://www.comparitech.com/blog/information-security/google-drive-secure/#Google_Drive_privacy_issues>:

Why in the first place did you buy an Android smartphone? Google has 
your data anyway.

> "Google has, over the years, perfected the art of surveillance
> capitalism—where your data is mined and sold to advertisers, which is
> then used to manipulate or influence your buying behavior."
> 
> You might also find it interesting to read the section "Relinquishing
> control".

No. I use my Pixel sometimes but the really important things are done on 
a different OS.

You are obviously lacking a coherent strategy. Conspiracy theories 
really don't help at all.

-- 
Gutta cavat lapidem (Ovid)

[toc] | [prev] | [next] | [standalone]


#109555

FromJeff Layman <Jeff@invalid.invalid>
Date2023-11-04 08:46 +0000
Message-ID<ui50cm$39h0v$1@dont-email.me>
In reply to#109507
On 03/11/2023 09:13, Jörg Lorenz wrote:
> Am 03.11.23 um 09:27 schrieb Jeff Layman:
>> On 03/11/2023 05:38, Jörg Lorenz wrote:
>>> Very very complicated. Drop your old habits and use Google Cloud.
>>
>> Nope. Google has enough of my private info without me making it simple
>> for them. Do you really believe that Google doesn't scan all the info
>> you store on their Cloud servers? From a very recent article at
>> <https://www.comparitech.com/blog/information-security/google-drive-secure/#Google_Drive_privacy_issues>:
> 
> Why in the first place did you buy an Android smartphone? Google has
> your data anyway.

Sadly, you're probably right. I suppose I should be looking at a 
Pinephone or something similar.

It never ceases to amaze me when I look at what my phone's doing that 
it's sending data to someone even when I thought I'd turned it all off. 
I never use Chrome, yet I see it's sending a few kB a day over wi-fi 
(which I have switched off!).

>> "Google has, over the years, perfected the art of surveillance
>> capitalism—where your data is mined and sold to advertisers, which is
>> then used to manipulate or influence your buying behavior."
>>
>> You might also find it interesting to read the section "Relinquishing
>> control".
> 
> No. I use my Pixel sometimes but the really important things are done on
> a different OS.

Well, we have something in common.

> You are obviously lacking a coherent strategy. Conspiracy theories
> really don't help at all.

The first sentence might be correct in relation to Android usage, 
although not using it for anything important is a sensible strategy. I 
doubt, however, that it's a theory any more as to what Google is doing 
with personal data.

-- 

Jeff

[toc] | [prev] | [next] | [standalone]


#109556

FromJörg Lorenz <hugybear@gmx.net>
Date2023-11-04 10:01 +0100
Message-ID<ui5194$3a0ji$1@dont-email.me>
In reply to#109555
On 04.11.23 09:46, Jeff Layman wrote:
> The first sentence might be correct in relation to Android usage,
> although not using it for anything important is a sensible strategy. I
> doubt, however, that it's a theory any more as to what Google is doing
> with personal data.

Perhaps you are right. It worries me to see how most users are naive.
Look at the neighbouring thread "RCS chat".

-- 
Gutta cavat lapidem (Ovid)

[toc] | [prev] | [next] | [standalone]


#109557

FromJeff Layman <Jeff@invalid.invalid>
Date2023-11-04 10:44 +0000
Message-ID<ui57ab$3b24l$1@dont-email.me>
In reply to#109556
On 04/11/2023 09:01, Jörg Lorenz wrote:
> On 04.11.23 09:46, Jeff Layman wrote:
>> The first sentence might be correct in relation to Android usage,
>> although not using it for anything important is a sensible strategy. I
>> doubt, however, that it's a theory any more as to what Google is doing
>> with personal data.
> 
> Perhaps you are right. It worries me to see how most users are naive.
> Look at the neighbouring thread "RCS chat".

Interesting thread. I've just read through it all (because most of my 
messaging is to iPhone users I didn't follow it for long when it first 
appeared).

I do wonder about End-to-End Encryption when the encrypted message goes 
through Google. They could simply be the man-in-the-middle who is able 
to read the message because they set up the encryption. It might also 
answer another question raised as to "what's in RCS for Google?". Well, 
if they are able to read those encrypted messages it's another source of 
data for them to sell that others can't read and make use of.

Or does that sound too much like another conspiracy theory? ;-)

-- 

Jeff

[toc] | [prev] | [next] | [standalone]


#109558

FromJörg Lorenz <hugybear@gmx.net>
Date2023-11-04 11:53 +0100
Message-ID<ui57r7$3atps$1@dont-email.me>
In reply to#109557
Am 04.11.23 um 11:44 schrieb Jeff Layman:
> I do wonder about End-to-End Encryption when the encrypted message goes
> through Google. They could simply be the man-in-the-middle who is able
> to read the message because they set up the encryption. It might also
> answer another question raised as to "what's in RCS for Google?".

Bingo! The world does not need Google as man-in-the-middle.

-- 
Gutta cavat lapidem (Ovid)

[toc] | [prev] | [next] | [standalone]


#109559

FromJörg Lorenz <hugybear@gmx.net>
Date2023-11-04 11:54 +0100
Message-ID<ui57t9$3atps$2@dont-email.me>
In reply to#109557
Am 04.11.23 um 11:44 schrieb Jeff Layman:
> Or does that sound too much like another conspiracy theory? 😉

No, this is the naked truth!

-- 
Gutta cavat lapidem (Ovid)

[toc] | [prev] | [next] | [standalone]


#109567

From"Carlos E. R." <robin_listas@es.invalid>
Date2023-11-04 14:43 +0100
Message-ID<kqn03lFlkl3U1@mid.individual.net>
In reply to#109557
On 2023-11-04 11:44, Jeff Layman wrote:
> On 04/11/2023 09:01, Jörg Lorenz wrote:
>> On 04.11.23 09:46, Jeff Layman wrote:
>>> The first sentence might be correct in relation to Android usage,
>>> although not using it for anything important is a sensible strategy. I
>>> doubt, however, that it's a theory any more as to what Google is doing
>>> with personal data.
>>
>> Perhaps you are right. It worries me to see how most users are naive.
>> Look at the neighbouring thread "RCS chat".
> 
> Interesting thread. I've just read through it all (because most of my 
> messaging is to iPhone users I didn't follow it for long when it first 
> appeared).
> 
> I do wonder about End-to-End Encryption when the encrypted message goes 
> through Google. They could simply be the man-in-the-middle who is able 
> to read the message because they set up the encryption. It might also 
> answer another question raised as to "what's in RCS for Google?". Well, 
> if they are able to read those encrypted messages it's another source of 
> data for them to sell that others can't read and make use of.
> 
> Or does that sound too much like another conspiracy theory? ;-)
> 

Yes.

-- 
Cheers,
        Carlos E.R.

[toc] | [prev] | [next] | [standalone]


#109568

FromJörg Lorenz <hugybear@gmx.net>
Date2023-11-04 16:13 +0100
Message-ID<ui5n2c$3dp78$1@dont-email.me>
In reply to#109567
Am 04.11.23 um 14:43 schrieb Carlos E. R.:
> On 2023-11-04 11:44, Jeff Layman wrote:
>> On 04/11/2023 09:01, Jörg Lorenz wrote:
>>> On 04.11.23 09:46, Jeff Layman wrote:
>>>> The first sentence might be correct in relation to Android usage,
>>>> although not using it for anything important is a sensible strategy. I
>>>> doubt, however, that it's a theory any more as to what Google is doing
>>>> with personal data.
>>>
>>> Perhaps you are right. It worries me to see how most users are naive.
>>> Look at the neighbouring thread "RCS chat".
>>
>> Interesting thread. I've just read through it all (because most of my
>> messaging is to iPhone users I didn't follow it for long when it first
>> appeared).
>>
>> I do wonder about End-to-End Encryption when the encrypted message goes
>> through Google. They could simply be the man-in-the-middle who is able
>> to read the message because they set up the encryption. It might also
>> answer another question raised as to "what's in RCS for Google?". Well,
>> if they are able to read those encrypted messages it's another source of
>> data for them to sell that others can't read and make use of.
>>
>> Or does that sound too much like another conspiracy theory? ;-)
>>
> 
> Yes.

Not at all indeed.

-- 
Gutta cavat lapidem (Ovid)

[toc] | [prev] | [next] | [standalone]


#109602

FromWally J <walterjones@invalid.nospam>
Date2023-11-04 21:30 -0400
Message-ID<ui6r7v$od23$1@paganini.bofh.team>
In reply to#109557
Jeff Layman <Jeff@invalid.invalid> wrote 

> I do wonder about End-to-End Encryption when the encrypted message goes 
> through Google.

Have you looked at PulseSMS' end-to-end encryption instead of Google's?

 *Pulse SMS* (Phone/Tablet/Web)
 free, adfree, reqgsf, 4.7star,78.5K reviews,1M+Downloads
 <https://home.pulsesms.app/overview/>
 <https://play.google.com/store/apps/details?id=xyz.klinker.messenger>

[toc] | [prev] | [next] | [standalone]


#109616

FromTheo <theom+news@chiark.greenend.org.uk>
Date2023-11-05 14:24 +0000
Message-ID<0eo*KLEuz@news.chiark.greenend.org.uk>
In reply to#109557
Jeff Layman <Jeff@invalid.invalid> wrote:
> I do wonder about End-to-End Encryption when the encrypted message goes 
> through Google. They could simply be the man-in-the-middle who is able 
> to read the message because they set up the encryption. It might also 
> answer another question raised as to "what's in RCS for Google?". Well, 
> if they are able to read those encrypted messages it's another source of 
> data for them to sell that others can't read and make use of.
> 
> Or does that sound too much like another conspiracy theory? ;-)

Yes.  E2EE means that Google in the middle can't intercept.  That's what
E2EE means - if they can, it's not E2EE.

However what's in RCS for Google is a competitor to iMessage.  Especially in
the US, Android suffers from 'green bubbles syndrome', where people buy
iPhones because they get better messaging with their iPhone owning mates via
iMessage, and Android owners have to fall back to SMS which is very much a
second class citizen.  RCS is Google's (umpteenth) attempt on an iMessage
rival.

(In the US iMessage has a big chunk of market share, in other countries this
isn't really a thing - everyone uses WhatsApp or Telegram or whatever so the
blue bubbles/green bubbles difference doesn't matter).

If RCS succeeds, it address a key deficiency of Android compared with iOS
and helps them sell more Android phones.

Google is pushing the narrative that RCS is 'open' and iMessage is 'closed',
but, with carriers throwing in the towel and using Google's server, it
sounds like it's not a million miles different from iMessage.

Google are doing this big US ad campaign to 'convince' Apple to add RCS
support to iOS - they know Apple won't, but it just gets Google publicity
for RCS.

Theo

[toc] | [prev] | [next] | [standalone]


#109617

FromLarry Wolff <larrywolff@larrywolff.net>
Date2023-11-06 00:44 +0900
Message-ID<ui8d92$189eq$1@novabbs.org>
In reply to#109616
On 11/5/2023 11:24 PM, Theo wrote:

> Jeff Layman <Jeff@invalid.invalid> wrote:
>> I do wonder about End-to-End Encryption when the encrypted message goes 
>> through Google. They could simply be the man-in-the-middle who is able 
>> to read the message because they set up the encryption. It might also 
>> answer another question raised as to "what's in RCS for Google?". Well, 
>> if they are able to read those encrypted messages it's another source of 
>> data for them to sell that others can't read and make use of.
>> 
>> Or does that sound too much like another conspiracy theory? ;-)
> 
> Yes.  E2EE means that Google in the middle can't intercept.  That's what
> E2EE means - if they can, it's not E2EE.
> 
> However what's in RCS for Google is a competitor to iMessage.  Especially in
> the US, Android suffers from 'green bubbles syndrome', where people buy
> iPhones because they get better messaging with their iPhone owning mates via
> iMessage, and Android owners have to fall back to SMS which is very much a
> second class citizen.  RCS is Google's (umpteenth) attempt on an iMessage
> rival.
> 
> (In the US iMessage has a big chunk of market share, in other countries this
> isn't really a thing - everyone uses WhatsApp or Telegram or whatever so the
> blue bubbles/green bubbles difference doesn't matter).
> 
> If RCS succeeds, it address a key deficiency of Android compared with iOS
> and helps them sell more Android phones.
> 
> Google is pushing the narrative that RCS is 'open' and iMessage is 'closed',
> but, with carriers throwing in the towel and using Google's server, it
> sounds like it's not a million miles different from iMessage.
> 
> Google are doing this big US ad campaign to 'convince' Apple to add RCS
> support to iOS - they know Apple won't, but it just gets Google publicity
> for RCS.
> 
> Theo

Have you read this?
https://www.reuters.com/article/us-apple-fbi-icloud-exclusive-idUSKBN1ZK1CT

It says Apple holds onto your encryption key to read your iMessages while
on iCloud and to give all your iMessages on iCloud to anyone they want to?

[toc] | [prev] | [next] | [standalone]


#109620

FromJörg Lorenz <hugybear@gmx.net>
Date2023-11-05 18:25 +0100
Message-ID<ui8j64$2oem$1@dont-email.me>
In reply to#109617
On 05.11.23 16:44, Larry Wolff wrote:
> Have you read this?
> https://www.reuters.com/article/us-apple-fbi-icloud-exclusive-idUSKBN1ZK1CT
> 
> It says Apple holds onto your encryption key to read your iMessages while
> on iCloud and to give all your iMessages on iCloud to anyone they want to?

*ROTFLSTC*

Very very old news and in the meantime Apple allows E2E-encryption.
You are trying to spread FUD and a lot of nonsense.

-- 
Gutta cavat lapidem (Ovid)

[toc] | [prev] | [next] | [standalone]


#109618

FromJeff Layman <Jeff@invalid.invalid>
Date2023-11-05 15:57 +0000
Message-ID<ui8e1h$21gb$1@dont-email.me>
In reply to#109616
On 05/11/2023 14:24, Theo wrote:
> Jeff Layman <Jeff@invalid.invalid> wrote:
>> I do wonder about End-to-End Encryption when the encrypted message goes
>> through Google. They could simply be the man-in-the-middle who is able
>> to read the message because they set up the encryption. It might also
>> answer another question raised as to "what's in RCS for Google?". Well,
>> if they are able to read those encrypted messages it's another source of
>> data for them to sell that others can't read and make use of.
>>
>> Or does that sound too much like another conspiracy theory? ;-)
> 
> Yes.  E2EE means that Google in the middle can't intercept.  That's what
> E2EE means - if they can, it's not E2EE.

I guess my use of man-in-the-middle was somewhat misleading as it has a 
specific meaning. Perhaps "backdoor" would have been a better choice.

<https://en.wikipedia.org/wiki/End-to-end_encryption#Backdoors>

My point is that Google provide Android. It doesn't matter how open 
source it is as nobody outside Google (and I would think many inside it) 
can know what umpteen million lines of code do. I was referring mainly 
to Google's own backup to their Cloud servers. It may also be the case 
that other manufacturers using their modified Android OS can do the same 
thing. It may be unlikely, but how would anyone outside the company know 
if there was a software backdoor in Android? Backdoors aren't unknown in 
hardware, either. This is from over 10 years ago:
<http://www.cl.cam.ac.uk/~sps32/Silicon_scan_draft.pdf>

Perhaps not relevant so much to Google, but what about Huawei or Xiaomi?

> However what's in RCS for Google is a competitor to iMessage.  Especially in
> the US, Android suffers from 'green bubbles syndrome', where people buy
> iPhones because they get better messaging with their iPhone owning mates via
> iMessage, and Android owners have to fall back to SMS which is very much a
> second class citizen.  RCS is Google's (umpteenth) attempt on an iMessage
> rival.
> 
> (In the US iMessage has a big chunk of market share, in other countries this
> isn't really a thing - everyone uses WhatsApp or Telegram or whatever so the
> blue bubbles/green bubbles difference doesn't matter).
> 
> If RCS succeeds, it address a key deficiency of Android compared with iOS
> and helps them sell more Android phones.
> 
> Google is pushing the narrative that RCS is 'open' and iMessage is 'closed',
> but, with carriers throwing in the towel and using Google's server, it
> sounds like it's not a million miles different from iMessage.
> 
> Google are doing this big US ad campaign to 'convince' Apple to add RCS
> support to iOS - they know Apple won't, but it just gets Google publicity
> for RCS.

I assume that if Google gets their success with RCS that would mean more 
data available for analysis by them, and more ads for us.

-- 

Jeff

[toc] | [prev] | [next] | [standalone]


Page 1 of 6  [1] 2 3 4 5 6  Next page →

Back to top | Article view | comp.mobile.android


csiph-web