Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.mobile.android > #37057
| From | Daniel James <daniel@me.invalid> |
|---|---|
| Newsgroups | comp.mobile.android |
| Subject | Re: Android 6 |
| Date | 2016-12-30 15:34 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <VA.00000c21.0051986f@me.invalid> (permalink) |
| References | (2 earlier) <GF5$UjdX6GXYFwDO@end.of.the.universe> <221220161930042824%nospam@nospam.invalid> <N9L96fgduRXYFwwR@end.of.the.universe> <1qfns956w49cz.1e2eg8f0ti0g$.dlg@40tude.net> <449f715e-6c60-7051-98a5-bed4624d9a68@arnowelzel.de> |
In article <449f715e-6c60-7051-98a5-bed4624d9a68@arnowelzel.de>, Arno Welzel wrote: > Pictures taken by a camera app are not the same as *private* data > of an app which is usually stored in SQlite databases (like the > contacts database). That's largely true ... but it is up to the programmer to decide what data an app uses should be "private" and what should be generally accessible. Even then, Android doesn't make the creation of generally accessible data areas easy -- the camera app is a special case. There's nothing special about SQLite databases. They're just files. The issue is whether the programmer has chosen to make the app write data to the SD card, and whether the app has the necessary permission to do so. Android apps are not supposed to write to any area of external storage apart from their own app directory. Before Android 4.4 "KitKat" that rule was not enforced. In KitKat it was enforced for the first time, which caused a lot of annoyance as many developers had not understood the requirements correctly, or had assumed that the rule would never be enforced. In Lollipop a new permission was added whereby an app could request permission to write outside its own directory (essential for file managers, and the like). In Marshmallow Google have changed the rules by making the user choose whether SD cards should be "internal" or "portable" storage. The old rules apply to "portable" storage, but (I think, I'm still learning about this) Android will no longer automatically move apps and their data to the card in that mode. -- Cheers, Daniel.
Back to comp.mobile.android | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Android 6 Bill <Billaboard@gmail.com> - 2016-12-22 17:21 +0000
Re: Android 6 The Real Bev <bashley101@gmail.com> - 2016-12-22 10:00 -0800
Re: Android 6 Bill <Billaboard@gmail.com> - 2016-12-23 00:23 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-22 19:30 -0500
Re: Android 6 Bill <Billaboard@gmail.com> - 2016-12-23 12:42 +0000
Re: Android 6 tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2016-12-23 11:58 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-29 13:43 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2016-12-30 15:34 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-30 22:33 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2016-12-31 13:27 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-04 08:59 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-04 13:40 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-11 09:00 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-15 18:23 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-15 21:20 +0100
Re: Android 6 AL <45364747@invalid.com> - 2017-01-04 10:06 -0700
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-11 09:00 +0100
Re: Android 6 tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2017-01-05 01:34 -0500
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-07 14:14 +0000
Re: Android 6 tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2017-01-07 13:09 -0500
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-08 18:18 +0000
Re: Android 6 tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2017-01-08 15:42 -0500
Re: Android 6 The Real Bev <bashley101@gmail.com> - 2017-01-08 17:11 -0800
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-08 20:19 -0500
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-09 23:55 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-11 18:07 +0100
Re: Android 6 Frank Slootweg <this@ddress.is.invalid> - 2017-01-08 21:34 +0000
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-09 23:55 +0000
Re: Android 6 Joerg Lorenz <hugybear@gmx.ch> - 2016-12-24 10:49 +0100
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-22 23:55 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-22 19:15 -0500
Re: Android 6 Joerg Lorenz <hugybear@gmx.ch> - 2016-12-23 05:46 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-23 00:15 -0500
Re: Android 6 Dave Higton <dave@davehigton.me.uk> - 2016-12-23 17:11 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-23 12:43 -0500
Re: Android 6 Dave Higton <dave@davehigton.me.uk> - 2016-12-23 21:22 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-24 14:29 -0500
Re: Android 6 Dave Higton <dave@davehigton.me.uk> - 2016-12-25 11:10 +0000
Re: Android 6 Piet <www.godfatherof.nl/@opt-in.invalid> - 2016-12-25 12:37 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-25 11:18 -0500
Re: Android 6 Dave Higton <dave@davehigton.me.uk> - 2016-12-25 20:28 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-29 12:02 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-29 23:45 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-29 18:02 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-30 22:24 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-31 11:55 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-04 09:04 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-04 10:14 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-11 18:11 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-11 13:05 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-13 17:23 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-16 15:35 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-17 05:39 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2016-12-30 15:34 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-30 22:26 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2016-12-31 13:27 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-31 11:55 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-04 09:11 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-04 13:40 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-04 10:14 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-11 18:12 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-11 13:05 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-13 17:24 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-15 18:23 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-15 21:30 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-16 15:42 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-16 15:35 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-17 05:44 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-17 17:47 +0000
Re: Android 6 Bill <Billaboard@gmail.com> - 2017-01-01 01:05 +0000
Re: Android 6 tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2017-01-02 02:08 -0500
Re: Android 6 David Taylor <david-taylor@blueyonder.co.uk.invalid> - 2017-01-02 08:01 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-02 08:51 -0500
Re: Android 6 Bill <Billaboard@gmail.com> - 2017-01-02 20:41 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-04 09:18 +0100
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-04 09:14 +0100
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-29 14:05 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-29 12:02 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-29 23:46 +0100
Re: Android 6 Dave Higton <dave@davehigton.me.uk> - 2016-12-31 20:18 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-29 13:47 +0100
csiph-web