John B. Slocomb <
sloc...@invalid.com> wrote:
[...]
> If anyone can move an App to the external sd card please advise the
> manufacturer of the device, the Android version, and how you
> determined that the App was actually moved to the external, user
> installed, memory, and to what directory on the external memory the
> app was moved to.
>
> This , by the way, is not intended as a challenge. I would really like
> to know what is actually possible on these confounded devices.
As I've mentioned several times before, my Huawei (Ascend Y300) with
(stock) Android 4.1.1 can do this, provided of course that the app is
written to be able to do this.
The most convincing proof that (the biggest part of) the app is
actually moved to the 'external' SD-card, is that the moved parts are in
the .android_secure folder on the 'external' SD-card. These moved parts
are the .asec files of the apps.
Note that the *content* of this folder is *not* shown by the file
manager (at least not the supplied file manager (called 'File
Manager')). The folder itself is shown, but says '[Files:0, Folders:0]'.
To be able to see the contents of the folder, I had to connect the
phone to my laptop in 'Connect as USB mass storage' mode. (In MTP mode,
the folder is shown, but not its contents.) (Of course one could also
take the SD-card out of the phone and insert it in a card-reader of a
computer, but that's quite a hassle and not needed.)
When connected to the laptop, it's very clear as to which folder/file
is in which storage area ('Internal storage' or ('external') 'SD card'),
because these areas have different drive letters. I.e. while there might
be confusion when looking at these areas from the Android side, there is
no such confusion when looking at them from the laptop/Windows side.
But even stronger than that, I know for sure that the files are on the
SD-card, because at one time I changed from a 8GB card to a 32GB and
when copying everything, the contents of the .android_secure folder were
copied from the old to the new card.
A specfic example (of one of my about ten moved apps):
- "GPS Navigation BE-ON-ROAD"
<
https://play.google.com/store/apps/details?id=cz.aponia.bor3>
- The .asec file is cz.aponia.bor3-2.asec. That's similar for other
.asec files: the Google play 'id', followed by a minus sign, followed
by a digit and followed by '.asec'.
- The cz.aponia.bor3-2.asec file is 21,862 KB, 21.3 MB.
- On the Android side, the 'App info' page says:
"Storage
Total 25.16MB
App 3.04MB
USB storage app 21.38MB
Data 756KB
SD card 0.00B"
- 'App' is the *un*-moved part, which is in the 'Internal storage',
i.e. the internal memory of the phone. I.e. very little in the
'precious' storage area.
- 'USB storage app' is the part of the *app*, which is moved to the
'external' SD-card. It matches quite closely with the size of the
.asec file. I.e. most of the app has been moved to the 'external'
SD-card.
- 'Data' is the data area in 'Internal storage'.
- 'SD card' is the *data* area on the 'external' SD-card.
N.B. For *this* (kind of) app - an offline GPS navigation app - the
sizes of 'Data' and 'SD card' data are not very relevant, because the
bulk of the data - hundreds of megabytes and sometimes even gigabytes
of offline maps - is in normal files on the 'external' SD-card. For
example for another navigation app - Navfree - the 'SD card' data area
is 572MB, so for that app, the big maps are not in normal files.
I hope this helps. Please feel free to ask any questions.