yashsingh1/xdaforums huggingface dataset:
[Android Software Development] rayraycarter4:
Replace this build prop with yours only on nexus 6p running 7.0! I'm using pure nexus rom so don't blame me for bootloops, remember back up your old build prop first and rename this assistbuild.prop to just build.prop

https://drive.google.com/file/d/0BwDqVXfbogaeUzZpY0doX1ZKOHc/view?usp=drivesdk
[Android Software Development] mykenyc:
I had a FEELING that was it, never seen that on any build prop before.
[Android Software Development] rayraycarter4:
Assistant and camera X are both working great
[Android Software Development] rayraycarter4:
So we just need to add the last line for assistant to work?
[Android Software Development] AXelzero1:
It works! Thank you!

---------- Post added at 05:09 AM ---------- Previous post was at 04:55 AM ----------

Exactly. Just add

ro.opa.eligible_device=true

and It'll work with the camera.

---------- Post added at 05:16 AM ---------- Previous post was at 05:09 AM ----------

I can give you the stock 6P buildprop if you want so that people have the option to use it if they don't have Pure Nexus.

Edit: If you have a stock 6p or stock+, backup build.prop, rename assistantbuild.prop to build.prop, and replace your build prop with it.
[Android Software Development] Yasharkhan:
The assistant start up screen shows up but when I say Google now or press the home button, Google now shows up, I've latest Google app, what am I doing wrong? I added that modified build prop line
[Android Software Development] AXelzero1:
Try changing the ro.product.model=YOURPHONE

to ro.product.model=Pixel
[Android Software Development] Yasharkhan:
Yeah it didn't work, what else? BTW I have nexus 6 running 7.0
[Android Software Development] AXelzero1:
Edit: Wipe the google apps's app data and reboot. Go into google settings and there should be new settings.
[Android Software Development] Yasharkhan:
Mine is working now, just gave it some time
[Android Software Development] AXelzero1:
Do you know why the mic icon wont stay inside the google pill? It keeps going back and forth from being there and not being there.
[Android Software Development] Hussainally:
I am a bit confused ..Do i need the new Google app?I can't install it though ,
[Android Software Development] minhas729:
Confirmed working on lgg3 on Android N

Just made these changes

Valvet latest.. made it system app.. permission to rw-r-r

ro.product.model=pixel

ro.opa.eligible_device=true

Rebooted.. cleared data for Google app.. allowed all permissions.. rebooted

---------- Post added at 06:14 AM ---------- Previous post was at 06:12 AM ----------
[Android Software Development] scabbie1980:
It's working on my 6p running SAOSP. I changed these two lines.

ro.product.model=pixel

ro.opa.eligible_device=true

I'm running SAOSP 7.0
[Android Software Development] AXelzero1:
Add the ro.opa.eligible_device=true line to your build.prop file, and change the ro.product.model=Nexus 6P line to ro.product.model=Pixel then reboot.
[Android Software Development] lucasdeeiroz:
I can confirm it is working on Lenovo VIBE K5 Plus with CM14! Thanks!
[Android Software Development] dazeone:
Try editing the build prop yourself. Then wipe Google data and reboot

sent from my Modded Moto G3
[Android Software Development] vignesh95:
did u add that "ro.opa eligible" line?

what phone u have ?
[Android Software Development] Sreekantt:
it always tells me add voice again when i say ok google........and if i make ok google detection on any screen...it crashes
[Android Software Development] Hamid Abolhassani:
After doing this I can no longer use snap chat , please help
[Android Software Development] Syenz:
I have the same issue and I can't seem to find a solution. Does anyone have any idea of what to do to fix it?

I'm using a moto x play and the guy above me was using a moto x pure.

Thanks.
[Android Software Development] DECEiFER:
Believe me, it's not complicated. In-fact, if you leave out the clearing of the Google App's data, it's a step less than the "official" guide.

