@Greenie I know gosh!!! I have been the first beta tester to mention the wifi problem stop repeating the same thing over and over. I have already fight that battle.
1 Like
When did you first report the issue, and can you confirm the staff that has known of the issue?
@0x7 I was one of the first to have the brax3 before my deployment. So The same day I received it at the very beginning of the beta program.
They did try to fix it with 2 updates if I am counting correctly no luck. That’s the thrid update they tried.
You can read earlier on this same thread how infuriated I am about the fact that only one dev took the time to reproduce the issue with the exact same setup (I hope) and not just trying to reproduce it out of the blue without my directives like the others did.
You have access to every comments I made besides the part in the beta part of the forum where yo uare not allowed.
I also have the same problem. Unable to connect using WPA or WPA2 personal to my Wi-Fi access point.
Technical information:
- IodéOS 6.5 - July 8, 2025 (I cannot update because OTA updates consistently fail)
- Wi-Fi Access Point: SFR NB6 Modem (Model: NB6VAC-FXC-r0 - Version: NB6VAC-MAIN-R4.0.47h3)
I tested, in 2.4 GHz band:
- WPA Personal - TKIP in b/g radio mode → Not OK
- WPA Personal - AES in b/g radio mode → Not OK
- WPA2 Personal - AES in b/g and n radio modes → Not OK
@rik If you think it might be useful, I can provide debug logs.
3 Likes
Well that’s a more problematic @rik one since it is going to be ISP box… Which mean an entire major ISP customers in FRANCE are going to be affected
sorry we do sleep sometimes, so depending on your timezone there can be delays.
tried on a mikrotik AP, a google home AP, and a local ISP modem called HELIX, all have 2.4 and 5gz
only think it connects is a hotspot from my other cell.
1 Like
It sounds like the team was made aware of this wifi connection problem during beta testing but still hasn’t found a solution? Specifically, the password asked by the system always fails even though we are connecting to the correct router host name. Doe anyone have any idea how long this will take to fix? I’m going to run out of data soon and will have to go back to my old phone.
Edit: I was able to connect my old phone (motorola G7 play) and the Brax3 by bluetooth hotspot so this should help me save data while at home. We are going out of town soon so will have to rely on data again.
Yes, it seems there aren’t any success stories with the latest 6.6 beta. Very infuriating for all of you, we certainly know this!
For me the only way I can get it to not authenticate correctly is when I set APs (Mikrotik with OpenWRT / TP-Link EAP245 stock firmware / gl-iNet with OpenWRT) to use WPA Personal (any combo of other options).
WPA2 Personal (any combo of options) keeps working reliably.
So, if any with issues can confirm they have tried (if possible) to set their AP to WPA2 Personal that would help, but I know that some have confirmed it still doesn’t work for them.
Also, if wireless security is not a risk for you (out of range of anyone not trusted accessing your network) WEP setting may work for you on your AP. BUT you have been warned, this is not much more secure than simply having a wide-open network.
Lastly, if you can get access to any wifi portable hotspot device that would share the connection to other devices, this could get you by without having to only use mobile data.
Yes, none of these options (except if WPA2 only works for you) are good.
To the issue, the debug logs we have gotten from the one iodé team member that reliably has connection issues show wpa_supplicant auth_failures=2 reason=WRONG_KEY errors. Again I am not involved at the core dev level for iodéOS, but as a long time Linux hacker / admin I speculate that it is at the underlying linux <--> wifi driver level, these errors are lower than the Android layers on top at least in my reading.
Working from the other side, we are also trying to see if there are any Android 15 based custom ROMs for a phone with this Mediatek Dimensity 6300 SOC that do not have the problem to cross reference. Motorola G and G Power (2025), Oppo devices, Realme, etc. but nothing that we know of that is able to be unlocked and has a de-googled (microG or no) custom ROM build. We will keep digging on both fronts.
PS for @ericHz nice avatar, I’m a long term Ubuntu Touch enthusiast too, only had to let it go when VoLTE was required in the USA and I couldn’t make calls.
3 Likes
Going to experiment today. I have never had an issue with my beta unit connecting to my wireless network and I have two final versions being delivered today. Going to see if when you try to connect to WiFi makes a difference. One, I will leave the sim out and attempt to set up wifi immediately. The other, I’ll put the sim in first and set up using mobile data. If one of these triggers the rejected password issue, we’ll know it’s not a router protocol issue. Will report once done
3 Likes
Wow, I’m really looking forward to hearing how it turned out. My BF hasn’t set up his Brax3 yet so I’m hoping he can avoid the wifi pitfall that I have ATM. To make matters worse, the seedvault backup failed 2x and am trying to do another so I don’t lose my apps in a factory reset to correct the wifi connectivity problem.
Yes, I have tried to set my AP to WPA2 Personal and I confirm it doesn’t work for me.
You are probably already aware, but for those interested in VoLTE support on Ubuntu Touch, it is now enabled on several devices.
Personally, I use it on my daily driver.
Here is a link to some tests conducted before enabling VoLTE on the Poco X3 NFC / X3
1 Like
UPDATE: No issue with WiFi connection
Phone 1: installed SIM card, turned on mobile data, did not attempt to connect to WiFi, went through setup, successfully connected to wireless network.
Phone 2: no sim, was able to immediately connect to WiFi.
Wireless details: TP-Link Deco X20 802.11ac WPA2-PSK AES
Noticed that I did have to set the date, time, and time zone first during setup. Could incorrect setting there be causing issues?
Only other test I can think of is to insert SIM, enable mobile data, and try to connect to WiFi immediately during setup but pretty sure that is the way I have been setting up the Beta device each time I reset it.
3 Likes
Was able to use the free wifi at the mall to-day. Router type unknown.
At BellAlliant , my ISP retail outlet, I was not able to use that router to-day. They provide the Actiontec GT784WN router.
So updated the BraX3 OS to 6.6 at the mall.
1 Like
Thanks so much for letting us know. I did set date and time zone during set up (sim not installed). I guess I’m going to have to factory reset the phone and try again to choose data (not wifi) during set up and hope for the best.
1 Like
I have this problem also.
Both my routers are dd-wrt, connecting with WPA2-PSK. All the other devices in the house are connected this way with no problems.
Ive managed to connect to the internet via bluetooth to another phone via tethering, and I am downloading the latest iode 6.3 update. That will take a couple hours.
Hopefully this fixes somthing.
I download the 6.6 update using data, and no, nothing changed
Sorry I think this will not be successful, we have confirmed reports of dd-wrt devices not connecting to the brax3. Also the update is to 6.6 if you refresh in your updater app before downloading. But I don’t think that you will have success with that either.
Not a lot of hope in this thread as of yet except for try different wifi hotspots 
1 Like
There appears to be some problem with the authentication logic. Was able to set up a guest wifi channel on my router with security turned off. Interested to see if others have the same results. Obviously not an ideal workaround…
Am using a TP Link C5400.. Granted, it’s a dinosaur…
The router is not issue its cypher key and timestamp maybe a timezone issue there as well as key exchanges must be valid in time as well..
Thing is hotspot works.. Let me ask grok and chatgpt
Chatgpt says:
- Security Mode Mismatch
Cause: Router uses WPA3 and your phone expects WPA2, or vice versa.
Fix:
In your router settings, try switching to WPA2-PSK (AES) only (not mixed WPA2/WPA3).
Grrok 4 says:
App Interference or System Settings: A third-party app (e.g., VPN, antivirus, or signal-monitoring tools) might be disrupting WiFi on certain networks. Incorrect date/time settings can also block secure connections.
Software Bug or Glitch in Android 15: Updates can introduce temporary WiFi connectivity issues, such as random disconnections, failure to detect internet on specific networks, or problems with certain frequencies (e.g., 5GHz networks). This seems common after the Android 15 update, where the phone might connect to some networks (like a hotspot) but struggle with others (like home routers)
DNS or Internet Detection Issues: The phone connects but thinks there’s “no internet” due to DNS resolution failures on your home network, even if the connection is established.