They will be able to degoogle Pixels as long as Google keeps the phone open source though there is this negative thing with the Titan M security chip which has a unique ID and it’s like the TPM for desktop computers.
They probably partnered with Motorola to be able to keep the project going as Google starts to lock down Android though I don’t think Motorola will ship any device without Google Services so you’ll have to reinstall a degoogled version of GrapheneOS.
For some reason they don’t want to port GrapheneOS to other devices like LineageOS does claiming that they don’t consider any other device secure enough.
I’d like to see some sources for the allegation that Canonical has ties to the military/spying industries. Everything I’ve been able to find directly contradicts that assertion. The AI summary of results for my search:
Military and Spying Industry Ties
There is no public evidence to suggest that Canonical has any direct ties to military or spying industries. The company’s operations are centered around open-source software and do not indicate involvement in military or espionage activities.
Summary
Canonical’s mission and business model focus on open-source software support, with no documented connections to military or intelligence sectors.
Brax3’s are made in mainland China by a “Chinese company”, right? What is the name of your Chinese OEM?
Motorola Mobility LLC ( Motorola Mobility - Wikipedia ) is one of the largest mobile phone manufacturers in the world, and as such, is a very well-known quantity. Can you say the same for your OEM?
Plamen made clear in another thread that Brax 3 doesn’t presently have the resources to keep working on the Ubuntu Touch port, and said it’s a community port at this point. Somebody who I think is the maintainer of the port of another UT device replied asking how they can help, and said last time they tried, merge requests weren’t being accepted.. there was no reply to this, at least publicly.
The UBports Foundation, which took over maintaining UT when Canonical abandoned it almost ten years ago, does not handle device ports - these are done by the community. I’m not aware of any individual who has taken on this device. To my understanding, unless some individual/group takes this on, or Brax 3 takes it back up, there won’t be further progress.
Many devices that run Ubuntu Touch are largely maintained by one individual, who is by no means working at it all that frequently. But the initial process of getting UT running well on a given device can take some real work, and I’ve never been clear how functional the Brax 3 team got things before stepping away.
So it’s hard to know how much work this would take. Probably not tonnes. But at present so far as I can see, nobody is doing it.
From what I have seen on the news Motorola has announced a partnership with GrapheneOS to produce a new phone that ships with GrapheneOS. Any web search should produce a lot of results. Rumors say sometime in 2027.
Yes, that was announced a couple of months ago. Will be interesting to see what actually transpires/gets released. Will still leave users having to deal with the same problematic aspects of Graphene though…
I’m bringing up a topic that had a closed thread, and was associated with the Operating System: the call volume on the Brax3. The thread said the volume increased/improved upon updating the iodeOS to 6.9 or 7.1. However, one of my Brax3 phones has 7.2 and the second Brax3 phone has 7.3, and the volume on both is still too low to hear it well.
Question 1: How can I get a greater call volume?
Question 2: Another Issue – Why does the Updater on Phone 1 say “No Updates Found” when Phone 2 offers the 7.6 download?
Question 3: Is that 7.6 download going to make any improvement in the call volume?
i’m pretty sure you can overdrive to 150% or so. I was trying to get ring volume louder and realized it was playing in the earpiece instead of on the loudspeaker and had it overdriven but honestly the sound quality only gets worse it’s not a strong point of this handset.
Option A — MediaTek Engineer Mode (no root, try first)
In the dialer, enter ##3646633##. On LineageOS-based ROMs like iodéOS this code is sometimes stripped — if nothing opens, install an “Engineer Mode MTK” / “MobileUncle”-type launcher that opens the activity com.mediatek.engineermode.EngineerMode directly.
Go to Hardware Testing → Audio → Normal Mode (this is the normal-earpiece path; “Headset Mode” is for wired, “LoudSpeaker” for speakerphone).
Set Type = Sph (Sph = speech/earpiece/receiver).
You’ll see per-Level gain values (one per volume step, usually 0–255) and a Max Vol. 0~172 field at the bottom.
Raise the Level value(s) for the top steps, and/or raise Max Vol — that lifts the overall earpiece ceiling.
Change Set and it applies. Bump by ~10–20 at a time, test on a real call, repeat.
Option B — audio mixer path (root required)
The stock earpiece ceiling lives in the audio HAL’s mixer file, typically /vendor/etc/mixer_paths*.xml (MTK: often mixer_paths_mtk.xml). Find the or voice-call earpiece path and increase its gain/ctl value, then reboot (or restart the
audio HAL). This overrides the cap globally. Keep a backup of the file — a bad value can mute or distort call audio.
Thanks. I did 2 manual updates to get the 7.2 versions on the phones originally, and now one phone automatically identifies updates and the other doesn’t. No change on the audio volume.
Thanks Daniel, this is a bit above my pay grade…..sounds like it’d work if I knew what I was doing. I’m not getting anything using the first, simplest step with the dialer. btw - Is that an italic hashtag in front and at end?
Hi, can you help with telling me what the latest iodeOS version is for Brax3, and how to view any official messages that inform us of its availability? I have no problem downloading from github but have a hard time finding the location of files, and learning of what’s available when it is issued. Is there a main topic page for that, that I’m missing? Thanks!