Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.mobile.android > #59490 > unrolled thread

Speaking alarm clock

Back to article view | Back to comp.mobile.android

Contents

  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

Page 1 of 3  [1] 2 3  Next page →

#59490 — Speaking alarm clock

Hi,


I had a look but I did not find what I'm seeking for.

I just would like an alarm clock app that besides playing some tune as
typical, also speaks up the current time. No telling the weather, the
news, phrases, etc: just the hour.

I have seen some that will not shut up till you solve a puzzle or a math
equation. Wow. The think would accidentally fall into a pail of water or
under a hammer something.

No, I just want it to politely tell me the hour, maybe when touching it,
and shut up.

Or an app that speaks a phrase at some defined time and shuts up...

-- 
Cheers, Carlos.

[toc] | [next] | [standalone]

#59491

"Carlos E.R." <robin_listas@es.invalid> wrote in news:cu4aif-ot4.ln1
@Telcontar.valinor:

> Hi,
> 
> 
> I had a look but I did not find what I'm seeking for.
> 
> I just would like an alarm clock app that besides playing some tune as
> typical, also speaks up the current time. No telling the weather, the
> news, phrases, etc: just the hour.
> 
> I have seen some that will not shut up till you solve a puzzle or a math
> equation. Wow. The think would accidentally fall into a pail of water or
> under a hammer something.
> 
> No, I just want it to politely tell me the hour, maybe when touching it,
> and shut up.

Your wife?

> 
> Or an app that speaks a phrase at some defined time and shuts up...
> 

[toc] | [prev] | [next] | [standalone]

#59493

> I just would like an alarm clock app that besides playing some tune as
> typical, also speaks up the current time. No telling the weather, the
> news, phrases, etc: just the hour.
> 
> I have seen some that will not shut up till you solve a puzzle or a math
> equation. Wow. The think would accidentally fall into a pail of water or
> under a hammer something.
> 
> No, I just want it to politely tell me the hour, maybe when touching it,
> and shut up.
> 
> Or an app that speaks a phrase at some defined time and shuts up...

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

[toc] | [prev] | [next] | [standalone]

#59496

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

[toc] | [prev] | [next] | [standalone]

#59498

On 31/01/2019 11.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?

It wants contacts? Identity?

-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]

#59500

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....

-- 
Cheers,
David
Web: http://www.satsignal.eu

[toc] | [prev] | [next] | [standalone]

#59501

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.

[toc] | [prev] | [next] | [standalone]

#59518

On Thu, 31 Jan 2019 11:27:20 +0100, Piet wrote:

> Looks interesting, but why does it need all those permissions?

I tried to install it just now...
o Talking Alarm Clock, by Mirolunapp
<https://play.google.com/store/apps/details?id=com.rosamaria.svegliaparlante>

It instantly asks for your "identity", "media", "microphone", "device id",
& "call information".

I didn't get past that as I agree with you that it's too much to ask for.

HOWEVER ... 

There are some apps that ask _before_ you install (like this one did), 
and there are some apps that ask _after_ you install.

What's the difference?

Nonetheless, the very _next_ "talking alarm clock" on the GP list was
o Speaking Alarm Clock, by Wansoft
<https://play.google.com/store/apps/details?id=wan.pclock>

I hit the "install" button, and it didn't ask for _anything_.
Then, after installing, I hit the "open" button...
And it _still_ didn't ask for anything.

I hit the "hourly interval" button.
Then the "hourly chime settings".
Then the "Type of alarm" was set by default to "Say time using TTS".

There are a ton of settings, so, I'll find out _what_ it does, over time.

[toc] | [prev] | [next] | [standalone]

#59519

On 01/02/2019 02.52, arlen holder wrote:

...

> HOWEVER ... 
> 
> There are some apps that ask _before_ you install (like this one did), 
> and there are some apps that ask _after_ you install.
> 
> What's the difference?

The Android version for which it was designed.

> 
> Nonetheless, the very _next_ "talking alarm clock" on the GP list was
> o Speaking Alarm Clock, by Wansoft

See my other post. That's the one I installed.

-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]

#59521

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).

o Speaking Alarm Clock, by Wansoft
<https://play.google.com/store/apps/details?id=wan.pclock>

[toc] | [prev] | [next] | [standalone]

#59530

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.

[toc] | [prev] | [next] | [standalone]

#59532

In comp.mobile.android, on Fri, 1 Feb 2019 14:09:44 +0100, "Carlos E.R."
<robin_listas@es.invalid> wrote:

>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.

You should send your criticism to the author.  I've done that with
success one time, with out a reply the other.  But one out of two is not
bad. 

[toc] | [prev] | [next] | [standalone]

#59538

On 01/02/2019 15.26, micky wrote:
> In comp.mobile.android, on Fri, 1 Feb 2019 14:09:44 +0100, "Carlos E.R."
> <robin_listas@es.invalid> wrote:
> 
>> 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.
> 
> You should send your criticism to the author.  I've done that with
> success one time, with out a reply the other.  But one out of two is not
> bad. 

Maybe I will :-)


-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]

#59576

arlen holder wrote:
> On Thu, 31 Jan 2019 11:27:20 +0100, Piet wrote:
> 
>> Looks interesting, but why does it need all those permissions?
> 
> I tried to install it just now...
> o Talking Alarm Clock, by Mirolunapp
> <https://play.google.com/store/apps/details?id=com.rosamaria.svegliaparlante>
> 
> It instantly asks for your "identity", "media", "microphone", "device id",
> & "call information".
> 
> I didn't get past that as I agree with you that it's too much to ask for.
> 
> HOWEVER ...
> 
> There are some apps that ask _before_ you install (like this one did),
> and there are some apps that ask _after_ you install.
> 
> What's the difference?
> 
> Nonetheless, the very _next_ "talking alarm clock" on the GP list was
> o Speaking Alarm Clock, by Wansoft
> <https://play.google.com/store/apps/details?id=wan.pclock>
> 
> I hit the "install" button, and it didn't ask for _anything_.
> Then, after installing, I hit the "open" button...
> And it _still_ didn't ask for anything.