In more detail, with the correct version of the Google App (I enrolled in the Beta), just edit the build.prop file to remove the "ro.opa.eligible_device=true" line and reboot. I assume you either flashed the ZIPs or manually edited your build.prop, therefore you at least have access to a recovery on your device. You'll have to do the latter for this to work, so to edit the build.prop, you can either use a root explorer on your Android device, or use "adb pull /system/build.prop" inside a recovery (like TWRP 3.0.2.0 in my case) with the system partition mounted to get the file onto your computer. It's quite clear on how to mount the system drive in TWRP so trust me when I say it's not difficult.

Here's a step-by-step to editing build.prop on your computer:

Make sure you have the latest beta of the Google app (6.6.14.21 at the time of writing)

Boot into recovery - TWRP recommended - and mount the system partition (make sure it's not read-only)

On your computer in a Command Prompt or Terminal, go to where you have the adb executable file

Type in: adb pull /system/build.prop

Using your favorite text editor (Notepad++ or Wordpad on Windows - regular Notepad is not recommended due to the fact that it doesn't recognize Unix newline characters and therefore the contents of the file are all bundled onto one line), remove the following line (which was added either by you or by the flashed ZIP): ro.opa.eligible_device=true

Now type in: adb push build.prop /system/build.prop to replace the one on your device with your edited version

Reboot your phone and set up Google Now with your preferred options

Reboot back into recovery and mount the system partition again

Edit the same build.prop you already pulled from your device to include the line (again): ro.opa.eligible_device=true

Push the edited build.prop back to your device using the same push command as stated above

Reboot again and see if it works as hoped

I know there are other ways to edit the build.prop, such as with tweak.prop files, but I'm sure they all require root, and I know that's not to everyone's liking. The above steps are detailed, but easy, and if anyone not comfortable with trying them out, then you really shouldn't be playing around with mods like these in case you end up soft bricking your device, etc., and you'd probably need hands-on help to get things like that fixed.
[Android Software Development] iDorkKnight:
Clearing the Google app "data" and not just the "cache" did the trick for me after editing the build prop. Hope it helps you.
[Android Software Development] banccalif:
I tried your method you explained a few pages back but to no avail. Still no hot word detection, retraining persistent
[Android Software Development] Skeptico:
Has anyone been able to get the camera working with this? Google assistant works fine, but the camera keeps crashing. I'm on a Moto X Play using AOSP 7.0.
[Android Software Development] dadymon53:
OK, finally got it working on my N6, on Pure Nexus 7.0. I used the zip file method and I add XL to Pixel in the build properties. And Boom!
[Android Software Development] DECEiFER:
After messing around with it and getting the retrain prompt every time I said OK Google, I had to reverse the build.prop edits to remove the eligible line and set up Google Now again with my voice model, etc. Then I edited the build.prop again to include the line and it worked, without clearing the Google app data. Clearing it meant having to train the voice model with the Google Assistant active and that wasn't working - ie. the configuration wasn't sticking, hence it asking every time it was invoked by voice. So it seems configuring it as Google Now, not clearing the data, and then activating the Assistant again via the line in the build.prop is the way to go - at least for me on my Nexus 6 (stock NBD90Z and rooted). The steps for doing so are in my most recent post on the previous page.

If ever you need to retrain the model again, subject to this continuing to be a problem, you'd have to revert to Google Now to do so as mentioned. Though I cannot guarantee this will work for everyone, I can say that clearing the app data for me was the issue and not doing so solved it. If you know what you're doing, it costs nothing but 5-10 minutes to try.
[Android Software Development] immich:
Here It Works, just the Ok Google didn't work, I don't know why but when I try to open the "Ok google" detection the google app stop working :/
[Android Software Development] DECEiFER:
When you had Google Now configured before adding the eligible line back, was the hotword working as expected, and is your Google app up-to-date (6.6.14.21 at this time)? Also, did you happen to push/install the HotwordEnrollment.apk file (which I found somewhere in this thread posted by the OP) and installed as instructed into /system/priv-apps/HotwordEnrollment? I did and since it didn't help at all, I removed it before trying the steps. Also try invoking it using the Home button first to see if it works, and then try voice invocation. I'm using stock 7.0 Nougat on a Nexus 6 so I can only truly speak for that situation.
[Android Software Development] malkuu:
Ahh thanks maan now working for me ;)
[Android Software Development] sharathsk:
Teach the assistant to recognize your voice loop!

Hey guys Iam Big fan of XDA developers!

I am running AOSP 7.0 on my Nexus 5

As you can see from the title, there was a small bug which I noticed after the reboot..the issue is, whenever I say "okay google" the same process (teach the assistant to recognize the voice) would start looping..and if I try to manually teach my voice via Google assistant voice settings the google app would crash.. please help me fix this issue..thank you
[Android Software Development] zextek:
After I got Google Assistant working, I tried the camera and I got a pop up saying that it couldn't connect to the camera. What I did to fix this situation was to go into Titanium Backup and wipe the data for the camera. It seems to work fine now.
[Android Software Development] CBMC:
That worked for me. The first time I changed the build.prop I had to clear the data in the app which forced the persistent retrain in assistant. Changed build.prop back, retrained with Google now, edited build.prop. No more persistent asking me to relearn voice. Like you said, on a rooted phone it takes about 10 seconds to edit build.prop(takes longer for the phone to reboot) ,so it really isn't a big deal.
[Android Software Development] DECEiFER:
Thanks for confirming that I'm not losing my mind! For some reason the retrain or persistent settings don't persist with the Google Assistant on our phones at least so this not clearing the app data thing was the only way to fix that - provided that the Assistant would work at all without clearing the app data and re-editing the build.prop, which thankfully it did. If ever you need to retrain or change the settings again, you'd possibly have to revert to Google Now again (provided that the issue doesn't get sorted in a later Google app update).

