Opened 5 months ago

Closed 7 days ago

#30607 closed defect (fixed)

Support Tor Running on Android Q

Reported by: sisbell Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: tbb-mobile, ff68-esr-will-have
Cc: gk, sysrqb, n8fr8 Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

There are a number of reports that tor is not starting up on Android Q.

Child Tickets

TicketStatusOwnerSummaryComponent
#30666closedtbb-teamAndroid Q Arm Testing on EmulatorApplications/Tor Browser

Change History (13)

comment:1 Changed 5 months ago by sisbell

One idea is to use JNI and the embedded API.

sysrqb already has some work testing this concept: https://gitweb.torproject.org/user/sysrqb/tor.git/log/?h=testing_26653

API headers
https://gitweb.torproject.org/tor.git/tree/src/feature/api/tor_api.h

We can also evaluate JNA.

comment:2 Changed 5 months ago by sisbell

Tested on Android Q x86 emulator and tor starts up with current code. This may be a problem with Android Q on arm so I'll test that next.

comment:3 Changed 5 months ago by sisbell

I have a Pixel 3a. Google will roll out Android Q Beta for Pixel 3a in June so I'll be able to get this tested on a device next month.

comment:4 Changed 4 months ago by sisbell

I upgraded my Pixel 3a to Android Q beta 4 (released Jun 5). Tor Browser starts fine for me. This could be a device issue or perhaps the latest beta fixed the problem people are seeing.

comment:5 Changed 4 months ago by sisbell

I should clarify, Tor starts and connects fine but I only see a blank page when I try to browse. I'm not sure if this was the issue that was being reported.

I do see a play store review from a Pixel 3a user that says:

"doesnt work with Q beta. goes through a succesful connection with tor, then blqnk screen. no error message saying i am not connected or anything."

I'm trying to collect some logs now. There are some native libraries used within the browser that could also be affected by upgrading to Android Q.

Based on this info, I don't think we need to go down the JNI path just yet.

comment:6 Changed 4 months ago by sisbell

I've gone through more testing on this issue. Nothing specific to this problem shows up in the logcat. We don't have any Tor specific issue, everything is loading and running. The about:tor page is blank on start so I think this is some sort of rendering issue within the gecko view.

I downloaded Firefox 66 for Android and installed on a Android Q device. Firefox 66 does not work. Version 67 works fine, however. So it looks like we will need to wait until we integrate against at least version 67 before we can get Tor Browser working on Android Q.

comment:7 Changed 7 weeks ago by gk

Does 9.0a6 work on Android Q? If so, then we can close this bug.

comment:8 Changed 2 weeks ago by eighthave

Also, FYI, the native TorService work will eliminate this kind of concern entirely since it'll link and run Tor via the officially supported methods, rather than the UNIX daemon hack.

comment:9 Changed 2 weeks ago by gk

Keywords: ff68-esr-will-have added

#32001 is a duplicate.

comment:10 Changed 8 days ago by sisbell

I verified running on Android Q (Android 10) so this can be closed.

comment:11 in reply to:  10 Changed 8 days ago by gk

Replying to sisbell:

I verified running on Android Q (Android 10) so this can be closed.

Thanks. What should we do with the child ticket?

comment:12 Changed 7 days ago by sisbell

I closed it. Android 10 devices have been released and are better for testing.

comment:13 Changed 7 days ago by gk

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.