Can't access my home wifi with my new Brax!

BraX3 iodéOS
70

so @rik…
I was asking you the model of your tplink. Because I am sorry but not all models are the same, there are version.
Do you know at least anything about wifi history and who did what about cracking and forcing the industry to evolve the wifi encryption method?

here, is to apparently enlighten you a little bit on the subject,

There are devices before that and after that.
Taht’s why I am asking you the model because after KRACK, manufacturer have rushed products into production to resolve the issue (which they couldn’t since even WPA3 is crackable but that’s another matter.

71

@Nefer well we can create a chat on brax.net if you prefer… But that would be simpler than to use this thread on the forum to resolve your network topology issue.
And my email would be the same nickname so [email protected]

72

Already posted way above: EAP245 5.2.0 Build 20240914 Rel. 59923(5553)

73

Brax.net does not work This site can’t be reached

brax.net took too long to respond.

Try:

ERR_CONNECTION_TIMED_OUT

74

sorry I am multitasking so I make errors my bad

if you prefer chat. We can do there. Or wherever you prefer it.

75

@rik give me a moment I m going to show you why that can’t be compared .

76

@rik
so this is going to be long I warn you. don’t complain afterwards dear sir!

1/ I don’t why do you get this idea but NEVER NEVER the firmware is unified across the board. Especially not between AP and router of the same brands. Why? Routers have a dedicated CPU for routing purposes but not only that.
Even ddwrt does not do unified build accross every devices the same.
I already point it out to the rest of the Team. ASK FUCKING KONG about it the main dev. He’s a very nice guy, never let anyone down.

2/ dimantle proof

Do you see the differences there?

3/ Did you not see the decrepencies between your 2 firmware and date of production?
His router is an FCC regulated from 2014 he has a 2015 firmware to prove it.
You, dear sir, have a fucking device from 2017 + what I suspect to be an up to date firmware.

Of course there is going to be changes in key exchange mechanism among those 2.

4/ You did notice I hope that in the review from the archer, and the routers I have mentionned many times in chat and in my posts that they are taken as comparaison . Same date of production, even different brands, same kind of implementation .

I have asked this many time to plamen and to the team. Why the fuck did you not ask Kong from ddwrt or the devs at lunarOS for the exact key exchange mechanism implementation. I am not talking about a fucking UML high abstraction schematics. I mean the fucking exact UML schematics granularity by granularity of each level of implementation.
You are not going to tell me, that and Kong and the devs at LunarOS are total morrons to who you can’t talk to no?
If lunarOS is working on the same goddamned phone in the same conditions and the iodeos is not on the same hardware in the same conditions…
It’s not like we did not test it during the beta. Mr Haack did it ofr us. Another guy User12345 did it too. So stop fucking around!

Ask the fucking implementations schematics of the devs who have already done the work on that same hardware.

We know it is not how the key is stored.
We know it is not because of some special options.
Not it is because of some special characters.
We did all those tests during the beta.

We know the problem is contained to the key exchange mechanism. That’s where the coding problem is. that’s where the problem happens. With specific encryption algorithm, proper surely to some OS implementation of routers.

But the matter stays that other devs did succeed with the same hardware and not avoid the problem like your team did.
And that every other fucking brands which are running under lineageOS don’t have the problem and still have a fucking Mediatek CPU. Don’t give me the fucking argument “it’s a lineage problem”, NO IT’s NOT.

It is a specific IodeOS problem with some encryption method exchanging with some specific cpu. Probably you did not include some conditional cases in your coding. That’s where the problem is.
So again ask people who knows better. Apparently the devs at mediatek does not help you much, so ask others.
And again… You want to reproduce the problem again and again… Ask for a free loan of hardware. The whole FFDN has plenty of those AP under ddwrt lying around.

And I ma pretty sure as soon as you have included those if missing in the programming, you will have also resolved and the wpa3 problem and the wpa2 enterprise key exchange problem. Because again, this a key exchange mechanism problem .

77

I did get an update that the connection issue is finally able to be reliably reproduced by the core devs. Yes, this is a very high priority for us, but no it is not the only thing that we are involved in (by far). But we are working on it, we never simply ignored the issue, but recreating it is key, and we are finally able to reliably do that.

BTW, I think its true that LunarOS (and any other “wifi is working” ROM) builds for the brax3 are still AOSP 14 based? One difference here is that the iodéOS 6.x builds are Android 15 based. We did see a similar wifi authentication issue on Sony XA2 device builds when moving from iodéOS 5.x (A14 base) to iodéOS 6.x (A15 base) that was resolved just in the past few months. No I am not the right person to comment on if the issue and fix for that device would be applicable to the brax3. But the point is that if the working ROMs are all A14 based then it is a lot more complicated to isolate the offending bits that are blocking the authentication handoff.

78

I sent you a message on Brax.me

79

Well ,we’ll see I guess in a few months. Because this being not the only thing you need to work on, and since your team is not decided since the beginning to ask for external help, I don’t see that resolve before months as I stated way before during the beta.
Problem is that again, other ROMs based on lineage 22.2, with mediatek cpu phones as such motorola and nothing phone and others do not report the same problem. Or else I would certainly have noted of that fact.

80

we’ll move there then :slight_smile:

81

@rik update from Nefer
also in wep he could not connect. but only on the 5ghz. The 2,4Ghz was able to be connected in wep.
IT is obviously not a solution but still using it because of your team’s sense of priority, so clearly described by plamen today.

So the only 2 places to look in the code, since in the beta you had even a problem to make recognize wifi network at first which I was the first to point it out to plamen in the chat and in the forum, are the way the phone is identifying the specs of a network and applying to his key exchange mechanism, and the key exchange mechanism itself.

82

I have the same problem. I cannot access my home wifi with my new Brax. However, I am in a worst situation than most because I am not tech savvy in the least! I spent a very long time on the phone with my internet provider Tech support and in the end, he concluded that the problem was with my new Brax 3 phone. All my other phones worked on wifi but only brax has failed.

83

Yes this is a very bad situation for you and for some others. Regardless of what has been said about us not caring, it is one that has been and remains a high priority. I am not one of the key devs and am new to the team, so there have been some gaps in me getting up to speed on the background of the issue, but the devs have been working on this, even sacrificing vacation time to keep working on this. It is a bit of a challenging bug, but at least it is reliably reproduceable now so that deeper digging can be done.

As a stopgap, you may need to use another device as a “wifi hotspot”. I’ll keep communicating here as any developments surface.

84

Thanking God that I was able to finally fix the wifi problem with my new Brax-3. You too may be able to do the same as I done that resolved my wifi issue. First, I did a factory reset and then I started over with the initial setup. When it got to the point to add my sim card, I did. Subsequently, it will ask you whether you want to use your sim card data or rather mobile data to use the internet, etc. I decided to choose that instead of choosing or using wifi. After I finished the setup. I used my mobile data to download the July 23, 2025 “update”. Once the update was finished, I than turned on my wifi and put in its password. Instantly, a notification popped up which alerted me that my wifi was now working. I then turned off my mobile data and surfed the internet without any problems. Matter fully resolved!

10 Likes
85

rik to be clear I did not say you did not care.
What I was staggering over is that only one of the devs did take the effort to reproduce the bug even so I have well explained, well contained the bug as others like xancudo.
That I did give specific instructions to get hardware to loan for free to test it. I asked this since week 3 or 4 from the beta start. It was a simple mail app to open and write a mail to the contact email to those non profit. Thats is all what I have said, you wanted to do this on your own without asking people who actually knows while you could have get more further logs from the AP in dev mode.

86

I resolved the wifi problem. Read my newest reply as to how I managed to do so. The only cost to fix the matter is to use your mobile data to download the July 23, 2025 update and of course, follow my simplistic instructions. Thanks for your response.

3 Likes
87

not the same problem then @yum because this has already been tested multiple times.

88

Remember it is just not the update but specifically choosing “mobile data” to access the internet and not choosing wifi during setup.

1 Like
89

well I will retry that in a few days but we already did try that a bunch of times, so unless there is something specific in the update of the 23 july …