Database Develop

[Q] Can you change the "Okay Google Now" phrase?

I think I saw it as something different once in a review but I can't remember. Could I change it to like 'Google' or something else?
Hopefully I'll have my own Moto X soon!

I'd love for this to happen, but afaik it's not something we can change.

stearic said:
I'd love for this to happen, but afaik it's not something we can change.
Click to expand...
Click to collapse
Perhaps when some ROMs start being made? I'd love to say "JARVIS" to call Google Now.

Epsilon707 said:
Perhaps when some ROMs start being made? I'd love to say "JARVIS" to call Google Now.
Click to expand...
Click to collapse
I wanted to say "Computer", a la Star Trek. Maybe not on touchless control, it'd be nuts, having the phone turn itself on I mention the word "computer". But with headset or stuff like that? "Computer. How's the weather like?"

I've gotten it to work just saying 'Okay Google......now' during the training.
Now I can just say 'Okay Google' and it activates. I don't know if this will work with anything else, and at times it activates when I didn't mean for it to, but I like it better than 'Okay Google Now'

I trained mine just by saying "okay Google" I didn't even need to say "now".
I always can activate it by saying "Hey Google"
The only problem with shortening the activation phrase is I noticed it would activate and start listening when I was talking to someone sometimes. It accidentally 'thinks' it hears the phrase when I said nothing near it.
Sent from my XT1058 using xda app-developers app

I want mine to respond to "ok R-2"

jncryer said:
I want mine to respond to "ok R-2"
Click to expand...
Click to collapse
Not" Jarvis" from iron man? You could mount it to your arm and be like Tony Stark lol.
Sent from my XT1058 using xda app-developers app

Xaroc8 said:
Not" Jarvis" from iron man? You could mount it to your arm and be like Tony Stark lol.
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
Lol. Either way, I'd like to think that I look cool using that feature, but in reality I'd look like this:
{
"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"
}

I use "OK google" to record the command, and it works fine, it won't activated when I just easily say "google"

desperadoxzg said:
I use "OK google" to record the command, and it works fine, it won't activated when I just easily say "google"
Click to expand...
Click to collapse
Yeah setting it to "OK Google" worked for me too and seems to recognize it better.

ok google works for me too, since i use this alot, im happier

Got it to recognized k google
Edit k oogle works
Sent on my Moto X

flashallthetime said:
Got it to recognized k google
Edit k oogle works
Sent on my Moto X
Click to expand...
Click to collapse
Step by step, getting it to just "'ey g!".

Was just able to set up touchless controls with the wake phrase "OK moto" I trained it by saying "OK moto.. Google now" with a slight pause between moto and Google... Works pretty well, not as good as "OK Google now" does... But at least I know it can be done
Sent from my XT1058 using XDA Premium 4 mobile app
---------- Post added at 12:00 PM ---------- Previous post was at 11:53 AM ----------
Just retrained as "hey moto" and it works just as good as "OK Google now" but I'll see how it works in the field, but it has no problem picking up the phrase in a noisy room.
Sent from my XT1058 using XDA Premium 4 mobile app

theraffman said:
Was just able to set up touchless controls with the wake phrase "OK moto" I trained it by saying "OK moto.. Google now" with a slight pause between moto and Google... Works pretty well, not as good as "OK Google now" does... But at least I know it can be done
Sent from my XT1058 using XDA Premium 4 mobile app
---------- Post added at 12:00 PM ---------- Previous post was at 11:53 AM ----------
Just retrained as "hey moto" and it works just as good as "OK Google now" but I'll see how it works in the field, but it has no problem picking up the phrase in a noisy room.
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
When I tried things like this I found it always wakes up randomly too much. I think its because the algorithm used to compare must have something to do with the three words and not just what you say during the training. What I'm trying to say is that it now thinks you say ok google now like ok moto or whatever you chose. This seems to make it finicky and wake itself up far too often. Even in class with just a professor talking my phone was waking up a few times.

