@RogerZ Thank you for your insight. I was not thinking about other phones being available.
2 Likes
Yes, that’s what I meant.
1 Like
I asked if it was possible to build this, but it would be a fairly large bit of work for our team, so they can’t commit to it. Sorry! We didn’t have a A14 iodéOS build created, and the hardware integration, etc. all happened for our team on the A15 base.
1 Like
Android doesn’t play nice with downgrading. So to “move back to stable” is to just remove the “Updater app” beta update “App Info > 3 dots > Uninstall updates” then just wait around for the next stable update. 6.7 “stable” will be released in a few days.
PS for others: I have been away for about 10 days, and don’t yet have feedback on any progress over the past few weeks on this key wifi issue. I’ll try to get more clarification if there is any progress to report in the next day.
5 Likes
thank you for the reply
1 Like
users like @Ricmar report that they use LunarOS A14 to fix their issues and they can also use Verizon by flashing the IMEI
Can we have that last LunarOS image ?
People have been fatigued and they return their phones, we need a quick solution to gain some time to fix this issue.
2 Likes
@george, just want to point out, my issues were with using BraX3 with Vzn, not wifi connection. My phone has connected with our wifi from the beginning, both on iode and lunar. So I have no knowledge if Lunar would resolve the wifi dilemma.
1 Like
@Ricmar It is said that the problem arose when Lunar became iodé and jumped from Android 14 r67 to Android 15, now I’m still afraid that the problem existed but the user base of the developers was too small and they thought that there was no problem, the developers struggled to find a non-working example device as far as I know, in that case it’s probably a Mediatek binary driver problem, we need even one user who solved that problem by moving back to Lunar.
2 Likes
@george can you please provide more info on this? When did that happen and exactly which “Lunar” are you talking about here?
Here’s a description of “Lunar OMP” from “The Good Phone Foundation”:
https://goodphone.foundation/lunar/
Note the LUNAR logos in the middle of the page. Here’s an example:
Unfortunately none of the “LUNAR” links on that Good Phone Foundation page resolve. However there is this “Supported Projects” page that still works, and lo and behold, we see the Brax2 listed:
https://goodphone.foundation/partners/
https://goodphone.foundation/partners/braxphone/
… So the BraX3 smartphone is assigned FCC ID 2BN26-BRAX3. The parent ID 2BN26 belongs to “Lunar Industries Inc.” apparently Doing Business As “Lunr” (note the lack of “a” in that name) with company headquarters at 4300-800 RUE du Square-Victoria Montréal Québec H4Z1H1 Canada. Here’s a link to their website:
Note their “LUNR” logo, which is exactly the same style (sans the “A”) as the project mentioned over at the Good Phone Foundation:
For grins and giggles, here’s a Case Study from their website that describes a Project very similar to the BraX3 (in very glowing terms of course):
The BraX3 could easily fit this otherwise anonymous description, non? 
So “who is ripping off who” here IP-wise with the change of logo? Or is this a deliberate attempt to obfuscate the supply chain for the BraX3 product?
2 Likes
@PeterBX It has been extensively analyzed by Rob in that video “Is GrapheneOS dying?” that LunarOS was merged into iodéOS, there is not any LunarOS anymore, Brax2 was shipped with LunarOS which was called BraxOS at the time.
2 Likes
… And the bigger question is, who is legally responsible for ensuring that the COMMERCIAL product known as “BraX3 Smartphone” is FIT FOR PURPOSE?
It matters not that the BraX3 ships with a FOSS operating system. There are certainly hundreds if not thousands of commercial products that implement some sort of FOSS solution. And I’d wager that none of the vendors of those products would use “It’s Free as in FOSS” as an excuse to not prioritize resolution of a broken software implementation.
Wi-Fi on the BraX3 is still not working with what is likely the majority of the installed access points around the world. I’m fairly certain that it falls on the vendor Brax Technologies to get this problem fixed in a timely manner. As the seller of the phone they are the ones that could get dragged into court over this. 
So what is Brax Technologies actually doing to fix this problem? IMHO having @rik from “iode team” attempting to play middleman here has not really resulted in any real progress. No offense to you @rik but what is really REALLY needed is a dedicated pinned thread with an actual timeline listing what’s been done so far by Brax and iode to resolve this issue, and what is being planned next, and exactly when. If someone needs to spend money to staff up iode so that they can actually devote uninterrupted effort on this then it would be Brax that needs to do that for their commercial product.
In any case, if indeed both Brax and iode have the full commercial SDK for the MediaTek SOC then there’s absolutely no reason why this problem shouldn’t have been resolved months ago. Someone just needs to put their uninterrupted attention on the problem – and that usually requires money for a commercial project like this.
We the customers of Brax Technologies have already ponied up by purchasing the BraX3 phone. Some of us certainly did that as a measure of support for an organization that is at least attempting to address privacy concerns for the larger population of smartphone users.
It’s time that Brax show the same level of support for their mission and customers by taking a real and visible role in the effort to resolve this issue. Please, no more excuses! 
7 Likes
Thanks @george , let’s hope they can spend as much effort “analyzing” this Wi-Fi issue as they apparently have the “lineage” of LunarOS. So far I’m just not seeing that happen… (at least not in this thread)
In the commercial IT world that I come from, we would have daily “red team” meetings with everything else being put on hold until the issue in question got resolved. Each meeting’s agenda and minutes would be made available to the customer paying for the project. And for any issue that dragged out for months before resolution, surely some heads would roll! 
4 Likes
I dont know where we are with wifi not working on some ap’s
Im reporting that i nstalled another router using wpa2 and this brax phone does connect.
Router is linksys mx4300
1 Like
Update. Installed the new 6.7 update and nothing changed.
1 Like
Just installed the 6.7 release. No Actiontec router connection.
1 Like
I just installed the 6.7 release. Still no connection to my D-Link router.
1 Like
@mike8itall @GromPilot @MichaelA in the iode news there is no reference to the WiFi for this update, it’s a regular update plus some new phones supported
1 Like
@rik WPA3 is the same as WPA2 beyond that it is preceded by a SAE authentication.
What are exactly the LineageOS security synchronizations? Could one of those be the reason for the problem?
Do we have any single example of some router that either suddenly broke or was fixed ?
Is there some kind of WPA3 WiFi USB dongle that can be easily plugged into the router and replace or function simultaneously with the router’s WiFi ?
Powerlines and range expanders are another solution
1 Like
excellent list. thanks
Interesting. The good old FCC violating privacy of the supply chain. It has happened to me using devices designed for different application. Wholesalers may try to get under your OEM’s via MAC address authorizations.