Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.mobile.android > #59530
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Newsgroups | comp.mobile.android |
| Subject | Re: Speaking alarm clock |
| Date | 2019-02-01 14:09 +0100 |
| Message-ID | <o1tdif-k0v.ln1@Telcontar.valinor> (permalink) |
| References | <cu4aif-ot4.ln1@Telcontar.valinor> <q2u0nj$mlj$1@news.albasani.net> <q2uii4$sas$1@gioia.aioe.org> <q308o3$pke$1@news.mixmin.net> <q30cs8$13n$1@news.mixmin.net> |
On 01/02/2019 04.02, arlen holder wrote: > On Fri, 1 Feb 2019 01:52:04 -0000 (UTC), arlen holder wrote: > >> There are a ton of settings, so, I'll find out _what_ it does, over time. > > The good news is that, at 6pm, it announced, verbally, "six pm", and then, > at 7pm, it annunced "seven pm". > > Unless there's a reason to not like this one, I think it may fit the OP's > request for a clocks that says the time on the hour, every hour (it's > settable by day of week or whatever). No, I already said why not: it speaks the time before the music. It speaks the hour at a loud volume, then starts the music at a very low volume. No, I want the speech after the music. Maybe 10 seconds after, or maybe after pressing the button. Also, adding a text to be read disables speaking the time. Why not both? Then the buttons to snooze or stop are too close one to other and in the same colour. I have to wake up a bit and read them! I may press stop instead of snooze by mistake, then go back to sleep "knowing" that it will ring again, but it doesn't. -- 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