jayboyyyy said:
When I tried things like this I found it always wakes up randomly too much. I think its because the algorithm used to compare must have something to do with the three words and not just what you say during the training. What I'm trying to say is that it now thinks you say ok google now like ok moto or whatever you chose. This seems to make it finicky and wake itself up far too often. Even in class with just a professor talking my phone was waking up a few times.
Click to expand...
Click to collapse
Undoubtedly. When I trained it for "OK Google now" it almost never randomly woke up during conversation. When I trained it for "OK Google" it would occasionally wake up during random conversation, and with "hey moto" it was waking up quite often... What's funny, is that the only time it ever wakes up randomly is when I'm with one my employees... Even with "hey moto" it would be fine for the most part, but as soon as he gets in my truck and we start talking, sure enough it starts waking up, doesn't really happen with anyone else. Definitely seems as though, the shorter the wake up command, the more prone it is to false positives... Which makes a lot of sense.
The "hey moto" though convenient wasn't ideal for consistent operation... It works great for the first few hours, but then it would take 2 or more tries to get it to recognize the command. Went back to"OK Google" hopefully, in the future, Motorola or developers will tweak this system to add different command phrases, but if not, it still works great if used as intended.
Sent from my XT1058 using XDA Premium 4 mobile app

My problem is that I trained it with the phrase "OK, Google Now," but it seems to start after "OK Google" a large percentage of the time. This messes up the command. When I say "OK Google Now, text Tom hello," it should record "Text Tom hello" and show a card to text contact Tom with the message "Hello." However, often the words showing up in the search will read "Now text Tom hello," and Google does a search rather than executing the command. It is frustrating. I tried just using "OK, Google, text Tom hello," but this fails to activate it. I think I will try retraining it this afternoon to "OK Google."

Paddington said:
My problem is that I trained it with the phrase "OK, Google Now," but it seems to start after "OK Google" a large percentage of the time. This messes up the command. When I say "OK Google Now, text Tom hello," it should record "Text Tom hello" and show a card to text contact Tom with the message "Hello." However, often the words showing up in the search will read "Now text Tom hello," and Google does a search rather than executing the command. It is frustrating. I tried just using "OK, Google, text Tom hello," but this fails to activate it. I think I will try retraining it this afternoon to "OK Google."
Click to expand...
Click to collapse
Yeah i was trying to get my wife to set it up on her Droid Mini, and i noticed this exact problem. "Okay Google" may be the way to go.

I got it to accidently accept bu** s**t, i was playing call of duty black ops and I said bu** s**t and it activated touchless control search, twice
Sent on my Moto X

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] Ok Google Everywhere option gone

I had this option turned on and was using it just a few hours ago. After restarting my phone, OK Google no longer works from anywhere except the Google app and the option in the settings is completely gone. Does anybody have any idea what may have caused the option to go away?

Same issue with me and its annoying.

Same issue here. Thought I was going crazy.

Same here, but I just bought it 12 hours ago. Been trying to make it work since.

don't have an s6 but read that the samsung push update removed it,delete the update and it should come back

Macklessdaddy said:
don't have an s6 but read that the samsung push update removed it,delete the update and it should come back
Click to expand...
Click to collapse
I can confirm that not the case. I have the push update and my okay Google functionality is fine.

0dBu said:
I can confirm that not the case. I have the push update and my okay Google functionality is fine.
Click to expand...
Click to collapse
Yes but can you use "ok google" from any screen?

Mine is gone, too. Very frustrating.

glensta said:
Yes but can you use "ok google" from any screen?
Click to expand...
Click to collapse
Yes, and I even have trusted voices as well, just noticed that.
{
"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"
}

0dBu said:
Yes, and I even have trusted voices as well, just noticed that. View attachment 3269958
Click to expand...
Click to collapse
Nice your lucky. This is what mine looks like. Are you on the latest build also? See my attachments. Or maybe like someone said earlier the latest Samsung update cancelled my okay Google functionality. Who knows, wish I had it though.

Latest build, latest Samsung Push update, latest Google Search, latest everything.

penner42 said:
Mine is gone, too. Very frustrating.
Click to expand...
Click to collapse
Whoops, just realized this is in the T-Mobile forum. I've got an AT&T Edge, same problem.

