Opened 7 months ago

Last modified 19 hours ago

#28119 needs_review defect

Provide Tor Browser for Android for arm64-v8a devices

Reported by: gk Owned by: tbb-team
Priority: High Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: tbb-rbm, tbb-mobile, TorBrowserTeam201905R, GeorgKoppen201905
Cc: sisbell, boklm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Supporting all devices Fennec supports means that we need to add support for arm64-v8a devices into tor-browser-build.

Child Tickets

Change History (7)

comment:1 Changed 4 months ago by peredor

hi,
i need to install Tor Browser for Ubuntu on an arm64 architekure.

I couldnt find any linux release for arm64, so i tried to build tor browser on my device (rockpro64, Ubuntu Bionic 18.04.1 arm64).
I used the git clone https://git.torproject.org/builders/tor-browser-build.git but i read in the README make will only produce a version for armv71 and I386/amd64.
i went further anyway executed make [file], i think the output is the following file:
/tor-browser-build/out/debootstrap-image/container-image_ubuntu-base-18.04.1-base-amd64.tar.gz

but what now?
Is it Possible?
Exist already a build?
is it neccesary to install tor browser, tor itself and mozilla is availible in my package repository?

Thanks and greetings
Mark

comment:2 in reply to:  1 ; Changed 4 months ago by cypherpunks2

Replying to peredor:

i need to install Tor Browser for Ubuntu on an arm64 architekure.

You can join #12631 and add rbm descriptors for aarch64.

comment:3 in reply to:  2 Changed 4 months ago by peredor

Replying to cypherpunks2:

Replying to peredor:

i need to install Tor Browser for Ubuntu on an arm64 architekure.

You can join #12631 and add rbm descriptors for aarch64.

Thanks a lot, i found this ticket already in the past but thougt this wouldn't work for me.
buying a modern SBC is how entering a Linux Lesson, you have to learn much :) Try my best

comment:4 Changed 4 months ago by gk

Keywords: TorBrowserTeam201902 GeorgKoppen201902 added
Priority: MediumHigh
Status: newneeds_information

We need to provide 64bit .apks by August this year for Google App Store which is why I gave this a shot. bug_28119 (https://gitweb.torproject.org/user/gk/tor-browser-build.git/log/?h=bug_28119) is the result. It gives me an .apk \o/ There is at least the Orbot piece missing, though, as it seems there is no aarch64 Orbot support yet. sisbell: How much of the Orbot stuff do we care here? I am wondering how much time I should spend fixing this up.

Last edited 4 months ago by gk (previous) (diff)

comment:5 in reply to:  4 ; Changed 3 months ago by sisbell

Replying to gk:

We need to provide 64bit .apks by August this year for Google App Store which is why I gave this a shot. bug_28119 (https://gitweb.torproject.org/user/gk/tor-browser-build.git/log/?h=bug_28119) is the result. It gives me an .apk \o/ There is at least the Orbot piece missing, though, as it seems there is no aarch64 Orbot support yet. sisbell: How much of the Orbot stuff do we care here? I am wondering how much time I should spend fixing this up.

Current Android devices will provide a backwards compatibility for 32 bit versions. What we can't do is mix and match libraries. Once you include one arm64-v8a library, all libraries will need to be compiled for arm64, otherwise a link error will be thrown.

So the Orbot piece would be required:
1) if you include any other arm64 library in the project OR
2) we attempt to upload to Google Play after July of this year

Otherwise it will run just fine on 64 bit devices.

comment:6 in reply to:  5 Changed 3 months ago by gk

Replying to sisbell:

Replying to gk:

We need to provide 64bit .apks by August this year for Google App Store which is why I gave this a shot. bug_28119 (https://gitweb.torproject.org/user/gk/tor-browser-build.git/log/?h=bug_28119) is the result. It gives me an .apk \o/ There is at least the Orbot piece missing, though, as it seems there is no aarch64 Orbot support yet. sisbell: How much of the Orbot stuff do we care here? I am wondering how much time I should spend fixing this up.

Current Android devices will provide a backwards compatibility for 32 bit versions. What we can't do is mix and match libraries. Once you include one arm64-v8a library, all libraries will need to be compiled for arm64, otherwise a link error will be thrown.

So the Orbot piece would be required:
1) if you include any other arm64 library in the project OR
2) we attempt to upload to Google Play after July of this year

Otherwise it will run just fine on 64 bit devices.

Yes. My question was more like, what do we need from the Orbot stuff we ship now after TOPL is used instead because I was wondering how much time I should spend on fixing the Orbot stuff.

Version 0, edited 3 months ago by gk (next)

comment:7 Changed 19 hours ago by gk

Keywords: TorBrowserTeam201905R GeorgKoppen201905 added; TorBrowserTeam201902 GeorgKoppen201902 removed
Status: needs_informationneeds_review
Note: See TracTickets for help on using tickets.