Feedback on text to speech feature

[mikeone]

The bottom line is: there is still place for manual operations, but having them automated on a regular basis is nice.

Yes, I completely agree with your arguments.
I would also prefer a solution that is as automatic as possible.
 

[mikeone]

+1

And: put TTS off when the user is calling (using phone/whatsapp voice). That's why I'm not using TTS AquaMail.

+1

I experienced a few times, that TTS suddenly rattled in a phone call... very annoying, since it tooks me some time to go through the phone to find that widget:

-> "shake to stop TTS immediately" I have missed every time:
https://www.aqua-mail.com/forum/index.php?topic=5776.msg35148#msg35148

[mikeone]

...
You cannot shake your phone while driving/biking (forbidden in France). The need is:
- an option to enable automatically TTS when Bluetooth is activated
- stop Aqua TTS when the phone (voice) is used

My experience was during a 'normal' call - just helding the phone in my hand - without headphones, not driving/biking.
-> In this situation "shake to stop TTS immediately" would be much more convenient than searching the widget 

[Kostya Vasilyev]

Re: put TTS off when the user is calling (using phone/whatsapp voice).

A mobile network call could in principle be detected (let's set aside permissions for a moment).

But detecting WhatsApp voice / Skype / VoIP ?

[StR]

Re: put TTS off when the user is calling (using phone/whatsapp voice).

A mobile network call could in principle be detected (let's set aside permissions for a moment).

But detecting WhatsApp voice / Skype / VoIP ?

That is a valid concern, and one can extend that line of thinking to other sources (what if you are recording an audio with one of many apps, etc.).
You are right, it is probably impossible to cover all interference situations.
But the phone call is the most obvious, and still most likely to happen (most frequent). Taking care of that would probably cover at least 80-90% of cases. And that is significant enough to justify doing that.

As my mentor once told me: "You cannot collect all marbles, you just do your best."

[Kostya Vasilyev]

Re: But the phone call is the most obvious, and still most likely to happen (most frequent). Taking care of that would probably cover at least 80-90% of cases.

Yes, right. We'll try to add this, not sure how it'll work out technically but we'll try.

( detecting "in call" state needs a permission that the app doesn't have right now )

[StR]

( detecting "in call" state needs a permission that the app doesn't have right now )

I am always very alert when any new or updated app is trying to grab extra permissions. So, I understand and appreciate your concern about adding permissions. And indeed, in this case (if I understand correctly), - the permission would be "phone status and identity", where the second part is a bit scary for the user.

Just a thought, - if and when you'd be adding this permission, maybe you can add the permission for BT status recognition, - to minimize episodes of added permissions...

[Kostya Vasilyev]

Re: So, I understand and appreciate your concern about adding permissions.

Yes, pretty scary and the permission lets apps do much more than detect in-call state - like reading the IMEI (if my memory serves). Unfortunately there is no finer-grained permission.