Because they already know all your info and has permission to do almost 
anything?

> 
> I hit the "hourly interval" button.
> Then the "hourly chime settings".
> Then the "Type of alarm" was set by default to "Say time using TTS".
> 
> There are a ton of settings, so, I'll find out _what_ it does, over time.
> 
Because they already know all your info and has permission to do almost 
anything?

[toc] | [prev] | [next] | [standalone]

#59577

On Sun, 3 Feb 2019 19:34:34 +1100, FMurtz wrote:

> Because they already know all your info and has permission to do almost 
> anything?

Hi FMurtz,
Are you _sure_ that answer you gave has _any_ facts behind it?

While the _vast_ majority of my apps don't ask for _any_ permissions, 
o Some apps ask for permission up front, while
o Other apps ask for permission only upon first execution.

The suggestion from (I think it was Carlos?) that the difference is due to
o Some apps user an "older" permission-request method, while
o Other apps use the "newer" permission-request style
seems to make more sense than your suggestion FMurtz.

It is a valid question, outside of "speaking alarm clocks", though, 
of _what_ an app _inherently_ knows about us.

I'll post a separate thread on that topic alone as it's off topic here.

[toc] | [prev] | [next] | [standalone]

#59497

On 31/01/2019 06.22, M. L. wrote:
> 
> 
>> I just would like an alarm clock app that besides playing some tune as
>> typical, also speaks up the current time. No telling the weather, the
>> news, phrases, etc: just the hour.
>>
>> I have seen some that will not shut up till you solve a puzzle or a math
>> equation. Wow. The think would accidentally fall into a pail of water or
>> under a hammer something.
>>
>> No, I just want it to politely tell me the hour, maybe when touching it,
>> and shut up.
>>
>> Or an app that speaks a phrase at some defined time and shuts up...
> 
> 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


Seems to be what I want, but all the recent reports say it went berseck.


-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]

#59505

In comp.mobile.android, on Thu, 31 Jan 2019 11:28:24 +0100, "Carlos
E.R." <robin_listas@es.invalid> wrote:

>On 31/01/2019 06.22, M. L. wrote:
>> 
>> 
>>> I just would like an alarm clock app that besides playing some tune as
>>> typical, also speaks up the current time. No telling the weather, the
>>> news, phrases, etc: just the hour.
>>>
>>> I have seen some that will not shut up till you solve a puzzle or a math
>>> equation. Wow. The think would accidentally fall into a pail of water or
>>> under a hammer something.
>>>
>>> No, I just want it to politely tell me the hour, maybe when touching it,
>>> and shut up.
>>>
>>> Or an app that speaks a phrase at some defined time and shuts up...
>> 
>> 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
>
>
>Seems to be what I want, but all the recent reports say it went berseck.

Yes, and it hasn't been updated since any of those reports. 

[toc] | [prev] | [next] | [standalone]

#59503

On Thu, 31 Jan 2019 03:59:56 +0100, Carlos E.R. wrote:
> I just would like an alarm clock app that besides playing some tune as
> typical, also speaks up the current time. No telling the weather, the
> news, phrases, etc: just the hour.

I recall seeing a couple that did that when looking for a new alarm clock,
but iirc, they all did all the extra stuff you don't want too.

I'm genuinely curious about that option tho, not trying to be a snot...
Why do you want the time spoken? For me, the alarm going off means it's the
chosen time. Maybe I'm missing something in your, and others', use case?

[toc] | [prev] | [next] | [standalone]

#59509

On 31/01/2019 15.17, Joe Beanfish wrote:
> On Thu, 31 Jan 2019 03:59:56 +0100, Carlos E.R. wrote:
>> I just would like an alarm clock app that besides playing some tune as
>> typical, also speaks up the current time. No telling the weather, the
>> news, phrases, etc: just the hour.
> 
> I recall seeing a couple that did that when looking for a new alarm clock,
> but iirc, they all did all the extra stuff you don't want too.
> 
> I'm genuinely curious about that option tho, not trying to be a snot...
> Why do you want the time spoken? For me, the alarm going off means it's the
> chosen time. Maybe I'm missing something in your, and others', use case?

The use case is that I snooze. I say "let's sleep some more, I'm too
tired". I may forget that, despite having slept only 5 hours I must get
up to do something important at a certain time, and that snoozing 4
times is too much.

So, tell my sleepy mind the time so it realizes :-)

Some people use difficult to switch off alarms. Or very loud. Those
instead turn me angry. Or alarmed.

So I use one that starts very softly and which doesn't wake me instantly
with a jolt.  But at that moment my neurons are not working right and
have a mind of their own to continue sleeping. They need to be reminded
why they must give up.


I have seen other tools that are not alarm clocks, but reminders. There
may be hundreds of alarm clock apps!


-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]

#59516

In comp.mobile.android, on Thu, 31 Jan 2019 18:27:27 +0100, "Carlos
E.R." <robin_listas@es.invalid> wrote:

>
>I have seen other tools that are not alarm clocks, but reminders. There
>may be hundreds of alarm clock apps!

My second year in college I had a clock radio I used to turn on a
floodlight that shone right on me.  

It made me get up iirc but it didn't make me get good grades. 

[toc] | [prev] | [next] | [standalone]

Page 1 of 3  [1] 2 3  Next page →

Back to top | Article view | comp.mobile.android

csiph-web