Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.mobile.android > #59501
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Newsgroups | comp.mobile.android |
| Subject | Re: Speaking alarm clock |
| Date | 2019-01-31 12:03 +0100 |
| Message-ID | <k81bif-arn.ln1@Telcontar.valinor> (permalink) |
| References | <cu4aif-ot4.ln1@Telcontar.valinor> <q2u0nj$mlj$1@news.albasani.net> <q2uii4$sas$1@gioia.aioe.org> <q2uk2l$1mo$1@dont-email.me> |
On 31/01/2019 11.53, David Taylor wrote: > On 31/01/2019 10:27, Piet wrote: >> M. L. wrote: >>> Talking Alarm Clock by Mirolunapp allows the option of playing >>> a typed message either before or after the time is announced. >>> https://bit.ly/2sVku1E >> >> Looks interesting, but why does it need all those permissions? >> >> -p > > Had a program update recently that required "Make and receiver phone > calls" (or words to that effect). Turns out that under Android 9 they > need that permission to read the hardware signature of the phone. > > Yes, this app is hardware locked, making more work for both the > developer and the end-user when they change their phone. I don't know > why they can't just use the PlayStore.... > Hardware locked? I don't understand. -- Cheers, Carlos.
Back to comp.mobile.android | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Speaking alarm clock "Carlos E.R." <robin_listas@es.invalid> - 2019-01-31 03:59 +0100
Re: Speaking alarm clock Boris <nospam@nospam.invalid> - 2019-01-31 04:03 +0000
Re: Speaking alarm clock "M. L." <me@privacy.invalid> - 2019-01-30 23:22 -0600
Re: Speaking alarm clock Piet <www.godfatherof.nl/@opt-in.invalid> - 2019-01-31 11:27 +0100
Re: Speaking alarm clock "Carlos E.R." <robin_listas@es.invalid> - 2019-01-31 11:31 +0100
Re: Speaking alarm clock David Taylor <david-taylor@blueyonder.co.uk.invalid> - 2019-01-31 10:53 +0000
Re: Speaking alarm clock "Carlos E.R." <robin_listas@es.invalid> - 2019-01-31 12:03 +0100
Re: Speaking alarm clock arlen holder <arlen@arlen.com> - 2019-02-01 01:52 +0000
Re: Speaking alarm clock "Carlos E.R." <robin_listas@es.invalid> - 2019-02-01 03:10 +0100
Re: Speaking alarm clock arlen holder <arlen@arlen.com> - 2019-02-01 03:02 +0000
Re: Speaking alarm clock "Carlos E.R." <robin_listas@es.invalid> - 2019-02-01 14:09 +0100
Re: Speaking alarm clock micky <NONONOmisc07@bigfoot.com> - 2019-02-01 09:26 -0500
Re: Speaking alarm clock "Carlos E.R." <robin_listas@es.invalid> - 2019-02-01 18:43 +0100
Re: Speaking alarm clock FMurtz <haggisz@hotmail.com> - 2019-02-03 19:34 +1100
Re: Speaking alarm clock arlen holder <arlen@arlen.com> - 2019-02-03 15:16 +0000
Re: Speaking alarm clock "Carlos E.R." <robin_listas@es.invalid> - 2019-01-31 11:28 +0100
Re: Speaking alarm clock micky <NONONOmisc07@bigfoot.com> - 2019-01-31 09:34 -0500
Re: Speaking alarm clock Joe Beanfish <joebeanfish@nospam.duh> - 2019-01-31 14:17 +0000
Re: Speaking alarm clock "Carlos E.R." <robin_listas@es.invalid> - 2019-01-31 18:27 +0100
Re: Speaking alarm clock micky <NONONOmisc07@bigfoot.com> - 2019-01-31 20:24 -0500
Re: Speaking alarm clock "Carlos E.R." <robin_listas@es.invalid> - 2019-02-01 03:13 +0100
Re: Speaking alarm clock micky <NONONOmisc07@bigfoot.com> - 2019-02-01 07:43 -0500
Re: Speaking alarm clock Frank Slootweg <this@ddress.is.invalid> - 2019-02-01 21:09 +0000
Re: Speaking alarm clock "Carlos E.R." <robin_listas@es.invalid> - 2019-02-02 03:20 +0100
Re: Speaking alarm clock micky <NONONOmisc07@bigfoot.com> - 2019-01-31 20:25 -0500
Re: Speaking alarm clock Joe Beanfish <joebeanfish@nospam.duh> - 2019-02-01 14:14 +0000
Re: Speaking alarm clock "Carlos E.R." <robin_listas@es.invalid> - 2019-02-01 18:42 +0100
Re: Speaking alarm clock Joe Beanfish <joebeanfish@nospam.duh> - 2019-02-04 14:15 +0000
Re: Speaking alarm clock "Carlos E.R." <robin_listas@es.invalid> - 2019-02-04 16:05 +0100
Re: Speaking alarm clock Joe Beanfish <joebeanfish@nospam.duh> - 2019-02-05 15:31 +0000
Re: Speaking alarm clock "M. L." <me@privacy.invalid> - 2019-02-06 11:10 -0600
Re: Speaking alarm clock Joe Beanfish <joebeanfish@nospam.duh> - 2019-02-07 14:23 +0000
Re: Speaking alarm clock "M. L." <me@privacy.invalid> - 2019-02-08 21:08 -0600
Re: Speaking alarm clock Joe Beanfish <joebeanfish@nospam.duh> - 2019-02-12 15:34 +0000
Re: Speaking alarm clock micky <NONONOmisc07@bigfoot.com> - 2019-01-31 09:26 -0500
Re: Speaking alarm clock Chris in Makati <mail@nospam.com> - 2019-01-31 15:48 +0000
Re: Speaking alarm clock "Carlos E.R." <robin_listas@es.invalid> - 2019-01-31 18:39 +0100
Re: Speaking alarm clock "Carlos E.R." <robin_listas@es.invalid> - 2019-01-31 20:43 +0100
Re: Speaking alarm clock arlen holder <arlen@arlen.com> - 2019-02-01 03:47 +0000
Re: Speaking alarm clock arlen holder <arlen@arlen.com> - 2019-02-01 04:48 +0000
Re: Speaking alarm clock "Carlos E.R." <robin_listas@es.invalid> - 2019-02-01 14:03 +0100
Re: Speaking alarm clock arlen holder <arlen@arlen.com> - 2019-02-02 20:02 +0000
csiph-web