this trick gives you an always on build of talkback for android apps

[Jordan Livesey]

hello everyone, I have finally found a way to keep talkback running on chrome OS when you switch away from an android app or turn off chromevox, things you will need, your chromebook needs to support linux and the develop android apps feature, next you will need the open source version of talkback which can be found on github, and your android subsystem needs to be activated, here are the steps, if you haven't done so, enable linux, go to settings, advanced, developers, then follow the instructions to turn on linux, keep everything at the default as we are only going to use our android subsystem only, once your terminal opens, do a sudo apt update, then do a sudo apt install adb, now when adb finishes installing, you will then want to go back to your settings and if you see the develop android apps option, you are ready to go, click on that and follow the instructions, you will be asked to reboot, on doing so you will see this message, continuing will enable adb debugging and requires a factory reset to disable, you can click continue at this point as you are well and truely finished, now just log in and reopen your linux terminal by searching for it or by navigating to the linux folder and then the terminal app from within it, once you see the full window, type adb and click enter, just like on an android phone, you will be asked if you would like to enable debugging, click yes, or always allow and you are now just about ready to proceed with the final step, now, you should see the build of talkback you obtained in your downloads folder, carefully copy it to your linux files folder and then, switch back to your terminal after you see the complete message and then do adb install talkback*.apk, depending on your device you may see a success message or it might not work at all, if this works now the magic begins, go to your launcher, press enter, then type android preferences, if that comes up then press enter to open android settings then go to accessibility, under installed services you should now see a new one, talkback foss, turn that on and unlike the playstore version of talkback, this will start talking strate away, at this point you can turn chromevox off to avoid having both on, arrow keys and tab should help you navigate but remember, you can always change keyboard mapping at any time now you can install an android launcher and essencially turn your chromebook into a secondary android device, this way you also have access to one of stock androids best apps, the clock app, meaning you can make your chromebook wake you up in the morning, if you have any questions feel free to reply

[mattias jonsson]

if i remember correct

yyou can install apk files without adb

just tturn the device in dev mode

9 okt. 2023 kl. 10:56 skrev Jordan Livesey <jordanl...@gmail.com>:

hello everyone, I have finally found a way to keep talkback running on chrome OS when you switch away from an android app or turn off chromevox, things you will need, your chromebook needs to support linux and the develop android apps feature, next you will need the open source version of talkback which can be found on github, and your android subsystem needs to be activated, here are the steps, if you haven't done so, enable linux, go to settings, advanced, developers, then follow the instructions to turn on linux, keep everything at the default as we are only going to use our android subsystem only, once your terminal opens, do a sudo apt update, then do a sudo apt install adb, now when adb finishes installing, you will then want to go back to your settings and if you see the develop android apps option, you are ready to go, click on that and follow the instructions, you will be asked to reboot, on doing so you will see this message, continuing will enable adb debugging and requires a factory reset to disable, you can click continue at this point as you are well and truely finished, now just log in and reopen your linux terminal by searching for it or by navigating to the linux folder and then the terminal app from within it, once you see the full window, type adb and click enter, just like on an android phone, you will be asked if you would like to enable debugging, click yes, or always allow and you are now just about ready to proceed with the final step, now, you should see the build of talkback you obtained in your downloads folder, carefully copy it to your linux files folder and then, switch back to your terminal after you see the complete message and then do adb install talkback*.apk, depending on your device you may see a success message or it might not work at all, if this works now the magic begins, go to your launcher, press enter, then type android preferences, if that comes up then press enter to open android settings then go to accessibility, under installed services you should now see a new one, talkback foss, turn that on and unlike the playstore version of talkback, this will start talking strate away, at this point you can turn chromevox off to avoid having both on, arrow keys and tab should help you navigate but remember, you can always change keyboard mapping at any time now you can install an android launcher and essencially turn your chromebook into a secondary android device, this way you also have access to one of stock androids best apps, the clock app, meaning you can make your chromebook wake you up in the morning, if you have any questions feel free to reply

--
You received this message because you are subscribed to the Google Groups "ChromeVox Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromevox-disc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chromevox-discuss/CAKbXg6GWOs2vfrPkNEk-1rdit9a_z0sUO5LtyOSkadwAt%2BWeFQ%40mail.gmail.com.

[Jordan Livesey]

while you could use developer mode, its not recommended and means that the chrome OS system can easily be tampered with, by default, chrome OS boots from a read only volume, I like to call them bootable snapshots because they can be reverted to when an update breaks things, if you do unlock the power of developer mode you can ea easily damage the system if you don't know what you are doing, your chromebook may also no longer be covered under warenty any moer

[YMG Snow]

Thanks