I found a work around with using the Nova Launcher. There is an okay Google option as you'll see with the attachment that works for me on any screen that I'm on. You have to have the premium version I think not sure about that but anyways for what it's worth

I believe it may have something to do with new Google play services that was just pushed. Option was enabled, but, when updated GPS to 7.3.28, function stopped and option disappeared.

Same here
Since Friday evening I've been going through every single setting on my S6 Edge. I had the phone since April 4th, where I had ok google everywhere, but not "trusted voice" in the Smart Lock settings. I restored my phone 2 times now, thinking the first restore got rid of Ok Google Everywhere. I now see others are having the same issue which is great!

I don't know if this has anything to do with it but check the version of Google Play Services. Last week Android Police posted an article about 7.3.27 and I saw their caution that you need to make sure you grab the right version for your device -- http://www.androidpolice.com/2015/0...d-wear-notification-dismissible-apk-download/ details how to decipher the salient version into. On my stock S6, I have -440 so I didn't update. Now, today, I see I've got 7.3.28 (1863718-440) -- It seems the 440 is an important part. So, I'm more current than the version in the Android Police article I cited and I have Trusted Voice and OK Google everywhere.

short/y said:
I don't know if this has anything to do with it but check the version of Google Play Services. Last week Android Police posted an article about 7.3.27 and I saw their caution that you need to make sure you grab the right version for your device -- details how to decipher the salient version into. On my stock S6, I have -440 so I didn't update. Now, today, I see I've got 7.3.28 (1863718-440) -- It seems the 440 is an important part. So, I'm more current than the version in the Android Police article I cited and I have Trusted Voice and OK Google everywhere.
Click to expand...
Click to collapse
I just downloaded 7.3.28 (-440) and still do not have access to Ok Google Everywhere, also Trust Voice is still "off" no matter what.

another setting also vanished.
Lost OK Google from any screen yesterday. Checked settings and the only option is "From Google App". No any screen and no Trusted voice settings. ALSO noticed another setting that vanished. In phone settings the option to "turn off screen during calls" is gone. Now during phone calls my screen turns off, which I really don't want and I can't find a setting to uncheck it.

voice your disapproval: @S6NoOKGoogle https://twitter.com/S6NoOKGoogle

It is now fixed!!!!! simply go to the play store, or your application manager, uninstall updates and reinstall.

Dialer codes not working

I have an unbranded (unlocked) Note 8 straight from Samsung. None of the dialer/hidden codes work. Any idea how to enable them?

What have you tried? I have the same and they work. There's no setting to enable/disable

I don't know what to try to be honest. They just don't work. I've tried the usual ones *#1234#, *#*#4636#*#* etc. None work, the phone just does nothing.

You can use a shortcuts app to do the hidden codes. A bunch of them work. I accidentally enabled some stupid on-screen display thing so when I do power off it displays some messages that tell me it is sending a shutdown command. Now I can't remember which one it was to turn that thing off....

Kalm_Traveler said:
You can use a shortcuts app to do the hidden codes. A bunch of them work. I accidentally enabled some stupid on-screen display thing so when I do power off it displays some messages that tell me it is sending a shutdown command. Now I can't remember which one it was to turn that thing off....
Click to expand...
Click to collapse
I believe you want *#9900# then scroll down to the shutdown option

me2151 said:
I believe you want *#9900# then scroll down to the shutdown option
Click to expand...
Click to collapse
That has a similar setting, this time the culprit was me changing the build.prop to say my device type was userdebug instead of just user. Changed it back and voila, no more shutdown text!

Still not working for me. I even did a factory reset and tried the dialer codes before even inserting a SIM card (thought Verizon provisioning played a trick on my unbranded N8). Any idea why they aren't working?

What are these codes for, again?

roaduardo said:
What are these codes for, again?
Click to expand...
Click to collapse
hidden menus for adjusting or testing various settings, as far as i can tell.

These work (unlocked note 8)
*#011# service mode
*#9090# diagnostic information
*#0*# hardware diagnostic
*#7353# quick test menu
This is not exhaustive, just me trying stuff out.

