Earlier today I purchased the galaxy gear watch & ever since I paired my device every time I use my browser it says "page loading" I even went into settings in the accessibilities turned off all audio features turned off talkback & it still talking driving me crazy..
parkstbully277 said:
Earlier today I purchased the galaxy gear watch & ever since I paired my device every time I use my browser it says "page loading" I even went into settings in the accessibilities turned off all audio features turned off talkback & it still talking driving me crazy..
Click to expand...
Click to collapse
I was only able to shut it off by actually shutting the talk back engine using titanium. In titanium go to "freeze apps" and freeze "samsung text-to-speech engine." Of course when you do this, your phone will never be able to talk back. I am sure there are other ways to do it, but this is what I could come up with.
parkstbully277 said:
Earlier today I purchased the galaxy gear watch & ever since I paired my device every time I use my browser it says "page loading" I even went into settings in the accessibilities turned off all audio features turned off talkback & it still talking driving me crazy..
Click to expand...
Click to collapse
Yep, that's really annoying when using the stock browser! For some reason sammy took out the Google TTS options.
Here's the 2 options to avoid the annoying audio feedbakcks:
1, install Google TTS, here's the link: http://forum.xda-developers.com/showthread.php?t=2472959
2. Chrome browser.
sharl1987 said:
I was only able to shut it off by actually shutting the talk back engine using titanium. In titanium go to "freeze apps" and freeze "samsung text-to-speech engine." Of course when you do this, your phone will never be able to talk back. I am sure there are other ways to do it, but this is what I could come up with.
Click to expand...
Click to collapse
If you have titanium backup freeze samsung tts
Talk to speech
Sent from my SM-N900T using Xparent Pink Tapatalk 2
I have the galaxy note 3. .. I can't figure how to turn this feature off... highly annoying!!!!!
This has been happening since the s3. Anytime you have anything under accessibility on, the phone starts talking. Samsung has been notified of this and have yet to fix it.
Sent from Flip's Note 3
page loaded tts talkback issue caused by galaxy gear
parkstbully277 said:
Earlier today I purchased the galaxy gear watch & ever since I paired my device every time I use my browser it says "page loading" I even went into settings in the accessibilities turned off all audio features turned off talkback & it still talking driving me crazy..
Click to expand...
Click to collapse
From my phone I selected Samsung Galaxy Gear on the pull down menu. Then My Apps / Installed Apps / FBQuickview / settings.
Then in Set Accessibility turned off Receive Notifications.
Pity it stuffs up the Facebook notifications on your new watch but it stops that awful voice over TTS , Talkback which plays even if it's turned off.
Potentially related. Tts enabled in stock browser out of box. Changing this from the settings menu did nothing. To disable tts in browser I had to enable the accessibility shortcut via the power key. I noticed that even though talkback was off in settings. the shortcut on the power Key menu showed that it was on. when pressed from this menu,it turns on tts. When pressed again, it turns off tts and then it finally shows in this menu that tts is off. The browser then will not use tts. I then hard reset the device and Verified this procedure a second time. Problem solved with no third party software.
Related
Every incoming call and text speaks out an annoying 'incoming call' or 'incoming message'.
I don't know what she activated on her phone, but I can't shut it off.
It's rooted, de-bloated and still on the stock ROM.
Check to see if you have driving mode enabled. It's under settings > voice input and output > text to speech settings.
Sent from my SGH-T989 using XDA App
Sounds like you have accessibility turned on.
go to settings/accessibility/ and uncheck accessibility.
Driving mode is also another possibility as raquel13 said.
robiatti said:
Sounds like you have accessibility turned on.
go to settings/accessibility/ and uncheck accessibility.
Driving mode is also another possibility as raquel13 said.
Click to expand...
Click to collapse
as they said sounds like driving mode or accessibility settings. if not try resetting to factory settings. that should clear out those options. but id do that as a last resort type thing.
personally i love that feature
i know it annoys the hell out of some people, but is very convenient for me when i'm busy working or driving
so people finds it really cool, and some other will find it really annoying
Thanks!
I kept freezing apps. Thought I had it, but it just wouldn't shut up!
I just had some hands on time with GS2.
I couldn't get into Voice input-output/Text to speech to disable driving mode because it just kept crashing.
I unfroze a few apps and finally solved it. I think unfreezing System Manager did the trick.
Thanks for the help.
So i updated to 4.1.2, and now for some reason Talkback will NOT stay disabled or stay removed. I've tried completely removing the app from my phone, and it will still somehow enable itself after a reboot (show talkback notification). Then, since the app was "removed", I have no way of disabling it unless i reinstall the app, then reboot, then go into "Accessibility" and turn it off... Even then, there are still some features turned on, like TTS and highlighting... I've even tried disabling all TTS apps, like Google TTS, Samsung TTS, and Svox TTS... Talkback will still will turn itself on after a reboot... and YES, Driving Mode is disabled...
Anyone have any advice?
That's impossible. If you remove the application using Rom Toolbox lite and you have root access, it will not come back.
Sent from my SGH-T999 using xda app-developers app
re: disable
dansl said:
So i updated to 4.1.2, and now for some reason Talkback will NOT stay disabled or stay removed. I've tried completely removing the app from my phone, and it will still somehow enable itself after a reboot (show talkback notification). Then, since the app was "removed", I have no way of disabling it unless i reinstall the app, then reboot, then go into "Accessibility" and turn it off... Even then, there are still some features turned on, like TTS and highlighting... I've even tried disabling all TTS apps, like Google TTS, Samsung TTS, and Svox TTS... Talkback will still will turn itself on after a reboot... and YES, Driving Mode is disabled...
Anyone have any advice?
Click to expand...
Click to collapse
Try using titanium backup and FREEZE any apps you do not want to run, once you freeze it you will not even see it
in your app drawer. If you change your mind and want to use the app you can always un-freeze it.
Good Luck!
I've tried both uninstall and freeze... it's almost like talkback is built into the framework... I've tried just about everything possible...
TheLastSidekick said:
That's impossible. If you remove the application using Rom Toolbox lite and you have root access, it will not come back.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I know right? It's not that the application "came back", but somehow it's being enabled even though the app has been removed... it's showing a "Talkback Enabled" notification whenever I reboot my device. Then when I go to "disable" it... I can't... because the app was REMOVED... WTF... so I'm stumped... it's almost like talkback features have been baked into the framework, and are some how being forced on...? If I can't figure out what the problem is, then I guess I'll just have to wipe and start fresh... as much as I dont want to have to do that...
I've tried to Clear Data for Talkback, and Google TTS. I've Frozen and even fully removed both Talkback and Google TTS. Yet every time I reboot, that damn "Talkback is enabled" notification is back... and it wont go away unless i go in and turn it off... Unless Talkback isn't installed, then I have to reinstall Talkback, and THEN I can disable it to remove that notification... really strange...
dansl said:
I know right? It's not that the application "came back", but somehow it's being enabled even though the app has been removed... it's showing a "Talkback Enabled" notification whenever I reboot my device. Then when I go to "disable" it... I can't... because the app was REMOVED... WTF... so I'm stumped... it's almost like talkback features have been baked into the framework, and are some how being forced on...? If I can't figure out what the problem is, then I guess I'll just have to wipe and start fresh... as much as I dont want to have to do that...
I've tried to Clear Data for Talkback, and Google TTS. I've Frozen and even fully removed both Talkback and Google TTS. Yet every time I reboot, that damn "Talkback is enabled" notification is back... and it wont go away unless i go in and turn it off... Unless Talkback isn't installed, then I have to reinstall Talkback, and THEN I can disable it to remove that notification... really strange...
Click to expand...
Click to collapse
Weirdest thing is I did a Rom where I removed all this bloat and have never even ran into talkback. Good luck, sorry I couldn't help you.
Sent from my SGH-T999 using xda app-developers app
re: talkback
dansl said:
I've tried both uninstall and freeze... it's almost like talkback is built into the framework... I've tried just about everything possible...
Click to expand...
Click to collapse
There are some apps like the play store which you CANNOT uninstall completely or delete, yet when you go into
settings>applications you can delete or disable the updates only for the app.
Perhaps like the play store talkback is also one of those apps, if it is try to uninstall the update to talkback
and then use a app like "system app remover" which has options to uninstall system apps and an option to
FREEZE them.
So first uninstall the talkback update in settings>applications and then find it again using system app remover
and instead of trying to uninstall it freeze it using system app remover.
Other than that I have no other ideas.
Good luck!
Sounds like I might just need to wipe my phone to get this fixed... must be something totally wacked out...
OK, so i found the problem... It's another "accessibility" service I was using that was causing strange issues with Talkback. In my case it was "Pebble Watch" app that was the culprit. I disabled the services for that app, and the issue disappeared. Although... I need this app for my Pebble watch to work... so I guess I will just have to deal with "disabling" talkback every time i reboot my device...
I just don't understand how it was STILL enabling Talkback even after completely removing the app from the device... Really strange issue... My guess is that there are still some "Talkback" features built into the Framework... and somehow my "Pebble Watch" app is triggering those features...
dansl said:
OK, so i found the problem... It's another "accessibility" service I was using that was causing strange issues with Talkback. In my case it was "Pebble Watch" app that was the culprit. I disabled the services for that app, and the issue disappeared. Although... I need this app for my Pebble watch to work... so I guess I will just have to deal with "disabling" talkback every time i reboot my device...
I just don't understand how it was STILL enabling Talkback even after completely removing the app from the device... Really strange issue... My guess is that there are still some "Talkback" features built into the Framework... and somehow my "Pebble Watch" app is triggering those features...
Click to expand...
Click to collapse
I have the exact same issue, also did freeze and uninstall Talkback in Titanium backup and that did not help at all! The only other accessibility service I have running is Llama - after disabling it the issue disappeared - just like your with Pebble Watch. And I like Llama a lot so I will also have to kill that notification at every boot. Darn!
EDIT: It turned out in my case disabling the Llama accessibility service does not affect the app features that I use, so I'm good. Pretty annoying though.
How are you guys figuring out which apps are causing these problems.
I hate seeing that stupid icon in the pulldown every time I reboot.
Thanks
reapur said:
How are you guys figuring out which apps are causing these problems.
I hate seeing that stupid icon in the pulldown every time I reboot.
Thanks
Click to expand...
Click to collapse
If you have ANY accessibility service enabled, you will get the persistent notification at boot. Disabling all accessibility services and then re-enabling removes the persistent notification.
I'm pretty sure at this point that Samsung developers are, quite literally, retarded.
Use Titanium Backup and free Google TTS & Samsung TTS.
OR
From App setting disable above applications.
I tried first option and the issue was gone.
Would you happen to be using Pebble app?
As others uninstalling and/or freezing didn't help. Disabling "Tasker-JB" in Accessibility killed it. Left TTS apps alone. Don't know yet if I broke Tasker. Since Llama is also a problem app, maybe it is related to Location. I do Location by sniffing WiFi AP's so maybe I'm okay. Maddening!
schneid said:
As others uninstalling and/or freezing didn't help. Disabling "Tasker-JB" in Accessibility killed it. Left TTS apps alone. Don't know yet if I broke Tasker. Since Llama is also a problem app, maybe it is related to Location. I do Location by sniffing WiFi AP's so maybe I'm okay. Maddening!
Click to expand...
Click to collapse
It doesn't break Tasker, but it will prevent it from reading to you (notifications, for instance).
Aerowinder said:
It doesn't break Tasker, but it will prevent it from reading to you (notifications, for instance).
Click to expand...
Click to collapse
Great news! I don't want it talking to me anyway.
having similar issues with LMT and Watchit for my Sony Smartwatch. I guess it's just a bug from Samsung.
Solution!
This was posted on the Android Central forums in November by Costas Andriotis. I implemented it and it works to get rid of the talkback notification on boot. You have to leave Talkback installed to disable it on shutdown though.
http://forums.androidcentral.com/t-mobile-galaxy-s-iii/279707-talkback-alert-wont-go-away.html#post3215875
I'm using GoLocker, MissedIt! and Tasker, and I need these enabled in accessibility.
Everytime I rebooted, Talkback was also enabled (known Samsung bug).
I solved this with Tasker + Secure Settings + Secure Settings' Helper, by creating 2 profiles:
Device Boot: Event > System > Device Boot
Tasks:
Wait: Task > Wait (10 seconds)
Flash: Alert > Flash ("Starting boot tasks...")
Enable Go Locker: Plugin > Secure Settings (Helper > Accessibility Services > Go Locker: Enabled)
Enable Tasker: Plugin > Secure Settings (Helper > Accessibility Services > Tasker: Enabled)
Enable MissedIt!: Plugin > Secure Settings (Helper > Accessibility Services > MissedIt: Enabled)
Device Shutdown: Event > System > Device Shutdown
Tasks:
Flash: Alert > Flash ("Shutting down")
Disable Talkback: Plugin > Secure Settings (Helper > Accessibility Services > Talkback: Disabled)
Disable Go Locker: Plugin > Secure Settings (Helper > Accessibility Services > Go Locker: Disabled)
Disable Tasker: Plugin > Secure Settings (Helper > Accessibility Services > Tasker: Disabled)
Disable MissedIt!: Plugin > Secure Settings (Helper > Accessibility Services > MissedIt: Disabled)
What this does, is disable all accessibility services when shutting down (because if any is active, Talkback will get re-enabled), and re-enable them (except Talkback) at boot. If you have different or additional services, you must disable them all at shutdown and re-enable them at boot.
If you reboot normally, all will be well. In case you have an abnormal shutdown, just reboot again properly.
This is a serious Samsung bug, because if you use an alternative lock screen you won't see the SIM unlock screen, and you will be effectively left without the possibility of making calls.
Click to expand...
Click to collapse
talkback clear data
My phone is Samsung Core 2. Accidentally i clear data of google talkback. Now my phone is getting hang...
Is anyone else having an issue with Google voice search always listening and not launching on the ok google command? Ive tried to re train several times now, turning off the settings rebooting, and then turning them all back on again, but i still almost always have to manually launch Google search.
What's funny, is both my old galaxy s3 and nexus 7 hear me, and auto launch, but the new note 4 doesn't.
Had anyone seen a fix for this issue anywhere?
Gareee said:
Is anyone else having an issue with Google voice search always listening and not launching on the ok google command? Ive tried to re train several times now, turning off the settings rebooting, and then turning them all back on again, but i still almost always have to manually launch Google search.
What's funny, is both my old galaxy s3 and nexus 7 hear me, and auto launch, but the new note 4 doesn't.
Had anyone seen a fix for this issue anywhere?
Click to expand...
Click to collapse
Are you using a different lockscreen, or no lockscreen?
When I tried AcDisplay and the Microsoft Next lockscreen, OK Google wouldnt work with the phone off. It also wouldnt work if I had lockscreen set to "None"
Also, i think you need to have the Google Text to speech selected for it to work. I recall selecting the Samsung TTS engine once and it didnt work.
crazed_z06 said:
Are you using a different lockscreen, or no lockscreen?
When I tried AcDisplay and the Microsoft Next lockscreen, OK Google wouldnt work with the phone off. It also wouldnt work if I had lockscreen set to "None"
Also, i think you need to have the Google Text to speech selected for it to work. I recall selecting the Samsung TTS engine once and it didnt work.
Click to expand...
Click to collapse
Another note. If you set up for phone to always listen per that other thread regarding Google Search "Ok Google" waking phone from sleep, I found after setting up secure lockscreen unlock using the fingerprint scanner, this option to wake the phone no longer works. Don't know if that is any part of your issue as described or not.
Standard lock screen, no fingerprint lock. I think i corrected it b qith b a suggestion in a post about this at android authority.
They suggested checki n g the samsung svoice settings, and setting it to the opposite of what it was set as. In my case, I had to turn svoice "wakeup on lock" off.
I suspect a conflict between svoice and google voice search.
Ever since the Lollipop upgrade, the only way I can get "Ok Google" recognition to work from all screens is to disable S Voice. But when I do that, I can no longer voice-control the built-in camera app (it tells me I have to enable S Voice).
Is there a way to fix this, or are we now forced to abandon one of these two useful features?
Gary02468 said:
Ever since the Lollipop upgrade, the only way I can get "Ok Google" recognition to work from all screens is to disable S Voice. But when I do that, I can no longer voice-control the built-in camera app (it tells me I have to enable S Voice).
Is there a way to fix this, or are we now forced to abandon one of these two useful features?
Click to expand...
Click to collapse
Are you sure you have that option activated in the camera under settings?
Also, I'm not a s/voice user myself, but I don't have it disabled. I just removed it from being activated from the home button.
Kamau54 said:
Are you sure you have that option activated in the camera under settings?
Click to expand...
Click to collapse
It turns off when I disable S Voice. If I try to turn it back on, it tells me I need to enable S Voice first.
Also, I'm not a s/voice user myself, but I don't have it disabled. I just removed it from being activated from the home button.
Click to expand...
Click to collapse
And does that let you use "Ok Google" recognition from all screens (including the lockscreen)? For me, that option in the Google Now settings is greyed out unless I disable S Voice.
No. Disable Svoice, activate ok google detection. Open your camera app and turn on voice. It will ask to enable Svoice. Enable it. Ok google voice still works on all screens and voice recognition works in the camera app as well.
Exactly correct.
erick161 said:
No. Disable Svoice, activate ok google detection. Open your camera app and turn on voice. It will ask to enable Svoice. Enable it. Ok google voice still works on all screens and voice recognition works in the camera app as well.
Click to expand...
Click to collapse
Works great. Thank you!
Ok Google Fix
This may help those who updated to 5.0.1 on the At&t Note 4. It may work for other note 4's. This applies if you already had Google Now set to work on all screens along with various other settings and now they are greyed out. If you never could get Google Now to work on all screens in 4.4.4 that is a different problem.
1. Disable S Voice, the Samsung voice control. Simply go to apps and disable it.
2. Either Restart your Phone, or Power it Off then turn it back on.
3. Try the settings in Google Now Voice again. The first setting which probably worked before - "From The Google App" should still be able to be toggled on and off.
The Second setting, "From Any Screen" May now work and let you train your voice. A clue is the very bottom of the screen "Train Voice Model" and "Delete Voice Model" should no longer be greyed out.
If the second setting gets you to the next screen now where you say Google Now three times but nothing happens, go to the next the step.
4. Put your Note 4 into safe mode. You will not be looking for any programs that might be blocking Google Now as you might expect. I know what is blocking it, it's S Voice that even though is turned off is still blocking it.
If you do not understand safe mode, or have any reservations doing it, don't. Though I feel it is a safe thing to do, I am not going to give instructions how to do it, you can find it online easily. I take no responsibility if you find how to do it then make a mistake somehow and screw up your phone.
5. Once in safe mode, and staying in safe mode and when the phone has loaded everything it is going to load, go to the Google Now settings again and you should see all settings available now. In the second setting "From Any Screen" toggle it on and when it takes you to the voice training do the three steps of Google Now voice training.
At that point you are done. Remember, there are other settings that may affect the use of Google Now but if you had it working before the Lollipop upgrade those settings should not have changed.
6. Simply restart the Note 4 and Google Now should work from any screen again.
7. You should be able to restart S Voice at this point if you need it, primarily for the camera voice commands. I decided to leave mine disabled since I rarely to never use the camera voice commands. You do not need S Voice to be active to use Google Now.
tampa8 said:
This may help those who updated to 5.0.1 on the At&t Note 4. It may work for other note 4's. This applies if you already had Google Now set to work on all screens along with various other settings and now they are greyed out. If you never could get Google Now to work on all screens in 4.4.4 that is a different problem.
1. Disable S Voice, the Samsung voice control. Simply go to apps and disable it.
2. Either Restart your Phone, or Power it Off then turn it back on.
3. Try the settings in Google Now Voice again. The first setting which probably worked before - "From The Google App" should still be able to be toggled on and off.
The Second setting, "From Any Screen" May now work and let you train your voice. A clue is the very bottom of the screen "Train Voice Model" and "Delete Voice Model" should no longer be greyed out.
If the second setting gets you to the next screen now where you say Google Now three times but nothing happens, go to the next the step.
4. Put your Note 4 into safe mode. You will not be looking for any programs that might be blocking Google Now as you might expect. I know what is blocking it, it's S Voice that even though is turned off is still blocking it.
If you do not understand safe mode, or have any reservations doing it, don't. Though I feel it is a safe thing to do, I am not going to give instructions how to do it, you can find it online easily. I take no responsibility if you find how to do it then make a mistake somehow and screw up your phone.
5. Once in safe mode, and staying in safe mode and when the phone has loaded everything it is going to load, go to the Google Now settings again and you should see all settings available now. In the second setting "From Any Screen" toggle it on and when it takes you to the voice training do the three steps of Google Now voice training.
At that point you are done. Remember, there are other settings that may affect the use of Google Now but if you had it working before the Lollipop upgrade those settings should not have changed.
6. Simply restart the Note 4 and Google Now should work from any screen again.
7. You should be able to restart S Voice at this point if you need it, primarily for the camera voice commands. I decided to leave mine disabled since I rarely to never use the camera voice commands. You do not need S Voice to be active to use Google Now.
Click to expand...
Click to collapse
Used to
Worked at stage 3. Reenabling S Voice rebroke OkGoogle. RE Disabled S Voice. All that's changed is either the screen must be on or it must be plugged in. Like my Note Pro. Used to just need to be on..screen off and all.
That's a change with Lollipop and not a "problem." (now it is screen on or charging) It appears Ok Google no longer works with the screen off by design, at least on the Note 4.
I can keep S Voice on after doing the steps. (Though I have since turned it off) Try doing all the steps and while in safe mode turn off then on the settings. It's possible this makes Ok Google the "default" over S Voice.
So I've been having this weird issue when I connect my Note 20 Ultra to Samsung Dex pad, the "Dance" ringtone starts playing, no apps are open, it's not even a ringtone I've selected for any of my apps, the only to stop it is to turn my phone off and then back on again.
Any ideas?
Cyclops1055 said:
So I've been having this weird issue when I connect my Note 20 Ultra to Samsung Dex pad, the "Dance" ringtone starts playing, no apps are open, it's not even a ringtone I've selected for any of my apps, the only to stop it is to turn my phone off and then back on again.
Any ideas?
Click to expand...
Click to collapse
Try to reset settings!!! and then go to notification settings. There you may find the settings about ringtones!!!
JhonMaxx said:
Try to reset settings!!! and then go to notification settings. There you may find the settings about ringtones!!!
Click to expand...
Click to collapse
I found the issue, it was a setting in the Desktop hub app, "HDMI audio on startup" was enabled, once I turned it off, it stopped happening.
Cyclops1055 said:
I found the issue, it was a setting in the Desktop hub app, "HDMI audio on startup" was enabled, once I turned it off, it stopped happening.
Click to expand...
Click to collapse
That's Great Then :good: