1885137 - The Translations feature is not available on some devices

Status: RESOLVED WONTFIX

(Firefox for Android :: Translations, defect, P1)

Description

[Adina Petridean QA [:apetridean]]

Attachment: logs 13.03.2024.txt

Prerequisites

Make sure to toggle the "Enable Firefox Translations" option in the Secret settings.
The system language is different from the language of the accessed webpage.

Steps to reproduce

1. Open the Fenix application.
2. Navigate to a page that can be translated (e.g., elpais.com).
3. Observe the behavior.

Expected behavior

The first translation bottom sheet is displayed.
The translation icon appears in the search bar.
The “Translate page” option is also displayed in the three-dot menu, positioned between “Find in page” and “Desktop site”.

Actual behavior

The Translation feature is not available.

Device information

• Firefox version: 125.0a1 from 13.03.2024
• Android device model and OS: Sony Xperia Z2 (Android 6.0.1)

Any additional information?

Please note this issue is also reproducible on Samsung A13 (Android 12).
On other mobile devices, the feature is available.
This issue is not reproducible on Google Chrome (please check the attached screenshot).

Comment 1

[Adina Petridean QA [:apetridean]]

Attachment: ScreenRecord_2024-03-14-02-28-58.mp4

Comment 2

[Olivia Hall [:olivia]]

Log shows:

2024-03-14 03:26:10.390 755-755 TranslationsMiddleware org.mozilla.fenix I Success requesting engine support.

So, the device architecture was successfully checked.

Need to add logging to see what the resolution was. (If that check resolved to false, then this is expected behavior.)

Comment 3

[Marco Castelluccio [:marco]]

I think it's expected not to work on Sony Xperia Z2, but it should work on Samsung A13 because it is Aarch64.

Comment 4

[Adina Petridean QA [:apetridean]]

Attachment: Chrome.png

Comment 5

[BMO Github Automation]

Attachment: [mozilla-mobile/firefox-android] Bug 1885137 - Added Logging for if the Translation Engine is Supported (#6008)

Comment 6

[BMO Github Automation]

Authored by https://github.com/ohall-m
https://github.com/mozilla-mobile/firefox-android/commit/bbc1bd60c15bb31ba4ae700c386075ed90c98cab
[main] Bug 1885137 - Added Logging for if the Translation Engine is Supported

Comment 7

[Olivia Hall [:olivia]]

When this patch makes it to Nightly, probably tomorrow or later today. Please check the logs for Success requesting engine support. isEngineSupported: false. If engine support is false, then we do not support the device and won't show entry points into the feature. (Please continue to note any devices this happens on for us to have to reference.)

Comment 8

[Marco Castelluccio [:marco]]

(In reply to Marco Castelluccio [:marco] from comment #3)

I think it's expected not to work on Sony Xperia Z2, but it should work on Samsung A13 because it is Aarch64.

While Samsung A13 uses a processor which is capable of Aarch64, we found that its OS architecture is 32 bit.
So the feature is not working on these phones by design.

Comment 9

[Olivia Hall [:olivia]]

Adding more info for future checks, one way to confirm if a device isn't supported is to go to https://webassembly.org/features/ and check the "Your browser" column for "Fixed Width SIMD" and "Relaxed SIMD".

Comment 10

[Mira Lobontiu (Android QA)]

I'll add the Lenovo tablet M10 (Android 10) to this list.
The feature is enabled successfully, but it does not translate any page. It keeps displayind the spinner icon and the "Translate..." option.
After about 5 minutes or so, the translation bottom sheet is dismissed, and the page is not translated.
I have verified on https://webassembly.org/features/ link, and the "Fixed Width SIMD" and "Relaxed SIMD" are checked, so it should work.

I'll attach a logcat, it might help.

Comment 11

[Mira Lobontiu (Android QA)]

Attachment: Lenovo logcat.txt

Comment 12

[Olivia Hall [:olivia]]

Thanks for the logcat for the Lenovo tablet M10! This is likely a different bug because if translations wasn't supported, the device shouldn't have shown the translations feature and it also should not have passed the SIMD test on the web.

Not sure where to go from here for that device, but here are my observations from the logcat for leads or things that stand out:

This is showing up in the logs a lot, seems like from a lot of different callers including system, could just be an Android 10 quirk I don't remember too:

StrictMode: StrictMode policy violation: android.os.strictmode.DiskReadViolation

NetworkManagement: Uid 10126 restricted because of app standby mode

Is also showing up a lot too, but probably expected if the phone is idling. Still seems like a lot in the logs. Could be a USB debugging type log as well? Not really sure here.

Only guess right now is it could be some phone permission issue on reading files, but that is really only a guess based on DiskReadViolation showing up everywhere.

I didn't see any specific translations logs or even many Gecko or Fenix logs. Maybe suppressed under restricted because of app standby mode. I'll keep a lookout for something actionable on this bug.