What phone and firmware/ROM are you using, out of curiosity?
[Android Software Development] CBMC:
Yeah. I probably should of mentioned. Nexus 6, NBD90Z, stock rooted, no encryption.
[Android Software Development] matt1515:
Working good for me including "Ok Google" from any screen only thing if I try and talk a text message out it seems to have a character limit where it will ask again what's the message. If i just say a few words it will work and ask if I'd like to send. Anyone else see this. Nexus 6P latest stock rooted ex kernel
[Android Software Development] DECEiFER:
Rockin' a "Pixel." :)

I have encryption on as standard, just so you're aware. It probably makes no difference considering that this worked the same for both of us.
[Android Software Development] :
works on Nexus 6 stock nougat with ElementalX kernel. thanks.
[Android Software Development] MrMiami81:
Where did you go to clear data in your Google app? I edited the build prop but when I go to settings, apps I only have an option to clear cache in the Google app
[Android Software Development] dazeone:
Manage space and then clear from in there

sent from my Modded Moto G3
[Android Software Development] Mic1604:
It seems this fix didn't work on my XT1064 (Moto G 2014) with Unofficial CyanogenMod 14.
[Android Software Development] :
exactly like that :)
[Android Software Development] MrMiami81:
That did the trick! Thanks! I rebooted and the little assistant voice popped up when I went to set up the Google app. It reminds me of Siri minus the word for word conversation written out on screen. ????
[Android Software Development] lightmastertech:
After trying many "fixes" on here, I'm still stuck with getting the tutorial screen on home long press,and then getting Now on Tap after either skipping or completing tutorial. Running a Nexus 6P with BenzoROM.
[Android Software Development] aankkurr:
Works well on Nexus 6 Stock Android 7.

1. Edit Your Build.Prop File

Start by heading to the /system/ folder from the root directory of your device. From there, long-press the build.prop file, then choose "Open with text editor" or similar from the context menu.

Find a line that starts with ro.product.model=. Delete everything after the = sign, then replace it with "Pixel XL" In the end, this line should read: ro.product.model=Pixel XL

Scroll down to the bottom of the list and add a new line. From here, type the following text: ro.opa.eligible_device=true

2. Reboot & Clear Data on the Google App

Reboot your device

And then to clear Google App Data head to the Apps menu in Settings, then select "Google App" from the list. From here, select "Storage," then tap "Manage Space" on the following screen. Finally, tap the "Clear All Data" button, then you'll be all set to go.

