[Android Apps and Games] brandall:
Thanks for sharing :good:

It depends on the location settings on the device (if it has a cellular connection etc) as to how often and how accurate the location data will be. There are always boxes to tick in the Android Settings where you can disable and enable such features. That said, I will be polling the location more often once the Location Profiles are released, as I'll need to know to trigger them.

If you go to the utter! Power User Settings and tick 'remove notification' so it is ticked. That will resolve the wording on the notification and it opening the Android Application Settings instead.

Google fixed the hack I was using on 4.1 (might have been 4.2), so now you have to have the notification displayed. In 4.3+ the notification will not appear in the status bar, only when you pull down the shade. This doesn't apply to the permanent recognition icon - I don't want any users accidentally leaving it on and then rating the app 1* because it killed their battery........

However, on some devices, the tick box 'show notifications' in the Android Application Settings for utter! will remove it, but it will show no others either.

Due to the way utter! is designed, it needs to have a permanent notification as a sign to the System that it must be the last service to be killed in low memory conditions. I've experimented with using a low priority, but with the likes of Google TTS hammering the device memory on initialisation, it was killed by Android before it even got to speak.......

So, the notification in some shape or form (unless you use the root app above) has to be there to stay.....

You are absolutely correct :good: I'm not sure if there is any side-effect to using these apps to remove the notification, I doubt it, as they'd have make other changes too, which would be overly complex.

:good:

1) It's still an issue on some of my test devices, but it is better. Like IVONA, I suspect with every update it will get faster and faster. It also depends on the memory conditions of your device at the time it launches.

2) For new users, it's essential that they understand that utter! 'tried' to match something, rather than just outright got it wrong (in some cases). I will be adding a way to replace all responses very soon. Your quick fix for now is to find out what Google is sending back when you say 'open Tasker' and use a replace words feature. Replacing the most likely 'open task her' with 'open Tasker' will hopefully solve this annoyance for you!

3) They usually come with a disclaimer that it could cause the app to function incorrectly - It just lowers the priority of DONT_KILL_ME and takes a chance........ I can't do this with utter! as TTS + audio recording + network connection + resulting launched app = death!

4) Oops! I forgot to enable something in my code. Will fix for the next release :good:

5) I'm going to keep nagging Google about this until they realise what an issue it is for apps that use this implementation. Removing the beep is great to solve this issue, but the impending amount of users that will speak too early is a load of 1*'s waiting to happen.......

Thanks for your input :good:

Bit by bit I'm getting there. I've got the 'don't connect to headset' option in the next release. Strangely, with some of my head sets that automatically route the audio, it works better! Time will tell........

Thanks for reporting this :good: Handled in the next release.

Banging my head against the wall with this one. Here's what your logging showed for the above request:

Your current device time

Default Calendar: Mon May 19 12:16:28 PDT 2014

Default Calendar TimeZone: Pacific Standard Time

Default Calendar EPOC: 1400526988216 (May 19 2014 12:16:28)

Your query

weekday: Tuesday

dotm: twentieth

month: May

year: 2014

EPOC: 1400569228136 (May 20 2014 00:00:28) <--- When I query the calendar from

Your events

eventNumber: 0

eventHour: 5

eventMinute: 0

eventAMPM: P.M

allDayFlag: true

eventStart EPOC: 1400544000000 (May 19 2014 17:00:00) <--- problem

eventNumber: 1

eventHour: 5

eventMinute: 0

eventAMPM: P.M. ...

allDayFlag: true

eventStart EPOC: 1400630400000 (May 20 2014 17:00:00) <--- problem

You'll see from the above, that the event times are out - and they are specifically out by your GMT and daylight saving offset.

The EPOC time I using to query the calendar, as you'll see from the above, is correct for your timezone - I use this handy website to double check.

Your events have the wrong start and end time, which is causing the overlapping.

I've tried readjusting the offset (-7 hours), but it's a flawed implementation.

So, unless there's something amiss with your calendar settings or your time & date settings (Android), I still remain stumped.......

What happens if you both create a calendar entry for a duration of one hour starting at 9pm?

Even with the offset issue, is should still be the same day, but I assume utter! will announce the start time incorrectly?

Thanks for your assistance on this one! I'm sure I'm missing something...... Well, I am! Just don't know what! :BangHeadAgainstWall:

-----------------------------------------------------

Thanks for all of the feedback as usual folks :good:

I'm just applying a few finishing touches to the next test build, which will actually be the Play Store release. I can't hold out any longer to push an update there.

Until then......

-----------------------------------------------------

For back page arrivals, the latest test build can be found here - CLICK ME

-----------------------------------------------------