Database Develop

Trouble with "Ok Google" Always On

[Original Post]
"Ok Google" works fine for me when the phone is on/unlocked without any training. However, to have it work even when the screen is off or the phone is locked it requires training your voice. For the life of me I can't get it to accept the training. It wants to record you saying "Ok Google" three times and it will move on to the second and third recordings after a previous recording is successful. I can't get it to move past the first recording. It just listens for a while and then times out. Anyone else have this issue? Any thoughts on how to resolve it?
[Update 1]
Clearing Google Search data made voice training quick and easy, but my option to have it always on has disappeared. See my post below. Thoughts?
[Update 2]
I just rebooted the phone and my "always on" option has returned but it wants me to retrain my voice. Now I can't get past the first recording again...

I don't have that issue. Voice training went off without a hitch. Did you go to a quiet place like the instructions said?

jakester99 said:
I don't have that issue. Voice training went off without a hitch. Did you go to a quiet place like the instructions said?
Click to expand...
Click to collapse
Thanks for the response. Yes, I was in a location with no sound.
Since posting the original post I found this thread where someone suggested clearing Google Search app data. I tried it and voice training was quick and easy. However, I don't seem to have the option for this to work with the screen off anymore. I can only do it when the screen is on, locked or unlocked.
Here is what the options used to look like (not my screenie, I just found this image on the web, probably from an N9 or something):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now here is what my screen looks like:
I no longer have the "always on" option. One step forward, one step backward.

@Marcellus1 I see that no one has offered any help here and I can't either. My N6 has the issue that your first picture shows. I am running Validus 5.0.1 alpha 1.0 Rom. I have read that this is an issue with all AOSP ROMs right now but there isn't very much being discussed about it. If you find a solution, please let me know. If I find one I'll definitely post it here.
The odd thing is that my my N5, N7(2013) and N9 all have this feature working flawlessly, all running Lollipop. My N6 is the only device with issues and I have tried 3 different ROMs as well as several different gapps packages to try to solve it to no avail.

you can try this thread, as thats what fixed my ok google everywhere and with screen off and unplugged http://forum.xda-developers.com/nexus-6/general/ok-google-everywhere-aosp-rom-t2963716
btw, im on rastapop.

I appreciate the replies. It seems that the fix is only a 50-50 chance of working AND it requires a custom ROM. I'm on stock, no root, no custom recovery, no anything special. I'll probably switch to a custom ROM at some point, but for now I don't think I'm ready to make the switch. One post mentioned in that thread referenced this other thread: http://forum.xda-developers.com/showpost.php?p=57335716&postcount=295
The suggestion is to clear search and play data in order for the changes to survive a reboot, but that you lose the option for always on while not plugged in. That doesn't seem optimal either. Word is Android 5.1 due out in February or so will address "Ok Google" issues, which hopefully means this issue. Maybe I'll just sit tight until 5.1 rolls out before trying factory resets, custom ROMs or the like.

I had a Pressy inserted into my headphone port. Ok Google worked fine on the homescreen with the Pressy inserted, but it would not work with the voice training with the Pressy installed. If i did the voice training without the Pressy, then put the Pressy in, Google Now still worked ok on the homescreen, but not with screen off.
EDIT: I am rooted on stock ROM.

