So I have tasker and I use it for a couple things, but one thing in particular is I use it so it turns on my screen for 5 seconds when google voice gets a notification. However, in order to have this enabled, tasker needs to have the "tasker - JB" accessibility option checked. When this is checked, it prompts saying "talkback cannot be enabled while airview is enabled, disable airview to enable talkback". If you go ahead and hit disable it turns on "tasker - JB" and turns off airview (though talkback accessibility is still off).
So I was fine with this for a while until I started using my s-pen. Now when I hover over my emails from my email app (not gmail) it will start reading emails as I hover over them. If I turn airview back on (at this point talkback has NEVER been enabled in the options), it still does the same thing.
In conclusion it seems like the tasker - JB accessibility option is causing talkback to be semi-enabled when hovering the s-pen over. I haven't noticed any other apps talking back besides the stock email app, gmail does not talk back.
Just a funny little quirk..
TalkBack with S-pen in mail app
Had the same issue when I installed an app (WatchIt!) for my SmartWatch which required permission for Accessibility Services. So I disabled TalkBack in the Application Manager, guess what, it defaulted to Google TTS Engine (I noticed a voice change). So, I responded like a war dog, and instantly disabled the same... The d’riod hits back, it defaulted to Samsung TTS (another voice change, this time a female). Finally I had the upper hand when I disabled that too. Now it is working fine.
In more 'formal/serious' terms, disable the following three TTS engines:
Google Text-to-speech Engine
Samsung TTS
TalkBack
Please note that you might have to disable any other too if you have more.
The same thing happens to me and it drives me nuts. I wish I could find a way to fix it.
1. Changing home screen pages from the little "bubbles" at the bottom of the home screen makes it say the number "1" "2" "3"
2. Zooming out on the home screens makes it say "Open home screen paged edit"
3. Selecting one makes it say "Home screen 3 of 5"
4. Opening an app folder makes it say "Folder Open" and then when you close it, "Folder Closed".
5. And of course, the most irritating: Hovering over an email with the pen in the email app makes it read the ENTIRE message out...
I need Tasker to get my notifications, there's got to be a way to disable this stupid thing.
-av
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...
I had a problem with Waze...so I uninstalled and then reinstalled it. When I open it up....it does the normal "Allow Waze to access this device's location?" So I select ALLOW and then I get this "Screen overlay detected" prompt. Says I have to first turn off the screen overlay from Settings> Apps OPEN SETTINGS ....so I hit the open settings and then it goes to the Draw over the other apps "Enabled list" of apps. I then scroll down to waze and it is already set to No...or off. I tap on Waze and then the draw over setting shows the toggle set to off....and also grayed out.
This happens with several apps......I have never had to deal with this "Draw over other apps" setting on any android device I have had yet to date. I had been using the Nexus 6 prior to the G4 and never had this problem with Overlay settings or the draw over apps thing. So I am perplexed at this....is this something that has come about more from Marshmallow?
Any help with getting some of my apps to get past this to start would be very appreciative...thanks!
bump....
Same problem here with a G3
I'm having the exact same issue with Waze on a G3.
I guess you have an app that is using overlays, like Lux Lite or the likes to setup brightness or color. Give that app the permission and your troubles should be over.
Sent from my H815 using Tapatalk
I've got the same problem. But I've set it to allow Twilight permission, and is still doing that endless loop with the greyed-out bit mentioned above.
I got it to work by turning overlay OFF for Twilight.. but then Twilight doesn't work. Why is this app even checking for overlays? Waze gets to be uninstalled for this treason.
So frustrated
I don't use Waze, but this same issue has rendered my G4 a nuisance rather than a useful tool. For example, I cannot add nor edit contacts because my contact list doesn't have permission to access my calendar (which shouldn't matter), but I cannot grant that permission because of screen overlay. I can't add anything to my calendar from my phone because of screen overlay. Custom ringtone... nope. Screen overlay. Essentially anything that involved editing, adding, or deleting of any kind is verboten because of this screen overlay nonsense.
I have tried turning off screen overlay to all apps that will allow me to, but some are grayed out and unable to be changed but they appear to be off. I can't even imagine what app I have installed that would use it so I can target it specifically and uninstall it altogether. Is there a fix for this other than turning it off for all apps? Maybe an app or bit of code that suppresses it?
Thank you in advance.
Recently I've had a problem running certain apps on my Gen 1 Zenwatch. When the app opens I get a message saying "Screen overlay detected...To change this permission you first have to turn off the screen overlay from Settings->Apps. There's a link to "Open Settings" which does nothing when I tap it.
Examples of apps that have this problem are Shazam (after I tap the tick on the "Allow Shazam to record audio?" prompt), and a voice recording app (after a similar prompt). So a common theme might be apps which require access to the mic?
My build number is M1D64F, and my phone is an LG G4 running Marshmallow. I've looked at the app settings on both watch and phone, and can't find anything related to screen overlays. If I open Settings...Permissions...Audio Recorder on the watch the microphone shows as DISABLED. If I tap on it I get the "Screen overlay detected...." message again.
Any ideas for how to fix this?
So far, the best answer I have found is to go to the Settings--> Apps --> Draw Over Screen (or something similar) and UNCHECK all of the boxes. Then launch your App and select the permissions it wants/needs from the dialog box. Then go back and recheck the Apps you'd like to be able to draw over other apps at will. A workaround, for sure, but it does work.
Rick "BlackIce"
The solution was to uninstall the Wear Mini Launcher app. For some reason this was causing the problem. I've since heard that others have noticed this as well (i.e. the problem with Wear Mini Launcher)