Did anyone ever respond and help her? I’m behind here but I haven’t seen it yet.
1 Like
@plamen Any news yet? Or can you say anything about the progress or why it’s taking longer than you predicted? We’re about a week and a half beyond your prediction so it would be nice to hear something.
2 Likes
Works with Firewalla Gold Pro and/or Nokia Novos provided modem/fiber 5GB up and down.
Using the most recent Brax3 iODE OS version 6.7-20250830-brax3. Some apps don’t work, some fail after updates, but you can go back to the older version that works.
1 Like
At the risk of sounding negative, this whole situation sucks. I’m not technically oriented, nor do I think I should have to be. I paid my money and the dang thing should work out of the box. And no way did you ship this many devices to your customers without knowing there were significant wifi issues from the get-go. So there! Now fix it.
2 Likes
Brax3 iodéOS 6.7
Router: Mikrotik RB962UiGS-5HacT2HnT (RouteOS 7.19.6)
Authentication Types: WPA2-PSK
Unicast Ciphers: aes ccm
Group Ciphers: aes ccm
2.4/5GHz = Saved/Check Password and try again.
Unfortunately, it’s not working 
2 Likes
The devs are still working on a fix. We’ve already eliminated the possibility of a hardware design flaw, as the device connects without an issue when running LunarOS (closer to stock BSP version).
We’ve engaged developers from our team, as well as lineage developers to help iode with a fix.
Hoping for a resolution soon.
3 Likes
Indeed the situation sucks. We caught a wifi issue during beta testing (we had about 25 beta users testing/using the phone for close to 2 months), but we identified only a bug that affects affects ddwrt routers or wpa3 protocol. The wpa3 was fixed shortly after shipping.
We’ve identified the WPA2 issue later than we hoped we would. iode team was trying their best but obviously it wasn’t good enough to resolve the issue promptly. We’re hoping that with the new external resources we’re engaging, we will be able to get this thing fixed.
5 Likes
Thanks for the update. Honestly though, it doesn’t sound much different than what we heard almost 2 weeks ago so it still seems like things are moving at a snail’s pace.
1 Like
That is not fair! How about a tortoise instead. A tortoise will continue to a fixed goal and will arrive in one piece. A healthy tortoise ready for battle. A snail only crawls at night since a bird or other prey will snatch it during the day. No more snail. https://www.youtube.com/shorts/2aakuRMQt8Y
1 Like
Installing 6.8-20250921-brax3 did not fix the WiFi problem with my Mikrotik router.
If you want it to run with your Mikrotik router, you need to have a routerOS 17.4.+ that enable WPA3. All WPA2 implementations I have tested, failed (and I have around 10 different mikrotik devices here).
1 Like
Thank you.
Alas, when I travel I have no idea what router the location is going to have.
Forcing my own router to a specific version doesn’t really help solve the broken WiFi stack on the Brax3.
I had not seen any other reports on 6.8 so thought I should report it (I do see one now that I search for 6.8 from four days ago, that I missed while trying to keep up with the messages).
3 Likes
heya all.. i just start to set up the brax phone but having the same issue not being able to connect with our Asus RT-Ac68U.. we have tried so many things.. it keeps on looping on putting the password.. and reading through all this above just makes my head spin and not understanding if there is a solution or not in the end ? thank so much
1 Like
what do you mean with new external recsources..? does this mean we cant use the phone we need to buy other things for it to work ? i am like roger.. i am not technically oriented and i get really confused with all this .thnx
1 Like
@annieie the options are to buy a new router known to work, set up your router to allow no password (not good security-wise), or wait for them to fix the issue. They keep saying they’re close to a fix but seems like they define “close” differently than most people do.
2 Likes
WPA3 cannot be activated on the hAP ac (In my case, RB962UiGS) after upgrading to RouterOS 7.x because this model does not support the wifiwave2 package, which is required for WPA3. WPA3 is only available on devices with newer chipsets (e.g., hAP ax², Audience, cAP ax) and with RouterOS 7.x, where the wifi-qcom-ac or wifi-qcom package can be used.
RB962UiGS uses an older wireless chipset (802.11ac Wave 1), which RouterOS 7 supports only through the classic wireless package.
WPA3 is implemented only in wifiwave2 (RouterOS 7.1+) and newer Wi-Fi packages that require Wave 2 or AX hardware.
I have a Mikrotik hAP ax2 (C52iG) where WPA3 is enabled and Brax3 works well.
A possible solution would be to switch to OpenWRT (OpenWRT uses mac80211 + hostapd, which support WPA3 since version 19.07).
3 Likes
Just updated my Brax3 to IodéOS 6.8, but no change… Issue still there. Let’s hope a fix with 6.9…
3 Likes
Sagem S018CAM1200150, WPA2, Iodé 6.8, Wingman106
1 Like
Hi @rik @plamen ,
whatever issue you might have with me. Since I’m on the beta team and I was the first to report the issue, you could have at least included my models in your charts and my name, don’t you think?
Those models being referenced in my several adb logs I pulled for your team specifically.
So you can add the models I previously mentioned That would be nice. To remind you, the ddwrt version of the consumer models of the router I was mentionning in the Beta.
Just received the end user unit for my friend, at the Mil Base of my deployment and as I can see wifi is not working with 6.8. That being also the case with Juniper AP, enterprise radius and Fortinet AP, enterprise radius. In wpa3 of course.
On a side note, nice to see that for a problem reported in 04/2025, we are in 10/2025 and still no solution and as predicted more and more people are impacted. So agreeing with @PeterBX on what he said. Especially since I had every tech info handed to you for that purpose and you apparently refused the help and pointers I was providing. @george so no eveyrhting was handled to them and even sources to actually get the equipment for free from non)rpofit working next to their homes of the majority of the team.
@PeterBX Also to answer to your question it would be possible to rollback from android 15 to 14 but you would do a complete reset, not use seedvault and go through the LunarOS as an intermediary step.
@rik glad to see that apparently my efforts during the beta were not being take into account on your gitlab with my adb reports and so fort. Good point for that 
and I see you have even the audacity to lie to everybody face including mine by saying :
As noted above, thanks to @guardian241 we now have many examples of non-working devices by simply using old phones as hotspots (my Pixel 3a XL for example). During the beta phase it was hard to find hardware to re-create the issue. I am not sure of the ease of access to common hardware that had the issue for the devs in France, but again, that is now moot as we all can see the issue easier with old phones acting as hotspots.
Where I gave you specific instructions on how to get devices non working with your OS and having those for free in a long letter in the beta section.
So thank yo ufor that.
I am at 21 august (starting from the end), since it is becoming more and more obvious that you ahve even the audacity to insult me indirectly and lie to everybody I will stop there my reading of this thread.
2 Likes
No issues with you personally whatsoever, in fact I think you will find I have been very appreciative of your detailed input and debugging in various threads, even defending you against some others that were devolving into name pointing etc over other issues. But, I am not going to accept your statement that I was lying to you however. The devs did not have time and resources to cold call various other companies to get a donated DD-WRT devices, etc. that had the issue, that is why Guardian uncovering that indeed the devs could reproduce this issue with devices already in their hand was a revelation.
Regardless, it isn’t useful to bring up “he said she said” finger pointing. The truth is the bug is beyond us at this point, we are hoping along with @plamen and the Braxtech team they can solve it with their LineageOS developer connections. Somewhere between Mediatek and LineageOS the bug lays buried at underlying Linux level / LineageOS overlay. Problem isn’t the hardware exactly, as an old AOSP 14 build of Lunar works. Problem isn’t universal with LineageOS / iodéOS as hundreds of other devices don’t have this issue. It is just a nasty bug we all want solved.
Regarding adding your specific devices to the chart, you can repeat them here, but if you will see I was reading 1000s of posts and writing 100s of replies in August / September and I didn’t have capacity to trawl through all other posts to find nuggets to put in the chart. Now the chart is not able to be edited by me due to it getting locked. I have asked @plamen to re-enable editing but I don’t have that ability yet.
2 Likes