PaisanNYC said:
I had a Pressy inserted into my headphone port. Ok Google worked fine on the homescreen with the Pressy inserted, but it would not work with the voice training with the Pressy installed. If i did the voice training without the Pressy, then put the Pressy in, Google Now still worked ok on the homescreen, but not with screen off.
EDIT: I am rooted on stock ROM.
Click to expand...
Click to collapse
That's interesting. I've had a pressy in my headphone jack. When I try training my voice with Pressy inserted, the phone just endlessly listens and eventually times out. When I removed it and tried voice training again I immediately got "something went wrong" and "It's a little too noisy in here. Please find a quieter place and try again". (and I'm in a quiet place).
[EDIT]: As a follow-up, I've uninstalled Pressy and the AutomateIt Pressy plugin. I've cleared my search data, and installed the new Google (search) app (http://www.androidpolice.com/2015/01/07/google-app-hits-version-4-1-now-cards-settings-apk-download/), but still no luck training my voice.

getting ok google to work, we have found a solution that should work for you.. http://forum.xda-developers.com/nexus-6/general/ok-google-everywhere-aosp-rom-t2963716

simms22 said:
getting ok google to work, we have found a solution that should work for you.. http://forum.xda-developers.com/nexus-6/general/ok-google-everywhere-aosp-rom-t2963716
Click to expand...
Click to collapse
Thanks for your suggestion but it did not work. I saw your suggestion previously and put it off because I didn't want to have to root my device. However, after getting the updated google (search) app today and it still not working, I decided to give it a go. Unlocked the device, rooted it, etc, then copied the files mentioned in your solution to the appropriate locations. Rebooted the device and now my "always on" feature is grayed out and disabled--it says this feature is currently unavailable for this language. The language is set to English (US). I cleared the search app data and was able to train the device immediately, but it was just like my post above where the always on is limited to when the screen is on and unlocked or when charging. Rebooting the phone and/or re-installing the updated google (search) app (because I lost it during the rooting process) takes me back to "this feature is currently unavailable for this language".
[EDIT]: I was looking through that thread some more and saw that some were having some success with flashing the zip by hlxanthus that was a little bit different from the original suggestion. I took my root a step further and installed a custom recovery and then flashed hlxanthus's zip. There is no change.
[EDIT 2]: As a follow-up to the previous edit, after flashing hlxanthus's zip, clearing search data no longer makes a change to enable voice training.

sledge3n8 said:
@Marcellus1 I see that no one has offered any help here and I can't either. My N6 has the issue that your first picture shows. I am running Validus 5.0.1 alpha 1.0 Rom. I have read that this is an issue with all AOSP ROMs right now but there isn't very much being discussed about it. If you find a solution, please let me know. If I find one I'll definitely post it here.
The odd thing is that my my N5, N7(2013) and N9 all have this feature working flawlessly, all running Lollipop. My N6 is the only device with issues and I have tried 3 different ROMs as well as several different gapps packages to try to solve it to no avail.
Click to expand...
Click to collapse
Sledge, I don't know if you ever got your Ok Google working, but I thought I'd post that it's working now for me with the 5.1 update without any tweaks or workarounds.

Marcellus1 said:
Sledge, I don't know if you ever got your Ok Google working, but I thought I'd post that it's working now for me with the 5.1 update without any tweaks or workarounds.
Click to expand...
Click to collapse
Thank you very much for the update! I was still having the issue and just forgot about it. I was thinking about trying out the 5.1 update but just haven't gotten around to it.

Me too, does not work with marshmallows, you have found a solution?

works fine on marshmallow over here. i even taught it to listen for ok nexus instead of ok google.

Do you have Now on Tap or Smart Lock enabled? Some people have reported that these cause issues with hot word detection.
simms22 said:
works fine on marshmallow over here. i even taught it to listen for ok nexus instead of ok google.
Click to expand...
Click to collapse
Would you mind sharing how? I'd love to have that on my phone.

Face_Plant said:
Do you have Now on Tap or Smart Lock enabled? Some people have reported that these cause issues with hot word detection.
Would you mind sharing how? I'd love to have that on my phone.
Click to expand...
Click to collapse
on tap is enanled. how? the normal way, it just works.

simms22 said:
on tap is enanled. how? the normal way, it just works.
Click to expand...
Click to collapse
Interesting. It must listen for "OK" instead of the whole "OK, Google".

Face_Plant said:
Interesting. It must listen for "OK" instead of the whole "OK, Google".
Click to expand...
Click to collapse
ahh, the ok nexus you meant.. yea, i think it listens for the ok mostly. but the second word cant be too different than google in syllables.

This Feature is Broken Again!!!
I've noticed this is broken on Android N. I often clean install custom ROM and then the latest OpenGApps only to find that when I toggle on OK Google "Always On" the toggle instantly turns itself back off the moment I turn it on. There's some work arounds on the forums and I can usually make it work by Installing and old version of the Google App clearing all data for Google App then training voice model and setting OK Google "Always On" toggle to "On". Then after everything is working I go ahead and update Google App from Play Store and usually it keeps working. Sometimes it breaks again. I'm tired of working around this. I wanna know if it will ever again be possible to use this feature. This has been going on for months. Perhaps they should just remove the feature all together then at least it won't be there broken and useless.

[Q] Google Now not working. Network error. [SOLVED]

Ok
I have a brand new Droid Turbo that is having problems with Google Now. I get no Cards. The Google now screen is blank except for the past 3 searched items.
If I swipe from the left and hit settings/Now Cards the first item is Show card which is off and I can't change it and it has an error messages under it that says "Network error. Check your network connection and try again."
I can browse the internet fine with all apps be it WiFi or Verizon 4G. I have tried to clear data from the Google App, I've uninstalled the latest update, I have done two factor resets. My Nexus 7 gets to this just fine. Any clues?
Thanks.
Nathan WIlliams

nlinecomputers said:
Ok
I have a brand new Droid Turbo that is having problems with Google Now. I get no Cards. The Google now screen is blank except for the past 3 searched items.
If I swipe from the left and hit settings/Now Cards the first item is Show card which is off and I can't change it and it has an error messages under it that says "Network error. Check your network connection and try again."
I can browse the internet fine with all apps be it WiFi or Verizon 4G. I have tried to clear data from the Google App, I've uninstalled the latest update, I have done two factor resets. My Nexus 7 gets to this just fine. Any clues?
Thanks.
Nathan WIlliams
Click to expand...
Click to collapse
I have the same exact issue too. Only it happens with certain apps too. Reddit sync pro is the worst/slowest app with the most lag. I made a thread on XDA a bit ago about the poor wireless/wifi performance,
http://forum.xda-developers.com/dro...vices-apps-t3035266/post58974614#post58974614
Also, here is a reddit link and a moto forum
http://www.reddit.com/r/droidturbo/comments/2wdb7c/slow_wifi_lag_with_google_services_and_certain/
https://forums.motorola.com/posts/06a2f3c5ca
http://forums.androidcentral.com/ge...-slow-google-services-facebook-wifi-only.html
Seems like many brands of routers paired with the Droid Turbo are acting up. Some report turning off IPV6 worked for them. It doesn't for me. I don't think it's a router issue as HTC and Apple devices work perfectly over wifi.
Hopefully Motorola gets the message...

jhmn7 said:
I have the same exact issue too. Only it happens with certain apps too. Reddit sync pro is the worst/slowest app with the most lag. I made a thread on XDA a bit ago about the poor wireless/wifi performance,
http://forum.xda-developers.com/dro...vices-apps-t3035266/post58974614#post58974614
Also, here is a reddit link and a moto forum
http://www.reddit.com/r/droidturbo/comments/2wdb7c/slow_wifi_lag_with_google_services_and_certain/
https://forums.motorola.com/posts/06a2f3c5ca
http://forums.androidcentral.com/ge...-slow-google-services-facebook-wifi-only.html
Seems like many brands of routers are effected. Some report turning off IPV6 worked for them. It doesn't for me.
Hopefully Motorola get the message...
Click to expand...
Click to collapse
You have completely misunderstood my problem.
I'm not having any lag nor are there any REAL network issues. My Google Now is blank. It doesn't show ANY cards. The error message says I have a network problem but I can use the phone just fine. Something is screwed up on Google Now. This has nothing to do with routers or anything of that nature.

nlinecomputers said:
You have completely misunderstood my problem.
I'm not having any lag nor are there any REAL network issues. My Google Now is blank. It doesn't show ANY cards. The error message says I have a network problem but I can use the phone just fine. Something is screwed up on Google Now. This has nothing to do with routers or anything of that nature.
Click to expand...
Click to collapse
Well, it just sounds mighty similar to what I and many others are experiencing.
Try it with wifi off and see if it does the same thing. For me, using verizons radio/data app grab data snappy like it should be. Wifi is my turbos issue.
Generally the turbo needs 2-3 tries of refreshing in in the play store, reddit sync, chrome and so on before loading images. For instance, the play store will show app tiles but take forever to load the icon. The wifi lag/poor responsiveness is intermittent happening around 50% the time an app needs data via wifi. Considering you just got your phone it might creep up on more apps as you use your phone. Just throwing it out there.
I also have the app Trend. Different apps show different errors and Trend will say "No data connection found" when my phone is acting shi**y over wifi. Refreshing it a couple of times generally restores data.

Had this issue just two days ago after refomatting my device and may have declined a google location setting. I posted my fix over in the Google help forums and this is what worked for me two days ago and its still working
Another thing to try that worked for me is> Google settings in the app drawer>Account History>Turn off Web&App Activity/Device Information/Voice & Audio Activity/ Youtube search History/ Youtube watch History/Google location History> wait five minutes and turn it all back on.
I tried this after i didnt know if it was my device or my account. so I deleted my google account from the phone and installed my wifes account and found "google now" worked perfect, so I knew it was in my account settings which was a relief. Thats how I found whats above worked for me. Maybe if the above doesnt work for you do as i did and install another persons google account on the phone see if the "google now "works then if it does then you know its your account, and try the above that worked for me.
https://productforums.google.com/forum/#!searchin/websearch/Google$20Now$20says$20%22No$20internet$20connection...%22$20but$20that$27s$20wrong%7Csort:relevance/websearch/5DAJe5-yWf4/w4a6zJjI65IJ

jdfrye said:
Had this issue just two days ago after refomatting my device and may have declined a google location setting. I posted my fix over in the Google help forums and this is what worked for me two days ago and its still working
Another thing to try that worked for me is> Google settings in the app drawer>Account History>Turn off Web&App Activity/Device Information/Voice & Audio Activity/ Youtube search History/ Youtube watch History/Google location History> wait five minutes and turn it all back on.
I tried this after i didnt know if it was my device or my account. so I deleted my google account from the phone and installed my wifes account and found "google now" worked perfect, so I knew it was in my account settings which was a relief. Thats how I found whats above worked for me. Maybe if the above doesnt work for you do as i did and install another persons google account on the phone see if the "google now "works then if it does then you know its your account, and try the above that worked for me.
https://productforums.google.com/forum/#!searchin/websearch/Google$20Now$20says$20%22No$20internet$20connection...%22$20but$20that$27s$20wrong%7Csort:relevance/websearch/5DAJe5-yWf4/w4a6zJjI65IJ
Click to expand...
Click to collapse
Thanks,
I tried a second fake google account and it brought the Google Now wizard right up. So it is some kind of authentication issue or file corruption either in the phone or at google. Though my Nexus 7 works just fine so I doubt it is an issue with the account on google's end. I'll try your recipe and see if that clears it.

Let us know if it works.

jdfrye said:
Let us know if it works.
Click to expand...
Click to collapse
It did. Something about the history was f'd up. Hate to delete it but it will rebuild soon enough. Thanks given.

nlinecomputers said:
It did. Something about the history was f'd up. Hate to delete it but it will rebuild soon enough. Thanks given.
Click to expand...
Click to collapse
Good!!!
I searched all of the internets for a solution and didnt find anything. One time I did a voice google "remind me" and instead of saying this "is not avalible on this device" it said " enable web & app activity" so thats how I came up with the solution. Maybe you didnt have to do all that deleting the history, but I did and thats what worked. Glad it worked for you and a couple of others on the google help forum. Makes me feel like a big wig! LOL.. Thanks for the "thanks"

jdfrye said:
Good!!!
I searched all of the internets for a solution and didnt find anything. One time I did a voice google "remind me" and instead of saying this "is not avalible on this device" it said " enable web & app activity" so thats how I came up with the solution. Maybe you didnt have to do all that deleting the history, but I did and thats what worked. Glad it worked for you and a couple of others on the google help forum. Makes me feel like a big wig! LOL.. Thanks for the "thanks"
Click to expand...
Click to collapse
Yep there is no way to really know if that was a necessary step or it was swatting flies with nuclear weapons. But it got the job done and now I can finally enjoy my new phone. Accidentally washed my Moto X so this has been totally frustrating until now.

the above solution is the only thing that worked for me... htc one m8

"Another thing to try that worked for me is> Google settings in the app drawer>Account History>Turn off Web&App Activity/Device Information/Voice & Audio Activity/ Youtube search History/ Youtube watch History/Google location History> wait five minutes and turn it all back on. "
I am having a dumbazz period. lol. I could not find the above on my Droid Turbo. Google settings in the app drawer is what I can't figure out. This is Greek to me. Please enlighten me. Thank you.

Here's Google settings in my app drawer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

jdfrye said:
Here's Google settings in my app drawer
Click to expand...
Click to collapse
Thank you so much. It makes a lot of sense now.

I had this same problem when I purchased this phone coming from Moto X with 5.0.
Solved this by excluding the cards preferences in google settings.
After excluding this preferences, google now started working.

Unable to click on pop up notifications in hangout and messaging.

Has anyone had issues clicking on pop up notifications from hangouts and messaging? I can only swipe them away. I can no longer click on them and go into the message. Pop up notification for phone calls work fine. I can dismiss or answer them. I want to say I noticed it after flashing Franco r19 but can't say for sure it's related.

biggiestuff said:
Has anyone had issues clicking on pop up notifications from hangouts and messaging? I can only swipe them away. I can no longer click on them and go into the message. Pop up notification for phone calls work fine. I can dismiss or answer them. I want to say I noticed it after flashing Franco r19 but can't say for sure it's related.
Click to expand...
Click to collapse
Never had such issue on stock

biggiestuff said:
Has anyone had issues clicking on pop up notifications from hangouts and messaging? I can only swipe them away. I can no longer click on them and go into the message. Pop up notification for phone calls work fine. I can dismiss or answer them. I want to say I noticed it after flashing Franco r19 but can't say for sure it's related.
Click to expand...
Click to collapse
do you have xposed installed?

biggiestuff said:
Has anyone had issues clicking on pop up notifications from hangouts and messaging? I can only swipe them away. I can no longer click on them and go into the message. Pop up notification for phone calls work fine. I can dismiss or answer them. I want to say I noticed it after flashing Franco r19 but can't say for sure it's related.
Click to expand...
Click to collapse
I think this is one of the inherent notification defects on 5.0. I encountered the same issue - please restart the device and see if this remedies the issue.

kingofkings11 said:
I think this is one of the inherent notification defects on 5.0. I encountered the same issue - please restart the device and see if this remedies the issue.
Click to expand...
Click to collapse
I have to ask, sure you are not just tapping on them once? In LP Stock, you tap once and get the "tap again to open" message lower down the screen.
What ROM you are running in addition to the kernel would be helpful, and I second the recommendation to reboot and retry, you could of course also go to a backup before you installed the new kernel, all things being equal, but the kernel shouldn't have anything to do with this.

kingofkings11 said:
I think this is one of the inherent notification defects on 5.0. I encountered the same issue - please restart the device and see if this remedies the issue.
Click to expand...
Click to collapse
That did it! wow, what is rule #1 of troubleshooting? REBOOT. I guess I tend to forget it when it comes to phones since we rarely ever have to restart.

biggiestuff said:
That did it! wow, what is rule #1 of troubleshooting? REBOOT. I guess I tend to forget it when it comes to phones since we rarely ever have to restart.
Click to expand...
Click to collapse
Glad it worked! Hopefully 5.1 fixes this issue.
Apparently it is caused by two finger swiping a notification see link below
https://code.google.com/p/android/issues/detail?id=79583

biggiestuff said:
That did it! wow, what is rule #1 of troubleshooting? REBOOT. I guess I tend to forget it when it comes to phones since we rarely ever have to restart.
Click to expand...
Click to collapse
99% of problems can be solved by hitting the restart button. This has been universally true since the SNES console.

Me too
I get this problem every now and then after my phone has been on for a few weeks without a reboot. Reboot works every time.

a.gu said:
99% of problems can be solved by hitting the restart button. This has been universally true since the SNES console.
Click to expand...
Click to collapse
Is there actually a "Restart" option for native Lollipop? I know you were being figurative, but having only a "Power off" option when running seems awfully spare compared to what I even had on an old Galaxy S III (plus, bootup on a Nexus 6 is rather long, but that's another point, I guess.)
- ooofest

ooofest said:
Is there actually a "Restart" option for native Lollipop? I know you were being figurative, but having only a "Power off" option when running seems awfully spare compared to what I even had on an old Galaxy S III (plus, bootup on a Nexus 6 is rather long, but that's another point, I guess.)
- ooofest
Click to expand...
Click to collapse
my nexus 6..
(there technically is only power off, but this is android. if anything is needed, then it's added to the rom)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

simms22 said:
my nexus 6..
(there technically is only power off, but this is android. if anything is needed, then it's added to the rom)
Click to expand...
Click to collapse
Sure, though I was wondering if this was somehow hidden in stock Lollipop, because I want to run vanilla for a bit longer - keeping variables down to help with diagnosing any early problems I might find with this new phone.
- ooofest

ooofest said:
Sure, though I was wondering if this was somehow hidden in stock Lollipop, because I want to run vanilla for a bit longer - keeping variables down to help with diagnosing any early problems I might find with this new phone.
- ooofest
Click to expand...
Click to collapse
in vanilla, no. but if you have root on vanilla, it can be done. if you use a terminal emulator, you can use the lines reboot, reboot recovery, reboot bootloader.

simms22 said:
in vanilla, no. but if you have root on vanilla, it can be done. if you use a terminal emulator, you can use the lines reboot, reboot recovery, reboot bootloader.
Click to expand...
Click to collapse
Thanks - do you find that Reboot is akin to a "fast reboot" or is startup more or less the same as going from initial powerup, perhaps?
- ooofest

ooofest said:
Thanks - do you find that Reboot is akin to a "fast reboot" or is startup more or less the same as going from initial powerup, perhaps?
- ooofest
Click to expand...
Click to collapse
its a hard reboot, not a soft reboot. it shuts down completely first, then the google logo, then it boots up. as apposed to a soft reboot, that starts after the google logo.

ooofest said:
Is there actually a "Restart" option for native Lollipop? I know you were being figurative, but having only a "Power off" option when running seems awfully spare compared to what I even had on an old Galaxy S III (plus, bootup on a Nexus 6 is rather long, but that's another point, I guess.)
- ooofest
Click to expand...
Click to collapse
Sorry, I haven't responded for nearly a month, but yes, I meant just turn the phone on and off again.

biggiestuff said:
Has anyone had issues clicking on pop up notifications from hangouts and messaging? I can only swipe them away. I can no longer click on them and go into the message. Pop up notification for phone calls work fine. I can dismiss or answer them. I want to say I noticed it after flashing Franco r19 but can't say for sure it's related.
Click to expand...
Click to collapse
Are you running vanilla, and if so, are you on 5.0.X or 5.1?

brandonjcreek said:
Are you running vanilla, and if so, are you on 5.0.X or 5.1?
Click to expand...
Click to collapse
I just had to reboot but I'm on stock 5.1

biggiestuff said:
I just had to reboot but I'm on stock 5.1
Click to expand...
Click to collapse
Man, that is weird. I've not had this issue at all on mine. Is it happening on all notifications or just messaging related ones? And if so, is it just Hangouts and Messages, or are other messaging clients (Facebook Messenger, Whatsapp, etc) behaving the same way?

brandonjcreek said:
Man, that is weird. I've not had this issue at all on mine. Is it happening on all notifications or just messaging related ones? And if so, is it just Hangouts and Messages, or are other messaging clients (Facebook Messenger, Whatsapp, etc) behaving the same way?
Click to expand...
Click to collapse
Are you having the issue because mine was resolved by a reboot. It was only happening on hangouts messages and texts. I don't have Facebook or what's app

[APP][root] Android Auto 3rd party App Enabler

Since Android Auto 3.0, third party apps have been removed from Android Auto despite having Developer Options and "Unknown Sources" checked.
Some developers have came up with a root workaround to allow these apps to show in the menu.
This workaround is dependent on current AA version to work and has always been implemented by specific apps. Some even had the unlock button in the AAuto interface
This app comes to fix that all.
It will list the currently installed AA third party apps, and will apply the workaround for them.
Instructions:
1. Get AA in developer mode and "Unknown Sources" checked. (details in steps 1-7 in this thread). Start head unit server is not needed in my tests.
2. Open the app, click "Read apps". Check the apps you want to enable in AA.
3. Click "Unlock"
4. Click "Apply".
5. Reboot.
6. Enjoy your apps
The indicator of wheter the Chimera service is enabled or not doesn't still work properly, don't take it as reference. Just click unlock every time you want to apply changes in the list.
The app will be improved whenever I have time.
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Download: https://androidfilehost.com/?fid=1322778262904028904 (updated 15/10 with support to android 5.0 and 6.0)

manudroid19 said:
Since Android Auto 3.0, third party apps have been removed from Android Auto despite having Developer Options and "Unknown Sources" checked.
Some developers have came up with a root workaround to allow these apps to show in the menu.
This workaround is dependent on current AA version to work and has always been implemented by specific apps. Some even had the unlock button in the AAuto interface
This app comes to fix that all.
It will list the currently installed AA third party apps, and will apply the workaround for them.
Instructions:
1. Get AA in developer mode and "Unknown Sources" checked. (details in steps 1-7 in this thread). Start head unit server is not needed in my tests.
2. Open the app, click "Read apps". Check the apps you want to enable in AA.
3. Click "Unlock"
4. Click "Apply".
5. Reboot.
6. Enjoy your apps
The indicator of wheter the Chimera service is enabled or not doesn't still work properly, don't take it as reference. Just click unlock every time you want to apply changes in the list.
The app will be improved whenever I have time.
Screenshot:
Download: https://www.androidfilehost.com/?w=files&flid=283691
Click to expand...
Click to collapse
Wow!!! Great job. Thank you, I will test it right away. Is this still dependent on GPS version?

This looks good, and I think it's exactly what I am looking for.
But I have a slight problem!
I hope this is a relevant place to ask, but please tell me if not.
Suzuki Vitara 2017 (UK) with SLDA 1860
SG8+
Rooted
Google Play Services 12.6.89
(I have disabled automatic/background updates in the hope that I can restrict this from updating as I believe newer versions cause AAMirror to stop working(?))
Android Auto 3.6.583534
AA with AAMirror was working fine, than as is the case with many people, the "AAMirror" Icon/Option disappeared from my car's display.
I looked in various places and tried various things to no avail. First I ended up not being able to connect to my car, then even on my Android, AA stopped working.
It opens, sort of swipes left-right, then just freezes and gives me a notification every 1/4 of a second or so saying "android auto collecting feedback". I can't even get to "About" and change it to developer mode, I just get the big blue arrow.
So today, I reset my phone, reinstalled AAMirror, AA, AAUnlock and now AAuto App Enabler, but AA *still* keeps freezing and giving me this notification.
Hoping someone can help.
Am I right to restrict GPS to 12.6.89?
Is version 3.6.583534 of AA appropriate?
Are these two compatible with each other?
Thanks in advance and let me know if I have missed some detail you need.

datasource said:
Wow!!! Great job. Thank you, I will test it right away. Is this still dependent on GPS version?
Click to expand...
Click to collapse
Works with latest GPS, but if Google changes the way of blocking apps in a new update, it will stop working.
The difference is that other implementations of this method only worked with a specific version of AAuto, while this app will work with any version of AAuto using this method for blocking. This approach was first implemented by AAMirror and AAUnlock's developer.
Credits for him, even though he obfuscated his code and I had to figure out how it was done by my own methods.
Breaders said:
This looks good, and I think it's exactly what I am looking for.
But I have a slight problem!
I hope this is a relevant place to ask, but please tell me if not.
Suzuki Vitara 2017 (UK) with SLDA 1860
SG8+
Rooted
Google Play Services 12.6.89
(I have disabled automatic/background updates in the hope that I can restrict this from updating as I believe newer versions cause AAMirror to stop working(?))
Android Auto 3.6.583534
AA with AAMirror was working fine, than as is the case with many people, the "AAMirror" Icon/Option disappeared from my car's display.
I looked in various places and tried various things to no avail. First I ended up not being able to connect to my car, then even on my Android, AA stopped working.
It opens, sort of swipes left-right, then just freezes and gives me a notification every 1/4 of a second or so saying "android auto collecting feedback". I can't even get to "About" and change it to developer mode, I just get the big blue arrow.
So today, I reset my phone, reinstalled AAMirror, AA, AAUnlock and now AAuto App Enabler, but AA *still* keeps freezing and giving me this notification.
Hoping someone can help.
Am I right to restrict GPS to 12.6.89?
Is version 3.6.583534 of AA appropriate?
Are these two compatible with each other?
Thanks in advance and let me know if I have missed some detail you need.
Click to expand...
Click to collapse
I got problems similar to yours trying to use lastest AAuto with an old GPS, update your GPS.
I have tested my app successfully using last version of AAuto and GPS.

manudroid19 said:
Works with latest GPS, but if Google changes the way of blocking apps in a new update, it will stop working.
The difference is that other implementations of this method only worked with a specific version of AAuto, while this app will work with any version of AAuto using this method for blocking. This approach was first implemented by AAMirror and AAUnlock's developer.
Credits for him, even though he obfuscated his code and I had to figure out how it was done by my own methods.
I got problems similar to yours trying to use lastest AAuto with an old GPS, update your GPS.
I have tested my app successfully using last version of AAuto and GPS.
Click to expand...
Click to collapse
Excellent, will try, thanks.
---------- Post added at 09:16 PM ---------- Previous post was at 08:38 PM ----------
manudroid19 said:
I got problems similar to yours trying to use lastest AAuto with an old GPS, update your GPS.
Click to expand...
Click to collapse
It worked. Thanks once again.
Now I just get an error message saying Google Play Services won't run unless you update Google Play Services! (14.3.62) But no option to update
But that's not your problem, will try and work out what's happening.
---------- Post added at 09:22 PM ---------- Previous post was at 09:16 PM ----------
Breaders said:
Excellent, will try, thanks.
---------- Post added at 09:16 PM ---------- Previous post was at 08:38 PM ----------
It worked. Thanks once again.
Now I just get an error message saying Google Play Services won't run unless you update Google Play Services! (14.3.62) But no option to update
But that's not your problem, will try and work out what's happening.
Click to expand...
Click to collapse
Actually, scrub that. I used "Play Services Info" to go back to the old version and update to the latest.
I feel bad for hogging your thread with my inane waffle, but will leave it up just in case it helps anyone.

Thanks for this app but i have one problem:
The app does not recognize Magisk Root. How can i fix that?
Thanks!

HofaTheRipper said:
Thanks for this app but i have one problem:
The app does not recognize Magisk Root. How can i fix that?
Thanks!
Click to expand...
Click to collapse
I have magisk v17.1 and the app asked for root permission without any problems. Maybe you need to update magisk.

Ok thanks. I was on an custom Magisk 17.2.8 version - reverted back to official 17.1 and it works!

@manudroid19
I have a little of confusion, I have AA unlock and AA mirror sometimes works & sometimes not.. My question is your app replace AA unlock?..Thanks

el_easy said:
@manudroid19
I have a little of confusion, I have AA unlock and AA mirror sometimes works & sometimes not.. My question is your app replace AA unlock?..Thanks
Click to expand...
Click to collapse
It does the same, but applies to any app you have installed, not just AAMirror. And allows you to check which applications are currently enabled. You can keep AAunlock installed if you wish

Hi,
great job, Thank you!
Unfortunately, your app will not install on my HTC ONE M8, Android 6.0, root with SuperSu, TWRP.
Message: App can not be installed
Everything is unlocked and works with all other apps.
I can not install only your AAuto App Enabler.
Do you have any idea?

DarkSide10 said:
Hi,
great job, Thank you!
Unfortunately, your app will not install on my HTC ONE M8, Android 6.0, root with SuperSu, TWRP.
Message: App can not be installed
Everything is unlocked and works with all other apps.
I can not install only your AAuto App Enabler.
Do you have any idea?
Click to expand...
Click to collapse
Similarly. The application is not installed.

DarkSide10 said:
Hi,
great job, Thank you!
Unfortunately, your app will not install on my HTC ONE M8, Android 6.0, root with SuperSu, TWRP.
Message: App can not be installed
Everything is unlocked and works with all other apps.
I can not install only your AAuto App Enabler.
Do you have any idea?
Click to expand...
Click to collapse
alexfocus said:
Similarly. The application is not installed.
Click to expand...
Click to collapse
What? I have just installed it again without any problem. So strange... Can you provide a screenshot?
Maybe is Google Play Protect detecting the app is used to cheat their restrictions?

Google Play Protect is off.
Code:
Can you provide a screenshot?
From XDA:
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!

manudroid19 said:
What? I have just installed it again without any problem. So strange... Can you provide a screenshot?
Maybe is Google Play Protect detecting the app is used to cheat their restrictions?
Click to expand...
Click to collapse
Huawei P9 Plus, Android 6.0, ARM64 HiSilicon Kirin 955 (ARM Cortex-A53)
Magisk-v17.1 GPS-14.3.66, Android Auto-3.6.583534

Hi manudroid19!
Nice Job! While everything works. Let's see what happens in a day or two.
alexfocus said:
Similarly. The application is not installed.
Click to expand...
Click to collapse
Perhaps the reason in the processor architecture (ARM7 or ARM64). I've ARM64 and I haven't any problem.

I have ARM7.

DarkSide10 said:
I have ARM7.
Click to expand...
Click to collapse
I told "perhaps". But some of my friends have arm7 too and haven't any problems with application works ))) 2-3 days testing and I'm will ready make a donation.

Also not installed. Samsung Galaxy Tab 2

Uksus17 said:
I told "perhaps". But some of my friends have arm7 too and haven't any problems with application works ))) 2-3 days testing and I'm will ready make a donation.
Click to expand...
Click to collapse
Everything else works for me(AAMirror + Unlock and many more), but this app does not want
I hope the author still has a good idea to fix this!

Use phone diealer when AA connected

Is it possible to use your phone dialer (using the phone itself) while AA is connected? I have alot of contact shortcuts on my screen for direct dial, but my Mate 20 pro dosnt let me use my phone for making calls while it ist connected to Audi MMI via Android Auto. Like it is blocking the dialer app.
It takes me 1 sek. to make a call when I'm using my phone screen to do this, but when I use cars screen to make a call in AA, it takes ages. And I'm faaaar more distracted from the road then when I'm searching contact on my cars display. So please any advice how to do this?

Did you try to disable "Lock phone while driving" in AA settings?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-N975F using Tapatalk

uhi711 said:
Did you try to disable "Lock phone while driving" in AA settings? View attachment 4958845
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
Yes, it is disabled. Could it be a bug in AA? I have version 5.0.500224.

Spartai said:
Yes, it is disabled. Could it be a bug in AA? I have version 5.0.500224.
Click to expand...
Click to collapse
Latest AA is 5.1.5006, but i don't think this is your problem. I have the same AA version as you, and the setting works on Note 10+. It is probably related to your phone.
Sent from my SM-N975F using Tapatalk
---------- Post added at 07:57 AM ---------- Previous post was at 07:52 AM ----------
Spartai said:
Yes, it is disabled. Could it be a bug in AA? I have version 5.0.500224.
Click to expand...
Click to collapse
You could still try to Enable/Disable the setting. Sometimes it helps.
Sent from my SM-N975F using Tapatalk

uhi711 said:
Latest AA is 5.1.5006, but i don't think this is your problem. I have the same AA version as you, and the setting works on Note 10+. It is probably related to your phone.
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
Hm... I'll try to download google phone (or some other dialer app) and give it a try. It could be a problem in Huaweis dialer app then. Not happy with it anyway. Samsung has the bes dialer app there is, exactly what I need. Tried to find some port for my Mate 20 pro, but no luck...

I don't think your problem is related to your phone dialer, as I understood, you can't reach your phone's screen during driving with AA in service. Are you able to get to other apps during driving? Usually this is forbidden for safety reasons. I'm even astonished that there is such a setting in AA, but probably this is provided for the case when the passenger is using the phone.
Sent from my SM-N975F using Tapatalk

uhi711 said:
I don't think your problem is related to your phone dialer, as I understood, you can't reach your phone's screen during driving with AA in service. Are you able to get to other apps during driving? Usually this is forbidden for safety reasons. I'm even astonished that there is such a setting in AA, but probably this is provided for the case when the passenger is using the phone.
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
Well I tried using Viber to place a call, and it kind of worked (call was placed, but active call wasnt shown on my screen), so I hat to close Viber from (swipe it from recent apps) to end the call. Other thing I tried is google maps and that also doesnt want to open. Just like the dialer.
Screen itself works on the phone, but seems the apps dont. At least those that are also awailable on AA. I'll try your suggestion to en/disable lock phone option.
For me it is far les risky to tape once on my phone for something I need, like copyng a phone number, direkt dial etc., then to try to find a way to do that on my car screen or to disconnect the USB cable each time...

Spartai said:
Well I tried using Viber to place a call, and it kind of worked (call was placed, but active call wasnt shown on my screen), so I hat to close Viber from (swipe it from recent apps) to end the call. Other thing I tried is google maps and that also doesnt want to open. Just like the dialer.
Screen itself works on the phone, but seems the apps dont. At least those that are also awailable on AA. I'll try your suggestion to en/disable lock phone option.
For me it is far les risky to tape once on my phone for something I need, like copyng a phone number, direkt dial etc., then to try to find a way to do that on my car screen or to disconnect the USB cable each time...
Click to expand...
Click to collapse
One more suggestion/question: why don't you try to use voice command to dial numbers? The process is not so fast, especially if there is more than one number defined for each of the contacts you need to call, but it works fine. Just say "Call nnnnn (name of contact as saved in your contacts)". You could make new contacts with only nicknames and one single phone number for all the contacts you need to call during driving, in order to shorten the voice dialing process.
Sent from my SM-N975F using Tapatalk

uhi711 said:
One more suggestion/question: why don't you try to use voice command to dial numbers? The process is not so fast, especially if there is more than one number defined for each of the contacts you need to call, but it works fine. Just say "Call nnnnn (name of contact as saved in your contacts)". You could make new contacts with only nicknames and one single phone number for all the contacts you need to call during driving, in order to shorten the voice dialing process.
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
Problem is that I work alot with foregn customers, so it doesnt recognize a German or Croatian name. Also, when a client calls, they mostly have few numbers in their office so I get alot of calls from new numbers during a day. And that is my problem... Or my office sends me a mail that a customer called and I must call back on that and that number. It is impossible to use anything but the phone screen to do all that.

I see. In that case I think I can't help you further. I hope you'll find a solution finally, but before anything, be safe when driving and keep others on the road safe also.
Sent from my SM-N975F using Tapatalk

uhi711 said:
I see. In that case I think I can't help you further. I hope you'll find a solution finally, but before anything, be safe when driving and keep others on the road safe also.
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
I will, thank you. If I do find a solution, I'll write you...

Spartai said:
I will, thank you. If I do find a solution, I'll write you...
Click to expand...
Click to collapse
I see you again with your "dialer issue" in separate thread here
I have two points:
- testing Google Maps as a app to be run when the phone is connected to Android Auto head unit is not good idea as this app is controlled via Google Services to be locked for AA only then
- your issue with dialer is probably related to Huawei dialer so try to use the Google Dialer. I know you tried with some dialer but remember that it should be patched. You can try to use one of these dialers:
https://forum.xda-developers.com/de...PUgvgMVvWC-46V8_msoKqVAySgQ80-tYxeM#downloads
Hope it helps. Good luck.
Sent from my SM-N960F via Tapatalk

zencooler said:
I see you again with your "dialer issue" in separate thread here
I have two points:
- testing Google Maps as a app to be run when the phone is connected to Android Auto head unit is not good idea as this app is controlled via Google Services to be locked for AA only then
- your issue with dialer is probably related to Huawei dialer so try to use the Google Dialer. I know you tried with some dialer but remember that it should be patched. You can try to use one of these dialers:
https://forum.xda-developers.com/de...PUgvgMVvWC-46V8_msoKqVAySgQ80-tYxeM#downloads
Hope it helps. Good luck.
Sent from my SM-N960F via Tapatalk
Click to expand...
Click to collapse
Yes, I'm looking for an answer since this way it is difficult to do my job. I do a lot from my car and I try to be efficient. I also save addresses in my google maps on the phone when I'm in office, but now I see when maps are in AA you have no option to see "labeled" things. You can search it by name and it will show, but that means I need to keep everything in my head. But when you save "Warehouse B+S Koblenz" and you have many similar names in your head, it isn't easy. Thank you very much for the dialers. Do you perhaps know if it is possible to port Samsungs Dialer to Huawei Mate 20 pro? I receive daily 20+ phonecalls from unknown numbers (clients) and samsungs dialer shows "contact history" when you receive a call (e.g. it shows a preview of a last message from that number or when was the last call made, all while your phone rings). And for me that was helpful since I knew if that number called me yesterday or 30 days ago. Also, Huawei only shows Country from where the number is coming from, Samsung showed a City name. End when I see Berlin or Frankfurt, I know which client it may be. But when I see "Germany" it doesn’t tell me anything

Spartai said:
Yes, I'm looking for an answer since this way it is difficult to do my job. I do a lot from my car and I try to be efficient. I also save addresses in my google maps on the phone when I'm in office, but now I see when maps are in AA you have no option to see "labeled" things. You can search it by name and it will show, but that means I need to keep everything in my head. But when you save "Warehouse B+S Koblenz" and you have many similar names in your head, it isn't easy. Thank you very much for the dialers. Do you perhaps know if it is possible to port Samsungs Dialer to Huawei Mate 20 pro? I receive daily 20+ phonecalls from unknown numbers (clients) and samsungs dialer shows "contact history" when you receive a call (e.g. it shows a preview of a last message from that number or when was the last call made, all while your phone rings). And for me that was helpful since I knew if that number called me yesterday or 30 days ago. Also, Huawei only shows Country from where the number is coming from, Samsung showed a City name. End when I see Berlin or Frankfurt, I know which client it may be. But when I see "Germany" it doesn’t tell me anything
Click to expand...
Click to collapse
Sorry I know nothing about Samsung Dialer port project.
First of all try to overcome first basic obstacle (using phone dialer when the AA is connected). So, try to install the Google Dialer and check if it works for you. If you get the satisfactory result it will be a first step and then you can think about next level
Regards,