Installing a local TalkBack build

122 views
Skip to first unread message

Eitan Isaacson

unread,
Jan 23, 2018, 6:24:24 PM1/23/18
to Eyes-free Programming and development
Hi!

How do you go about testing a local talkback build on a Pixel device?

You aren't alowed to uninstall the "system" version.

Cheers,
 Eitan.

Victor Tsaran

unread,
Jan 24, 2018, 12:46:39 AM1/24/18
to Eyes-free Programming and development
Hi Etan.
If you are installing an open source build, it should co-exist side by side with the prebuilt version that comes as part of the system image. This means that you should see two services called "TalkBack" in Settings > Accessibility.

Hope this helps.
Victor


--
You received this message because you are subscribed to the Google Groups "Eyes-free Programming and development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to eyes-free-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

gary-melconian

unread,
Jan 24, 2018, 2:17:42 AM1/24/18
to eyes-f...@googlegroups.com

Victor wil  open gaps now have the talkback 6.1 in their open gapps packages.that  is what I think is making things not work for us who install custom roms on oreo . 

Eitan Isaacson

unread,
Jan 24, 2018, 12:04:59 PM1/24/18
to Eyes-free Programming and development
I'm getting this error when I try to install a github build:

com.android.builder.testing.api.DeviceException: com.android.ddmlib.InstallException: Failed to finalize session : INSTALL_FAILED_DUPLICATE_PERMISSION: Package com.android.talkback attempting to redeclare permission com.google.android.marvin.talkback.permission.LABELING already owned by com.google.android.marvin.talkback

On Tue, Jan 23, 2018 at 11:17 PM, gary-melconian <gmelco...@gmail.com> wrote:

Victor wil  open gaps now have the talkback 6.1 in their open gapps packages.that  is what I think is making things not work for us who install custom roms on oreo . 

--

Victor Tsaran

unread,
Jan 24, 2018, 1:29:52 PM1/24/18
to Eyes-free Programming and development
Are you building from the command line? I suggest doing that.

Eitan Isaacson

unread,
Jan 24, 2018, 1:52:55 PM1/24/18
to Eyes-free Programming and development
yes.

I'm using the bundled gradlew command, tried all the different tasks (debug, release, aosp, etc).

Victor Tsaran

unread,
Jan 24, 2018, 2:25:41 PM1/24/18
to Eyes-free Programming and development
From your previous message, it looks like your gradle script attempts to compile instrumentation tests? Don't know why.
If I simply try 

./gradlew assembleRelease
or
./gradlew assembleebug

everything works great!

Nolan Darilek

unread,
Jan 24, 2018, 2:49:42 PM1/24/18
to eyes-f...@googlegroups.com

It looks like the failure is in the *installation* step, not the build step. Been a while since I've done this, but assembleDebug just does a build and not an installation, right? If so, that isn't the issue here--at least, not based on my reading.


I'm guessing that, while the open source release does use a different package name, that it tries to define the same permissions that the official release does, and that the package installer doesn't like this. I don't know of an easy fix.

To unsubscribe from this group and stop receiving emails from it, send an email to eyes-free-de...@googlegroups.com.

Victor Tsaran

unread,
Jan 24, 2018, 2:54:20 PM1/24/18
to Eyes-free Programming and development
Let me check. I am sure the "aosp install" task worked for me just fine.
Reply all
Reply to author
Forward
0 new messages