hi, I don’t know why, but I tried talk back, on my fairphone 5, not knowing it, and now, my phone has totally “frozen”. I can’t even draw my diagram to open it…can you help?
Combination to have problem is 4x4 pattern with a pattern which goes down and TalkBack activated without option to use volume buttons
I am in recovery and I am trying to use this command:
adb shell pm disable-user --user 0 app.talkbackfoss
Error is:
/system/bin/sh: pm: inaccessible or not found
Is this even possible? (And yes I have to do it in recovery)
@piero@tcecyk Do you know this? Or someone who might know this?
The problem is a lockscreen pattern of 4x4 in combination with TalkBack. It is not frozen but the devices closes the pattern again and you can try again to unlock again and again. When drawing more than 3 dots, it just crashes
… of in the weeds? I like the positive meaning, but had the waiters situation in mind. Most neutral meaning seems “busy with details”
…, so deep in the weeds that there doesn’t seem any way out, that all is hopeless, and that with each passing moment the weeds get thicker and thicker.
“ran into” was misuse? you’re either (deep) in the weeds or not
‘To turn Talkback on or off, press both volume keys of the device for 3 seconds to turn TalkBack. This functions as a volume key shortcut. Note that it will only work after you have enabled it. To enable the volume key shortcut for TalkBack:’
Not sure if it is activated in this case Edit: I am sure it wasn’t.
My test included change of PIN where I saw a warning about potentially harmful loss of data.
For me, after the restarts, the second image was toggled on by default but the first was disallowed (I think this must be the case) by the change of PIN.
Not that this helps … but … I suppose the logic is that if a user required Accessibility and locked screen that is doable but the phone is then vulnerable to a “stranger”. That stranger should be prevented to change lock screen PIN – idk but maybe even at expense of loss of data by Factory reset (??) … but also I am not sure if this matches your situation.
I totally agree with you. It is a stupid bug and @vega (Telegram group chat) is thinking of formatting the device. It is FP5 with official and locked bootloader. So in recovery using format data would show the wizard again at first boot?
Thanks to you gang (@tcecyk, @aibd) for your help, as usual very helpful and good points to try for solutions. .
Hey, I also just locked my phone testing talkback, anyone understands why adb from recovery does not work and always says inaccessible or not found for pm, settings, etc?
There should be a way to disable talkback from ADB but I just cannot seem to find it…