- Nov 7, 2016
- Reaction score
Donation incoming! Thank you for all the great work!
So johnboy00 and I have been working on this today, and found that If you revert the Google TSS Engine back to Factory settings, Without any updates. This problem seems to be fixed. This isn't a Permanent fix, since it will try to auto update the App and the problem will reappear.For some unknown reason....when I get KA alerts now it will say something like "Front KA dot". Did this twice today driving home.
FYI You can use it without having to pair a V1 to it. It's called standalone mode. That's what I'm currently doing. I wanted to learn the features that weren't V1 specific first, as my interest in the app was with the CSAs, PAWS, Weather RADAR overlay, and Heat Map overlay. I figure I'll run it in standalone mode a few more weeks and then begin learning about the options of pairing it to my V1 Gen 2. In the meantime, I have V1 Driver paired with my V1 Gen. 2. I didn't want to overload myself right away, as this app is by far one of the most in depth apps I've ever used.I dont run this app yet, but I cant wait to! the functionality looks incredible!
JB, I'm also getting Dot announced all of a sudden, I could not uninstall the update to Google TTS but I did uninstall and reinstall and we'll go test again today. This just started a couple days ago for me out of the blue.@V1Jake Periods aren't supposed to be spoken by TTS. Another user fixed this by uninstalling updates to the Google Text-to-Speech engine and disabling further updates. The fact that this issue isn't occuring on every phone, that it started just a few days ago, and that the most recent update is now shown as September 23, makes me think that perhaps an update was released and then pulled and that many phones (like mine) never picked it up. I'd suggest uninstalling updates to Google TTS and then either disabling updates or updating again to see if it stops speaking the periods.
You need to revert back to previous or original file, the most recent update seems to be the problem, so uninstalling and reinstalling just adds the problem back in. Go to the play store and search for Google TTS, click bubbles on top right, click revert to factory. Then disable updates.JB, I am still on the S8+, so yes to Samsung, but I have been using Google TTS. I am still getting the "Dot" today after my uninstall/re-install. It has happened over the past 4 days, my Google TTS did update in Sept. I assume they did a Ghost update for things to randomly change like this. I am open to any testing if needed. I have it on recorded as Jake did, I don't think that adds and value to you, but can send if desired.... Also, this isn't pressing to me, I can live with it. Your software is so amazing there isn't anything that would keep me from using it.
I don't have that option. Maybe the rooted ROM I'm using, not sure.You need to revert back to previous or original file, the most recent update seems to be the problem, so uninstalling and reinstalling just adds the problem back in. Go to the play store and search for Google TTS, click bubbles on top right, click revert to factory. Then disable updates.
Sent from my Pixel 4 XL using Tapatalk
If there was one source option everyone should be using, there would be no source option.
Do you care how much data is used? If not, use ALL or HwR. If you do care, use AUTO or a specific source (a-c). They all have "global" coverage, but some may be worse than others in some areas. I can't evaluate coverage for every corner of the globe.
I retract that I was in the source config in advanced and not just looking at the paws source. I am the dumb.JB, in 2.5.5 i do not see HwR as a source option. I am upgrading to .5.6 just in case.