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...
Hi,
I cannot activate the automatic hibernation for Greenify on my Honor 7 because "secure key-guard" is activated.
How can i desactivate it ?
At the same time, i cannot activate the accessibility service of greenify. Each time i activate it, it turns to desactivated. I could activate it for other apps such as Automate but not for Greenify.
Maybe these two problems are related to the same problem.
Can you help me ?
Thanks.
Go to phone manager app. Then click Battery Manager. Click on protected apps. Mark Greenify as a protected app. Now enable accessibility services of greenify... This will fix your problem...
It is possible to keep doze enabled and receive email(gmail) notifications instantly?
Whitelist or PNF enabler
Simply add email app to doze whitelist. phone will be enter to doze except the email app. Enable Auto-sync data.
If these methods didn't work, try Push Notification fixer. it's on Google playstore. But I doubt it might interrupt doze.
I tried these methods and it didn't work on both the op3 and s7
Do you use any 3rd party doze app? Like force doze or naptime xposed? If yes, add email app to those whitelists too.
turn off the doze mode and use the Xposed+Greenify instead
ninechi said:
turn off the doze mode and use the Xposed+Greenify instead
Click to expand...
Click to collapse
In 3.5.x you can not turn off. Only in 3.2.7 there is a option.
In battery settings, click the options button (3 dots), select battery optimization, change not optimized to to all apps, select Gmail and choose do not optimize. It should add it to Doze's whitelist.
So I am trying to save as much battery as possible on my S20Ultra Exynos.
I installed Naptime using ADB and I enabled all these:
Aggressive Doze enabled
Re-apply doze after wakeups enabled
Disable motion detection enabled
Disable aggressive doze when charging enabled
Disable aggressive doze during audio session enabled
Disable Bluetooth on doze enabled
Disable location on doze enabled
Auto Android Battery saver enabled
Disable auto-sync enabled
If I enable these all the time, will my phone stop receiving notifications from Facebook, FB Messenger, Gmail, WhatsApp, chrome sharing to device pages, etc?
Cause I need these to go through during the day.
If that's the case, then maybe it is better to use naptime during the night?
I apologize for all these questions, just trying to understand how Naptime works.
Thank you