Thank you
[Android Software Development] xhitm3n:
Everything working on LG G3 D855 beanStalk 7.0 Thanks!
[Android Software Development] loader72:
I've got a Oneplus One with unofficial CM14. Edited the build.prop, installed the right app version. Wiped Google data&cache and rebooted a thousand times. Now, long pressing the Home button does nothing, not even NowOnTap appears. In the Google Settings, I can change settings on Google Assistant, but when I try to setup my "Ok Google" voice for every screen, it crashes. Yes, all permissions are granted. What can I do?
[Android Software Development] nikhilbhalwankar:
Ok Google is also working? Me too using moto g 2014 but ok google does not work
[Android Software Development] SimonNWalker:
Hot Word Detection Not Working

I am also having the issue with hot word detection. I'm running the Nexus 6P with Pure Nexus and from what I gather, there is a know issue with hot word detection on these new 7 builds. It's not related to Google Assistance but a more widespread issue. I had issues prior to this getting hot word detection working across all apps and when my device was sleeping.

Regardless of this, I've tried toggling permissions on the Google App and rebooting as this was reported by one user as fixing the issue but he could not remember the order he changed things.

Changing the Build Prop back, retraining, changing build.prop again and rebooting.

Here's what one user said on the Pure Nexus Thread.

Nothing I've done has kept the hot word detection working, but again, I don't think its related to Google Assistant.

If anyone has any other advice or solutions, I'd love to try them :)
[Android Software Development] Drac13l:
Nexus 7 (2013) with Android 7.0v6 AOSP.

I retrained on Google Now, changed build.pro via root explorer than rebooted. I got Google Assistant but everytime I say "Ok Google" it asks to retrain. Actually I can't open "Ok google settings" because its crash app.
[Android Software Development] stuff:
As for the hotword issue, I had that problem since using the leaked Pixel Launcher on my Nexus 6P.
[Android Software Development] PabloCruzIII:
I'm going crazy here... I got it to work perfectly on my N6 using Nutty then tried to update my ROM (data not working on the update) so I reverted. I knew this would effect the build prop so I flashed the assistant zips again. I have not been able to get it to work again since, I've tried clean flashed if the ROM and assistant zips, I've tried editing the BP manually always wiping data, I've tried different combinations of flashing and wiping, retraining all of it. I just don't understand how it worked and now it doesn't. I should have backed up.... but i didn't. I know for a fact it worked in other apps and while the screen was off, I used it for like 10 minutes before stupidly trying to flash my ROM update. Oh and I'm back on the original ROM it worked on 9/25 Nutty.
[Android Software Development] brucewayne10101:
Lol hotword isn't working for me either but a lot of people had that issue so I didn't mention :D
[Android Software Development] DECEiFER:
I forgot to mention in my previous posts in relation to this that I'm using the Pixel launcher as well and it's working just fine now that I didn't clear the Google app data and just set up the voice model, etc., with Google Now.
[Android Software Development] vignesh95:
Is okay Google hotword working on OnePlus 2 cm14

I even tried the method mentioned by [MENTION=4894658]DECEiFER[/MENTION]

But it's not working

I followed the steps below

1) train voice with unEdited build prop

2) edit build prop (ro.product.model=Pixel , ro.opa eligible_device=True)

3) rebooted and tried

But still it's prompts to train the voice

Google app latest beta

My device OnePlus 2 (cm 14 by shreesha)
[Android Software Development] DECEiFER:
Sorry to hear that. Just some things to keep in mind while you keep looking for a fix:

- Make sure Google Now worked with the hotword on any screen/sleeping and that the settings persisted. You can revert your build.prop anytime to check this.

- Make sure you're using the latest beta of the Google app via the Play Store.

- Make sure you're using the Google Now or Pixel launcher or Nova with the hotword setting on to get things set up initially. I'd recommend any of the former two.

Other than that, it's a combination of making sure of the above with either clearing the Google app data or not from Google Now before the Assistant build.prop edit. You've got all the above down and nothing helps, then I guess you'll have to wait and see if a Google App update makes a difference or anyone else in your shoes has a solution.
[Android Software Development] bluetigger68:
This one works flawlessly on a Shamu with stock rooted Shamu!

Gesendet von meinem Nexus 6 mit Tapatalk
[Android Software Development] DECEiFER:
Did you try clearing the Google app data before going back to the unedited build.prop and retraining again from scratch? Not sure if it makes a difference but all variables are worth considering when you're stuck.

