Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.mobile.android > #59375
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Newsgroups | comp.mobile.android |
| Subject | Re: Call Recording |
| Date | 2019-01-27 14:36 +0100 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <9no0if-jcf.ln1@Telcontar.valinor> (permalink) |
| References | <6Y13E.178018$pE1.105319@fx38.am4> <q2jj3q$5ei$1@dont-email.me> <1cpvz6tqrx1x2.dlg@v.nguard.lh> |
On 27/01/2019 08.31, VanguardLH wrote: ... Re legality. Here sometimes companies call us and say they are going to record the call for legal reasons, for contracting some service, say. If they are recording, so we can. > That apps can no longer record incoming calls has nothing to do with > legality. It all has to do with Google deciding to remove some or all > of an API that the apps used to record the calls (instead of the apps > using their own code which may require rooting the phone). > > https://developer.android.com/guide/topics/media/mediarecorder > > RECORD_AUDIO is considered a "dangerous" permission because it may > pose a risk to the user's privacy. > > As of Android 6, users got prompted when an app wanted access to a > dangerous permission, and at some point Google decided to prompt the > user on all of what permissions an app can have. This didn't meant > users were instantly and magically educated about the permissions but > they were told an app wanted one, or more. An app, for example, could > run in the background and record all your calls, not just the calls you > chose to record, and even send the recordings to somewhere. > > Google did NOT disable the ability of apps to record a call in Android 9 > Pie. What they did was change the API so *background* apps could no > longer keep recording the incoming calls. The user now has to take > overt action to record a call and that meant the app must be > foregrounded. Ah? > > (from the above article) > Note: On devices running Android 9 (API level 28) or higher, apps > running in the background cannot access the microphone. Therefore, > your app should record audio only when it's in the foreground or when > you include an instance of MediaRecorder in a foreground service. What about the microphone apps, to record a speech, say? Here some people use it, covertly, to record what the boss says and have proof (example). > That means your recording app must be foregrounded for it to record the > call, not hiding as either a backgrounded app or running as a service. > The recording app must now change from a hidden and automatic recording > app to itself being a dialer that you use to make the outgoing call or > as a substitute "phone" app that appears for you to accept an incoming > call. There might be other means of getting the app to appear and in > the foreground when a new call comes in but the obvious one is to use a > Phone app to take the incoming calls and which adds a recording option. Looks good to me. > Recording apps that only record are going to get killed. Those single- > purpose backgrounded apps that only record a call won't work, anymore. > However, as a phone app that has you decided to take the call and is > foregrounded then those can still record your calls. Or you root your > phone to get around the limitation. -- Cheers, Carlos.
Back to comp.mobile.android | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Call Recording Ian <ian@privacy.net> - 2019-01-26 18:48 +0000
Re: Call Recording arlen holder <arlen@arlen.com> - 2019-01-26 20:48 +0000
Re: Call Recording Boris <nospam@nospam.invalid> - 2019-01-26 21:12 +0000
Re: Call Recording arlen holder <arlen@arlen.com> - 2019-01-26 22:17 +0000
Re: Call Recording Joerg Lorenz <hugybear@gmx.ch> - 2019-01-27 07:29 +0100
Re: Call Recording VanguardLH <V@nguard.LH> - 2019-01-27 01:31 -0600
Re: Call Recording Joerg Lorenz <hugybear@gmx.ch> - 2019-01-27 11:13 +0100
Re: Call Recording Chris in Makati <mail@nospam.com> - 2019-01-27 15:04 +0000
Re: Call Recording 123456789 <123456@123456.com> - 2019-01-27 09:09 -0700
Re: Call Recording arlen holder <arlen@arlen.com> - 2019-01-28 01:49 +0000
Re: Call Recording arlen holder <arlen@arlen.com> - 2019-01-28 01:49 +0000
Re: Call Recording Joerg Lorenz <hugybear@gmx.ch> - 2019-01-27 11:16 +0100
Re: Call Recording VanguardLH <V@nguard.LH> - 2019-01-27 20:03 -0600
Re: Call Recording "Carlos E.R." <robin_listas@es.invalid> - 2019-01-28 03:54 +0100
Re: Call Recording arlen holder <arlen@arlen.com> - 2019-01-28 03:53 +0000
Re: Call Recording "Carlos E.R." <robin_listas@es.invalid> - 2019-01-27 14:36 +0100
Re: Call Recording Piet <www.godfatherof.nl/@opt-in.invalid> - 2019-01-30 21:32 +0100
Re: Call Recording nospam <nospam@nospam.invalid> - 2019-01-27 14:16 -0500
Re: Call Recording John McGaw <Nobody@Nowh.ere> - 2019-01-27 11:11 -0500
Re: Call Recording "s|b" <me@privacy.invalid> - 2019-01-27 17:49 +0100
Re: Call Recording "s|b" <me@privacy.invalid> - 2019-01-27 17:58 +0100
Re: Call Recording Joerg Lorenz <hugybear@gmx.ch> - 2019-01-27 21:39 +0100
Re: Call Recording "s|b" <me@privacy.invalid> - 2019-01-27 23:00 +0100
Re: Call Recording Joerg Lorenz <hugybear@gmx.ch> - 2019-01-27 21:32 +0100
Re: Call Recording arlen holder <arlen@arlen.com> - 2019-01-28 01:48 +0000
Re: Call Recording arlen holder <arlen@arlen.com> - 2019-01-28 01:49 +0000
csiph-web