SteelPicori said:
These work (unlocked note 8)
*#011# service mode
*#9090# diagnostic information
*#0*# hardware diagnostic
*#7353# quick test menu
This is not exhaustive, just me trying stuff out.
Click to expand...
Click to collapse
Yeah.... none of these work for me. None at all. I'm kinda fed up with all the small nagging issues. The phone is going back to Sammy. I'll just go get one from Verizon store.

odesskiy said:
Yeah.... none of these work for me. None at all. I'm kinda fed up with all the small nagging issues. The phone is going back to Sammy. I'll just go get one from Verizon store.
Click to expand...
Click to collapse
Got a Verizon branded phone. These do not work str8 from vzw either. But vzw phones are unlocked either way. Verizon has disabled the ability to enter in codes from dialer.
Sent from my SM-N950U using XDA-Developers Legacy app

LpSk8r said:
Got a Verizon branded phone. These do not work str8 from vzw either. But vzw phones are unlocked either way. Verizon has disabled the ability to enter in codes from dialer.
Sent from my SM-N950U using XDA-Developers Legacy app
Click to expand...
Click to collapse
This is exactly why I as well as others are questioning why there aren't carrier specific forums for the Note 8 as there have been for every other note. There is too much confusion when we're all on the same forum to solve these problems. You have people posting how to do this or that but it doesn't work for every model/carrier.
You have to go to
/efs/carrier/HiddenMenu
And change the setting from off to on... but root is needed.

jellyhead said:
This is exactly why I as well done others are questioning why there aren't carrier specific forums for the Note 8 as there have been for ever other note. There is to much confusion when we're all on the same forum try to solve these problems. You have people posting how to do this or that but it doesn't work for every model/carrier.
You have to go to
/efs/carrier/HiddenMenu
And change the setting from off to on... but root is needed.
Click to expand...
Click to collapse
Didn't OP specifically state he has unlocked, unbranded phone?

pete4k said:
Didn't OP specifically state he has unlocked, unbranded phone?
Click to expand...
Click to collapse
I sure did.

I have an OEM unlocked unbranded 950f and can't use dialer or phone info *samsung* app to launch codes. I tried efs/carrier and it doesn't exist.
{
"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"
}

(Almost) No secret/dialer codes
When I try to use the phone info app to use secret codes I get a whole bunch of errors and can't access any of the secret codes any help would be appreciated

Try entering them manually in dialer. *#77467# takes me to ims settings. On Tmobile. Other carriers lock theres so root is needed.

Genesis730 said:
What have you tried? I have the same and they work. There's no setting to enable/disable
Click to expand...
Click to collapse
N950FXXS5CRJ1
flash this firmware 1000000% will work:good:

This is a struggle ive been working with since switching to Vzw. I did the same thing. I started the phone without a SIM and the dialer codes work. Once I put the SIM in, the phone said it needed to restart to apply carrier settings. Once it restarted, the dialer codes no longer worked. Samsung must have special coding to lock this down once a Vzw SIM is inserted.

Google Keyboard and Censoring Bad Language

Google Voice Typing and Censorship of my potty mouth.. So I have all of the settings configured to not block offensive language on both the Google keyboard settings and the Google voice typing settings within language and input on my Pixel 4. Is there a setting I'm missing because every time I say a curse word I still get the crazy asterisks

Note 10 plus too lol can't stop it , shows bad words in voice assistant tho

shftn2gear97 said:
Google Voice Typing and Censorship of my potty mouth.. So I have all of the settings configured to not block offensive language on both the Google keyboard settings and the Google voice typing settings within language and input on my Pixel 4. Is there a setting I'm missing because every time I say a curse word I still get the crazy asterisks
Click to expand...
Click to collapse
Did you disable it in the text correction sections of the Gboard app? I had to re enable it and disable it to get it to work.

I'm cursing just fine here. [emoji23]
Sent from my Pixel 4 XL using Tapatalk

Omg this is happening to me now too. For years I've had no problem and now it's censoring my curse words. I disabled options that block curse words in both texting and voice text through Gboard but it still replaces curse words with ***
Since changing the options do not give a different result my assumption is this is somehow server side with Google

