I get a lot of repeated messages where the app generating the message sends an empty message, and then a (repeated) message. In other words, it 'fools' voice notify. This seems quite common across a lot of apps, I dont know why!
Voice Notify already helps, but the 'repeated message' mechanism looks at messages coming in, not messages that have been 'voiced', so this sort of 'empty message' behaviour fools Voice notify....
Voice Notify could deal with this very easily, if voice notify isn't going to 'say' the message (it's repeated, or its empty), then dont record it as the 'lastMsg' - so that Voice Notify really doesn't repeat itself :-)
Looks like a very simple fix around like 229 of Service.java ? Only record the lastMsg if the message hasn't been ignored?
I get a lot of repeated messages where the app generating the message sends an empty message, and then a (repeated) message. In other words, it 'fools' voice notify. This seems quite common across a lot of apps, I dont know why!
Voice Notify already helps, but the 'repeated message' mechanism looks at messages coming in, not messages that have been 'voiced', so this sort of 'empty message' behaviour fools Voice notify....
Voice Notify could deal with this very easily, if voice notify isn't going to 'say' the message (it's repeated, or its empty), then dont record it as the 'lastMsg' - so that Voice Notify really doesn't repeat itself :-)
Looks like a very simple fix around like 229 of Service.java ? Only record the lastMsg if the message hasn't been ignored?