Related
My Google maps navigation seems to to get stuck in loop and repeats the last set of directions over and over the list directions are right just the voice part. I'm on team perfection rom. I've cleared the cache and all but it just keeps happening maybe its from this last Update. Anyone else?
Sent from my SAMSUNG-SGH-I717 using xda premium
Mine has been working well after the update. Try clearing the data then uninstall, reboot, and reinstall.
Sent from my SAMSUNG Galaxy Note using XDA Premium HD app
nthknd said:
My Google maps navigation seems to to get stuck in loop and repeats the last set of directions over and over the list directions are right just the voice part. I'm on team perfection rom. I've cleared the cache and all but it just keeps happening maybe its from this last Update. Anyone else?
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Same issue here. Running Only1 base. I have to clear app data every week or it gets stuck repeating the route from the state I was previously working in. The map directions are accurate, but the voice keeps saying to turn on a road from the previous week. Over and over and over again. Crazy.
rsfinsrq said:
Same issue here. Running Only1 base. I have to clear app data every week or it gets stuck repeating the route from the state I was previously working in. The map directions are accurate, but the voice keeps saying to turn on a road from the previous week. Over and over and over again. Crazy.
Click to expand...
Click to collapse
Yep it also happen on my skyrocket running the collective rom. Wtf
Sent from my Xoom using xda premium
Why don't you guys use a NAV app that doesn't need data connection? I've been using CoPilot Live Premium and haven't had any problems whatsoever.
Same here
Hi!... same happening here.. Happened with Epsilon ROM... then with WanamLite 12.0 it worked ok for a few days, then it started repeating the route over and over again =((
No solution for this??
moreaup said:
Hi!... same happening here.. Happened with Epsilon ROM... then with WanamLite 12.0 it worked ok for a few days, then it started repeating the route over and over again =((
No solution for this??
Click to expand...
Click to collapse
Same problem, Galaxy Nexus VZW on JellyBean, was having the issue on ICS as well. Did an uninstall/clear cache...worked for a while, and then started repeating again. Only thing that fixes it temporarily is clearing the app's data.
Happens to me once a week. Go to applications in settings, force stop maps, clear data, and reopen maps/nav. Problem solved. Its getting very annoying though, to do this once or twice a week.
Sent from my SAMSUNG-SGH-I717 using xda premium
Same problem
This is my same problem and my location never picks up anymore..this is why I'm trying to go back to gingerbread cuz I never had a problem with maps
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
I had the same problem on the Team Perfection ROM, in addition to it not using my Ivona TTS voice or speaking street names. Clearing cache and data didn't help, neither did an uninstall and reinstall from Play. What DID work however, was installing an older version apk I found (which kept FC for some reason), and then updating that version from Play. (Sorry, I don't recall which version it was, but I downloaded it from Aptoide.) After that, everything worked perfectly again. I noticed other people complaining about the same problem in Play's comments section. Really strange, but at least it works again for me.
Settings > Language & input > text to speech output.
Changing this to Pico TTS fixed it for me.
This has been happening on my phone (Verizon Galaxy Nexus on 4.1.1 JB AOKP build 2) on and off for a few months now, it first started happening right before android 4.1 Jellybean was officially announced. *It was at that precise time that the voice for Google Maps Navigation changed to be the same voice that Google Now uses in Jellybean. I remember there was a period of time where I would hear both voices like they hadn't finished converting all of the speech over to the new voice. It's been ever since then but this problem has been happening, I have noticed the clearing cache seems to sometimes stop it from happening only to return again randomly.
Sent from my Galaxy Nexus using Tapatalk 2
Protonus said:
This has been happening on my phone (Verizon Galaxy Nexus on 4.1.1 JB AOKP build 2) on and off for a few months now, it first started happening right before android 4.1 Jellybean was officially announced. *It was at that precise time that the voice for Google Maps Navigation changed to be the same voice that Google Now uses in Jellybean. I remember there was a period of time where I would hear both voices like they hadn't finished converting all of the speech over to the new voice. It's been ever since then but this problem has been happening, I have noticed the clearing cache seems to sometimes stop it from happening only to return again randomly.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Looks like this might be the solution, going to try it will report back.
http://forum.xda-developers.com/showpost.php?p=26802275&postcount=373
Any updates?
orvtech said:
Any updates?
Click to expand...
Click to collapse
Yup, the fix i posted above has worked since I did it.
Protonus said:
Yup, the fix i posted above has worked since I did it.
Click to expand...
Click to collapse
I tried that but latter I got the same error. I am guessing that something is corrupting my data, either an app or faulty hardware.
did you uninstall any app by any chance?
Maps issue
Does anyone here know why my stock map flickers and cause force close in stock navigation. I'm on a custom rom and was wondering if it was the rom or the stock map app. Can anyone help, because I love using google map and navigation.
hue180 said:
Does anyone here know why my stock map flickers and cause force close in stock navigation. I'm on a custom rom and was wondering if it was the rom or the stock map app. Can anyone help, because I love using google map and navigation.
Click to expand...
Click to collapse
what rom and kernel are you currently using?..The flicker is a issue with some roms..editing the maxlayer overlay build prop helped with alot of people.
Did anybody think to post what version of google maps your using, without it any fix or info is almost useless because it might work for one version but not another (ex// im on 6.14.1 but someone else may not if not updated or running old GApps
Hey all, I seem to be having an issue with the Pandora app. It is an app I use heavily, which it crashing is driving me bonkers.
Here's what happens. I open the app and it stays open until it starts to play/load music. The moment the artist information shows up the app closes itself. I had flashed the debloat script and rooted the phone. Then I disabled swap and of course, installed all my apps. Later I noticed the Pandora app crashing problem. I figured it was probably something the debloat script removed that I might have needed so I recovered to stock and only restored root. Low and behold, Pandora worked fine. I spent an hour or two listening and reading a book. I paused it so I could prepare for bed and when I hit play, it crashed again. Tried rebooting the phone, clearing the apps cache/data and reinstalling. Nothing seems to work. The app is set as a protected app in the settings. Also, I have the KIW-L24(USA) model.
tldr: Read the title
Hoping someone has some hints they could throw my way. It seems curious that the app would work for a few hours then only stop working after I paused and then hit play again. If anyone has any advice, please shoot it my way.
What software build do you have? This issue was previously reported, but it should be fixed by now. Also, what version is the Pandora app?
wimbet said:
What software build do you have? This issue was previously reported, but it should be fixed by now. Also, what version is the Pandora app?
Click to expand...
Click to collapse
Build number: KIW-L24C567B140
Pandora: version 6.9.2 (I have Pandora One, just in the off chance that would matter?)
I just cleared the app cache, deleted the app data, uninstalled, then booted into twrp, cleared the dalvik cache and rebooted (as I stated in the first post, I had done this all before). It now seems to be working. If it begins to crash a third time, I'll update.
And it started crashing again. I may have found the culprit. Everything was kosher until I allowed notifications. When I did the app crashed, with near instant crashes there on. Shut off notifications for Pandora in settings and it works like a charm.
Edit: I can repeat this issue by enabling/disabling notifications. A bit annoying, bit at least the app works.
Sent from my KIW-L24 using Tapatalk
I had just found this issue with my phone too, can't enable notifications, wonder why it does that
Sent from my KIW-L24 using Tapatalk
ZeRo2o9 said:
I had just found this issue with my phone too, can't enable notifications, wonder why it does that
Sent from my KIW-L24 using Tapatalk
Click to expand...
Click to collapse
Bugs are fun, no? The phone is new, you'll always find a few.
Sent from my KIW-L24 using Tapatalk
mematt69 said:
Build number: KIW-L24C567B140
Pandora: version 6.9.2 (I have Pandora One, just in the off chance that would matter?)
Click to expand...
Click to collapse
Have you tested with the new Pandora 7.0?
wimbet said:
Have you tested with the new Pandora 7.0?
Click to expand...
Click to collapse
Google Play shows 6.9.2 as up to date. If you could explain how to download Pandora 7.0, I will try it out.
mematt69 said:
And it started crashing again. I may have found the culprit. Everything was kosher until I allowed notifications. When I did the app crashed, with near instant crashes there on. Shut off notifications for Pandora in settings and it works like a charm.
Edit: I can repeat this issue by enabling/disabling notifications. A bit annoying, bit at least the app works.
Sent from my KIW-L24 using Tapatalk
Click to expand...
Click to collapse
Good find, thank you. I had the exact problem, tried the exact same fixes. Disabling notifications fixed instantly. CM can't come soon enough.
wimbet said:
Have you tested with the new Pandora 7.0?
Click to expand...
Click to collapse
I have now updated to Pandora 7.0, the issue is still there.
Sent from my KIW-L24 using Tapatalk
chefchuck said:
Good find, thank you. I had the exact problem, tried the exact same fixes. Disabling notifications fixed instantly. CM can't come soon enough.
Click to expand...
Click to collapse
I'm using an unofficial build uploaded by bandit development. It works fine and everything runs very smoothly. The only things that don't work are the fingerprint reader, the back camera, and the back flash.
My clock only responds to "Ok Google" maybe 2 out of 10 times. When it works (or when I swipe to "Speak now" manually) the voice control is almost flawless (I'd say 95% success rate), so it obviously understands me.
What could be wrong and is there something I could do about it?
djr83 said:
My clock only responds to "Ok Google" maybe 2 out of 10 times. When it works (or when I swipe to "Speak now" manually) the voice control is almost flawless (I'd say 95% success rate), so it obviously understands me.
What could be wrong and is there something I could do about it?
Click to expand...
Click to collapse
I have exactly the same problem but with the 360 sport. If I delete and retrain the voice model on my phone it seems to temporarily fix the issue. Have tried factory reset, removing the wear app and reinstalling all to no avail. Have you had any luck? Im going to try pairing to a different phone to see if it's my phone or the watch. If that doesn't work I'm returning thE watch.
Mars104 said:
I have exactly the same problem but with the 360 sport. If I delete and retrain the voice model on my phone it seems to temporarily fix the issue. Have tried factory reset, removing the wear app and reinstalling all to no avail. Have you had any luck? Im going to try pairing to a different phone to see if it's my phone or the watch. If that doesn't work I'm returning thE watch.
Click to expand...
Click to collapse
That won't do any difference. I've tried another Moto 360 with another phone and it works as bad on the "Ok Google" part.
Retrain the command doesn't work when using another language than English so I haven't tried that.
I don't have scientific proof, but I believe different watch face apps provide different results. When I have had the "OK Google" problem, changing the watch face solved it.
kat3k said:
I don't have scientific proof, but I believe different watch face apps provide different results. When I have had the "OK Google" problem, changing the watch face solved it.
Click to expand...
Click to collapse
I haven't noticed any difference and most watch faces have been the stock ones that comes with Moto 360.
in my opinion, the stock watch faces respond faster than custom watch faces
I've had the same problem from Day One, the response to the keyword is far more haphazard than it was with my LG G Watch, but the speech recognition once past that is about the same; changing how I say "Okay Google" seems to be the only thing that makes any difference.
djr83 said:
My clock only responds to "Ok Google" maybe 2 out of 10 times. When it works (or when I swipe to "Speak now" manually) the voice control is almost flawless (I'd say 95% success rate), so it obviously understands me.
What could be wrong and is there something I could do about it?
Click to expand...
Click to collapse
Same for me. I had the LG Watch R before (a year ago) and it was working flawless. Thinking about buying the Fossil Q Founder. But new watches will be out soon when Google releases Wear 2.0, I guess.
Just to update. I recieved my replacement moto 360 sport. The 'ok google' command still only works about 20% of the time. It seems apparent this is a software issue as the mic and voice recognition seem to work fine. I hope this is fixed in wear 2.0 or another update.
In the meantime my workaround was to create a floating icon in AutoWear that launches GoogleNow on my watch. Now I just press the icon on my watch whenever I need to launch GoogleNow to set an alarm/reminder etc.
Mars104 said:
Just to update. I recieved my replacement moto 360 sport. The 'ok google' command still only works about 20% of the time. It seems apparent this is a software issue as the mic and voice recognition seem to work fine. I hope this is fixed in wear 2.0 or another update.
In the meantime my workaround was to create a floating icon in AutoWear that launches GoogleNow on my watch. Now I just press the icon on my watch whenever I need to launch GoogleNow to set an alarm/reminder etc.
Click to expand...
Click to collapse
How do you launch Google Now? It's not available under system apps.
So for me it shows an an available system app in autowear 'mange app actions' section (see attachment). If it's not in your version maybe it is a beta feature. I signed up for the beta test release :
http://joaoapps.com/beta-testing/
Mars104 said:
So for me it shows an an available system app in autowear 'mange app actions' section (see attachment). If it's not in your version maybe it is a beta feature. I signed up for the beta test release :
http://joaoapps.com/beta-testing/
Click to expand...
Click to collapse
What version do you have?
1.0.26
Mars104 said:
1.0.26
Click to expand...
Click to collapse
Same as me, but I still don't have Google Now in system apps. What could be wrong? Running Android 7 DP5.
Not sure. I'm running Google 6. The new update (M1D63G) seems to have improved 'ok google' detection. Not done much testing yet, but so far so good.
Mars104 said:
Not sure. I'm running Google 6. The new update (M1D63G) seems to have improved 'ok google' detection. Not done much testing yet, but so far so good.
Click to expand...
Click to collapse
I've done some testing and it worked all of the times except one. But that time I just said "Ok, Google" again and it worked. Before it has never worked after a fail without letting the watch be for a long while.
I'll test it more the coming days.
When I activate google with a voice command I no longer get an audible ready beep and unable to get voice toolbar on home screen. Anybody else having this problem using Google Now launcher.
Is it normal for the device to be listed as pixel even though I'm using the Google Now launcher under Google settings
Plz dont use beta version , mine had same bug
bkwas said:
When I activate google with a voice command I no longer get an audible ready beep and unable to get voice toolbar on home screen. Anybody else having this problem using Google Now launcher.
Is it normal for the device to be listed as pixel even though I'm using the Google Now launcher under Google settings
Click to expand...
Click to collapse
try clearing app data and re train the voice,
i do use beta from a long time, i didnt faced any such issues
thilak devraj said:
try clearing app data and re train the voice,
i do use beta from a long time, i didnt faced any such issues
Click to expand...
Click to collapse
On 7.1 that data wipe dint worked , it trains voice once and later it wont detect my voice . Happend on my own build of purenexus.
gopinaidu77 said:
On 7.1 that data wipe dint worked , it trains voice once and later it wont detect my voice . Happend on my own build of purenexus.
Click to expand...
Click to collapse
Wiered.. Sometimes **** just happens.. I'm on beta since the marshmallow days, no problem at all
But mine had issues. I dont mind about it , as i am not a user of voice commands
Hi,
As you may have known, ok Google issue has been solved in recent miui 10 stable update. Now it offers to unlock the device using voice match even when the display is turned off.
Now even I say ok Google when the screen is turned off, it does wake the device but it's still locked and it shows me pattern unlock.
How to unlock the device so that I can pass an actual command to Google assistant?
Thanks
My phone just updated to MIUI Global 10.0 (10.0.4.0 OEJMIFH) and it was fixed.
Now I can say 'Ok Goolge' and it opens assistant.
Phone unlocking by voice command is disabled by miui and afaik even Google is removing this feature from assistant, security reasons probably
lipaum said:
My phone just updated to MIUI Global 10.0 (10.0.4.0 OEJMIFH) and it was fixed.
Now I can say 'Ok Goolge' and it opens assistant.
Click to expand...
Click to collapse
Yes that works but I was talking about unlocking the phone.
OK google works on miui 10 Global stable?
I didnt know that, i thought it just work on stock base android roms.
pack21 said:
OK google works on miui 10 Global stable?
I didnt know that, i thought it just work on stock base android roms.
Click to expand...
Click to collapse
It was broken when the device came out. Now they fixed it on popular demand. [emoji16]
lockhrt999 said:
Yes that works but I was talking about unlocking the phone.
Click to expand...
Click to collapse
Did you try 'Voice Match Unlock' (or something because mine is in portuguese) in settings? Here (again) is working.
Sent from my Poco F1 using XDA Labs
lipaum said:
Did you try 'Voice Match Unlock' (or something because mine is in portuguese) in settings? Here (again) is working.
Sent from my Poco F1 using XDA Labs
Click to expand...
Click to collapse
Yes, I did that. It does wake up the device but doesn't unlock it.
Edit: Sorry. I wasn't facing the same issue. I was facing the issue where the Google Assistant wasn't working properly, and it would show me the error "unable to open microphone".
I found the solution on the MIUI forums. Here's what I did...
You have to go to the Google app in "Installed Apps" and clear the cache and the data and reboot, and it'll start working fine.
It was a little tricky to find the Google app as it wouldn't show in the Installed Apps. You have to click on the 3 dots on the upper right side corner and select "Show all apps" and then it'll show up. After that, you just clear the cache and the data and reboot phone, and it'll start working properly
Nevertheless, I tried your solution and it didn't work either way.
Ok Google straight up doesn't work for me
Delete data, clear cache, udpate app. This worked for me
muham47 said:
Delete data, clear cache, udpate app. This worked for me
Click to expand...
Click to collapse
There are lots of different places where I can delete Google data. Could you walk me through it?
muham47 said:
Delete data, clear cache, udpate app. This worked for me
Click to expand...
Click to collapse
you are saying you can wake and unlock the sleeping phone by saying ok Google, right?
I have tried deleting cache and data, updating but it didn't work for me.
What exactly did you do?
Google's quietly removes Voice Unlock on Pixel 3
lockhrt999 said:
Nevertheless, I tried your solution and it didn't work either way.
Click to expand...
Click to collapse
Don't get your hopes high about this feature's implementation on OEMs. Google were already silently phasing-out this feature and the OEMs will soon to follow.
Refer to these links:
https://www.theverge.com/2018/10/19/18001460/google-pixel-3-xl-google-assistant-voice-match-removed
https://9to5google.com/2018/10/26/google-killing-android-voice-unlock/
lockhrt999 said:
you are saying you can wake and unlock the sleeping phone by saying ok Google, right?
I have tried deleting cache and data, updating but it didn't work for me.
What exactly did you do?
Click to expand...
Click to collapse
Yep, i just cleared cache, data then udpated the google app and it worked.
---------- Post added at 03:09 AM ---------- Previous post was at 03:04 AM ----------
raydialseeker113 said:
There are lots of different places where I can delete Google data. Could you walk me through it?
Click to expand...
Click to collapse
Go to settings -> installed apps -> search for google, tap on google app -> tap clear data, clear cache, uninstall updates, then update your google app.
muham47 said:
Go to settings -> installed apps -> search for google, tap on google app -> tap clear data, clear cache, uninstall updates, then update your google app.
Click to expand...
Click to collapse
Tried this as per instructions but still no avail. Are you using stable MIUI version?
lockhrt999 said:
Tried this as per instructions but still no avail. Are you using stable MIUI version?
Click to expand...
Click to collapse
It sort of works for me (Stable 10.0.6.0). However, following those instructions it only wakes the phone, but doesn't unlock. But - after getting to that point, I went into the Google assistant, settings, voice, voice match and it let me select the slider - gave me a warning about being less secure, and then it woke up AND unlocked via voice.
Unfortunately, it then failed to do it the next time I tried it and asked for my pattern/face. Not sure if it requires log in sometimes and not others, or if the first time was just luck!
At one point it would wake up and let me ask a question, but only read or show me the answer when I unlocked, but now it won't even do that, so basically it's completely inconsistent! hurrah!
Clearly some sort of security issue - whether it's Xiaomi or Google's fault is up for debate, but if Google are removing it from their flagship then I wouldn't be surprised if it never works properly on anything else.
If they would only get Trusted Places working properly (Google that is) or even allow trusted Wifi (I know the security implications but I'm prepared to accept them!) then it would probably not be necessary.
I could keep it unlocked with my watch, but then I find that (despite pocket mode) my phone regularly does random things while in my pocket!
I had similar issues with my Mate 10 Pro, that I've just changed from, so it's not solely Xiaomi's fault, but is it really too much to ask to expect Android features that are offered to actually work out of the box?!
gonzo99 said:
It sort of works for me (Stable 10.0.6.0). However, following those instructions it only wakes the phone, but doesn't unlock. But - after getting to that point, I went into the Google assistant, settings, voice, voice match and it let me select the slider - gave me a warning about being less secure, and then it woke up AND unlocked via voice.
Unfortunately, it then failed to do it the next time I tried it and asked for my pattern/face. Not sure if it requires log in sometimes and not others, or if the first time was just luck!
At one point it would wake up and let me ask a question, but only read or show me the answer when I unlocked, but now it won't even do that, so basically it's completely inconsistent! hurrah!
Clearly some sort of security issue - whether it's Xiaomi or Google's fault is up for debate, but if Google are removing it from their flagship then I wouldn't be surprised if it never works properly on anything else.
If they would only get Trusted Places working properly (Google that is) or even allow trusted Wifi (I know the security implications but I'm prepared to accept them!) then it would probably not be necessary.
I could keep it unlocked with my watch, but then I find that (despite pocket mode) my phone regularly does random things while in my pocket!
I had similar issues with my Mate 10 Pro, that I've just changed from, so it's not solely Xiaomi's fault, but is it really too much to ask to expect Android features that are offered to actually work out of the box?!
Click to expand...
Click to collapse
You're right. But if it had worked then it would have been a great party trick. I never had a phone which could wake up with an audio command.
lockhrt999 said:
You're right. But if it had worked then it would have been a great party trick. I never had a phone which could wake up with an audio command.
Click to expand...
Click to collapse
The irony is that I've just switched from a Huawei Mate 10 Pro (Various reasons, but flaky bluetooth top of the list) and that did do it after the last update. That's because they have their own voice recognition baked in to the Kirin chipset though I think, so it's not using just Google's voice match - and even that took a lot of fiddling to get working. No idea how secure it was, but it was handy for finding the phone by asking it where it was! I refuse to talk to my phone in public anyway, so it's something I can live without I think