![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/94b2b808-7c9c-4de0-a35b-966d14ae40fd.png)
Really nice to see improcements being made to local voice control.
I personally haven’t opted for it yet due to the computing reqirements - instead been looking into dedicated offline voice recognition modules, since they use much less power. Downside is that they recognise a mostly predefined set of commands, and are just looking for patterns in speech instead of actually performing voice recognition
Would be interesting to compare the two voice control approaches side by side at some point
Why? Anyone is free to use whatever browser floats their boat 🤷♂️
Do you get the same issues on an older version of Firefox for that device? If yes, proceed with caution - your device’s internal EMMC might be nearing EOL considering how old Android 6 is
They probably just stopped building for Android 6 devices. The SDK and various third party libraries continue to add new features all the time, and unlike Firefox, the majority of devs do not have the time or resources to manually code-in the missing bits to retain compatibility with old versions of Android. As a side effect, these custom implementations may have bugs or issues that go unnoticed due to the shrinking install base.
One of the more noticeable bits that changed is the Share API, which is why Firefox’s one looks so different vs every other app. There are other things like enhanced battery optimization and the storage API, which have changed a lot since Android 6.
IMO your best option is an older version of FF, or install Lineage (etc) on that device and use another browser
Edit: change “age of device” to “shrinking install base”