---------- Post added at 20:11 ---------- Previous post was at 20:04 ----------

I guess it depends on what phone you have and so far the Nexus 6 is the one this method seems to work with best. Thanks for confirming.
[Android Software Development] bluetigger68:
Just edited my post to make things clearer.

Gesendet von meinem Nexus 6 mit Tapatalk
[Android Software Development] DECEiFER:
Cool. I saw your signature anyway which says it's a Nexus 6.
[Android Software Development] zextek:
I'm running a Nexus 6p, rooted and build NBD90X with the Pixel launcher. Using the ES file manager Root Explorer I edited build.prop to change the model from Pixel XL to Nexus 6p. Then I rebooted and Google Assistant was still there. It stuck around for a few minutes and then gradually it switched back over to Google search. I then edited build.prop again to change the model to Pixel XL. I played with it for a little while and then I edited build.prop once again so the model was Nexus 6p. Using TWRP I wiped cache and Dalvik and then rebooted to system. So at this point I have Google Assistant working and my model number is Nexus 6p. It's been working fine for about a half-hour.

Below are a couple of screenshots.
[Android Software Development] rchtk:
Hotword works fine with alternative desktops. I use Nova Launcher and it works.
[Android Software Development] Nimroko:
hey and first thanks,

my nexus 5 launguage isnt english and I am using sasntosh rom

how can i make only the assistant launguge english? I changed the search launguage and it did not help..

thanks!
[Android Software Development] rchtk:
I think only by changing system language...

Edit: crap. Thanks Deceifer!
[Android Software Development] DECEiFER:
Settings > Google > Search & Now

Then under Google Assistant click Settings at the top and you'll find it in there under an option called Assistant Language.
[Android Software Development] amitks:
I managed to get the Assistant to show up on my Nexus 6 (rooted stock). However, despite clearing Cache, Dalvik, and the app data, every time Assistant starts, it crashes within seconds. I have tried both - the home press and the google now search bar to invoke it. Any suggestions?
[Android Software Development] michel sedgh:
For those who say train Google Now then edit build.prop, I do the same but after reboot I still get Now On Tap.
[Android Software Development] OsniNO:
Working in Moto G 2014 CM14. Has some little bugs
[Android Software Development] Nimroko:
it is saying to change the device launguage..
[Android Software Development] DECEiFER:
Perhaps you can add English US as a secondary preference?

---------- Post added at 20:53 ---------- Previous post was at 20:52 ----------

What phone have you got and maybe try clearing your entire cache?
[Android Software Development] Nimroko:
didnt help
[Android Software Development] michel sedgh:
OnePlus 3. Ok I'll try.
[Android Software Development] rchtk:
It worked for me. I have the device in English and Search in French. But quickly reverted because it's far from perfect..
[Android Software Development] dipstik:
setting ro.opa eligible_device=false, rebooting, setting up always listening, setting ro.opa eligible_device=true, rebooting worked on pure nexus 7.0 on shamu. my problem was the toggle for setting always listening to on while having the assistant would snap back to off if i tried to turn it on. now i have the assistant with always listening on.
[Android Software Development] Tyrany:
I might be wrong but it looks like its easier to get hot word detection on aosp roms instead of cm
[Android Software Development] jonzey231:
This guy right here

I made these changes AND I noticed another line that said Nexus 6P so I changed that too.

So I did the three lines quoted AND

# ro.build.product is obsolete; use ro.product.device

ro.build.product=Pixel

Both assistant and the camera are working!!!!
[Android Software Development] michel sedgh:
I still get Now On Tap after reboot and cleaning my device's cache
[Android Software Development] frankfurts:
Guys finally got it working, I had to flash a custom kernel as I'm stock unrooted so selinux stopped build. Prop changes.

Now I'm getting camera crashes, I notice it says if camera crashes to restore and try new method, what is the new method? Editing Manually or the flashable zip?

Cheers
[Android Software Development] Simonthow:
Installed on Pixel C

Hi i installed it on pixel C and it correctly works apart from being forced into portraits