Oddly enough as you get older you tend to like cursing less and less, at least as a crutch instead of actually having a vocabulary. Still sometimes nothing quite works as well as a proper curse; an interesting tidbit is that the one that starts with F is the word most taken from the English language and used by others in their language with OK as a distant number 2. All that being said I'd try adding them to the dictionary, this got it working for me although it's kind of a work around. Not that I curse. Ok, maybe a little here and there...

1dopewrx05 said:
Omg this is happening to me now too. For years I've had no problem and now it's censoring my curse words. I disabled options that block curse words in both texting and voice text through Gboard but it still replaces curse words with ***
Since changing the options do not give a different result my assumption is this is somehow server side with Google
Click to expand...
Click to collapse
I'm still not being blocked it's gotta be a phone setting... Did you disable it through the Google app as well?

odd, never thought this block offensive words was mainly for voice typing, but now that I tried it, it's f****** censoring my s*** too! this f****** sucks!! definitely has to be a bug unless Google's gotten soft like people these days

dimm0k said:
odd, never thought this block offensive words was mainly for voice typing, but now that I tried it, it's f****** censoring my s*** too! this f****** sucks!! definitely has to be a bug unless Google's gotten soft like people these days
Click to expand...
Click to collapse
Clear your app data and try again. I would post a screenshot or video recording of all the curses I was just able to do perfectly fine but I don't want to get in trouble on the forums. [emoji23]
Sent from my Pixel 4 XL using Tapatalk

EeZeEpEe said:
Clear your app data and try again. I would post a screenshot or video recording of all the curses I was just able to do perfectly fine but I don't want to get in trouble on the forums. [emoji23]
Click to expand...
Click to collapse
Cleared app data completely and set it up from scratch and it's still censoring. It's really annoying and inconvenient but also I'm glad this is the only problem I've had with my pixel. Some people have had much bigger and worse issues. I hope whatever it is does get sorted soon.

You have to disable it in the Google App under voice and then under Gboard as well. Under Gboard it's under text correction, unselect Block offensive words and it works now.

1dopewrx05 said:
Cleared app data completely and set it up from scratch and it's still censoring. It's really annoying and inconvenient but also I'm glad this is the only problem I've had with my pixel. Some people have had much bigger and worse issues. I hope whatever it is does get sorted soon.
Click to expand...
Click to collapse
And you definitely have this option off?
{
"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 Pixel 4 XL using Tapatalk

EeZeEpEe said:
And you definitely have this option off?
Click to expand...
Click to collapse
Yup have both ticked to the off position. Also, I was saying earlier how I've had this phone for months and it worked without problems for the majority of my ownership of the phone and I haven't changed any Gboard options since setting the phone up but it just all of a sudden one day decided it was going to start censoring everything. Annoying AF

I had it randomly start doing this. Toggling the censorship on and back off didn't work. Clearing data for gboard and setting everything up again did fix it. Back to freedom of speech.

1dopewrx05 said:
Yup have both ticked to the off position. Also, I was saying earlier how I've had this phone for months and it worked without problems for the majority of my ownership of the phone and I haven't changed any Gboard options since setting the phone up but it just all of a sudden one day decided it was going to start censoring everything. Annoying AF
Click to expand...
Click to collapse
Mine started doing this today... smh
The fix is to disable Faster Voice Typing
https://www.reddit.com/r/GooglePixe..._medium=Search&utm_name=Bing&utm_content=PSR1

shftn2gear97 said:
Google Voice Typing and Censorship of my potty mouth.. So I have all of the settings configured to not block offensive language on both the Google keyboard settings and the Google voice typing settings within language and input on my Pixel 4. Is there a setting I'm missing because every time I say a curse word I still get the crazy asterisks
Click to expand...
Click to collapse
I am not going to read all of the threads in here, but the culprit seems to be Faster Voice Typing. Turn it off and things should be ****ing wonderful for you again. Seems to have started around April 20, 2020. Again, make sure you have "Block Pottymouth Words" disabled, and I think there are like three places you'll need to check.