ipat / eyes-free

Automatically exported from code.google.com/p/eyes-free
0 stars 1 forks source link

uninstalling talkback beta disables talkback on Moto X 2014 #426

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.  Go to my apps in the play store and select Google Talkback.
2. Choose uninstall updates.
3. Press the ok button to confirm the uninstall.

What is the expected output? What do you see instead?

I expect talkback to return to the version that was installed on the system 
rom. Instead, talkback goes silent because it has been disabled.

What version of the product are you using? On what operating system?

Talkback 4.0 beta. Android 5.0.

Please provide any additional information below.

Because I'm a totally blind person without sighted help, the only way to 
recover from this bug is to use Android Device Manager to wipe the phone thus 
loosing all data.  I consider this to be a critical bug!

Original issue reported on code.google.com by hittsj...@gmail.com on 25 Jan 2015 at 4:00

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
not able to reproduce on motox and nexus 7

The "disable" button is right next to the "Uninstall Update" button

Accidentally click the disable button may cause this.

In case it does happen, you can always re-enable the app by press the enable 
button 
where disable button located.  You don't have to reset your phone use device 
manager. 

Original comment by jins...@google.com on 3 Feb 2015 at 10:03

GoogleCodeExporter commented 8 years ago
If there is a disable button, then talkback isn't reading it.  I'm
totally blind with no access to sighted help.
How will I get to settings accessibility to enable talkback without
sighted help?

Because you can't reproduce it, will you update the download page on
eyes-free with an apk for Talkback 3.6?  That way, I can return to the
stable version without risking encountering this bug again?  I have
reproduced this bug 2 times so far.  In both cases, resetting my phone
remotely was my only option.

Original comment by hittsj...@gmail.com on 3 Feb 2015 at 10:12