It’s hard to predict an ETA on a fix from iode.
There were a lot of positive signs last time I posted (e.g. making WPA2 working, but braking WPA3) but the issue is still not resolved.
We were hoping that involving devs on our end (more familiar with BSP development), will help resolve the issue quick. What ended up happening is getting iode broken (BSP developers aren’t familiar with iode/lineage code, and iode team isn’t familiar with BSP code).
We haven’t given up on resolving the issue. We are exploring different ways to resolve the issues, that are in our control, including:
1. Fixing the issue on iodeOS
We’ve contracted LineageOS developers to port LineageOS on the BraX3.
Lineage developers have way more experience resolving similar driver/HAL related issues - it’s what they deal with on every new port. When successful on the BraX3, it will be easier for iode team to port the changes to their OS and thus fix the issue (iodeOS is a fork of lineageOS after all).
We’ve been looking into porting LineageOS for a while, but the priority was not high, as it was just another OS option to introduce (similar to UB touch). Now the priority on LOS port is high, as it is expected to resolve issues with iodeOS.
2. Porting more operating systems to the BraX3
While 1 remains priority, we will add more OS options as well. We’ve already ported UB Touch (installable build will be shared very soon), working on LineageOS (as shared in point 1), working on CipherOS port. We’re also discussing making LunarOS more user-friendly as well, making it closer to stock OS experience, similar to what BraXOS was on the BraX2.
We still believe that collaborating with different custom ROMs is the way to go. We won’t give up on that. We’ve learnt a lot of things in this process so far, and understood that some mistakes were made. We will do what is in our control. The rest is noise.
Whilst a different issue, is it likely fixing this wifi bug will also recctify the inability to make wifi calls unless mobile coverage is present (which defeats the whole purpose of wifi calling)?
And if not, what is the timeline / ease of non tech people being able to install a new OS that actually allows the phone to function fully? Does it delete all data etc for example, in the process?
It is not the same bug. Those are different. But nonetheless, porting lineageOS will aim to resolve other iodeOS issues, including the wifi calling one.
Timeline is hard to set. Getting a port to boot is rather quick. Getting it to a stage where it’s stable and has resolved medium/major issues, could take a bit. We will be fully transparent on the progress of each. We will also be sharing early stage ports, so that volunteers can help us testing. Feedback on those will be collected publicly. Issue boards will be made public as well, so that people can make an informed decision on when to switch.
We will try to make installing a new OS as easy as possible. The objective is to help non tech savvy users to make the switch.
Yes, data stored on the device will be deleted when making the switch.
Unsure if this is related or not but initially i had the password not accepted issue for wifi which I resolved by purchasing a new repeater which has worked flawlessly for many weeks. However now since i updated to iodeOS8 I can no longer access wifi via that new repeater. So getting the same original problem, password not accepted. Did OS8 break something ?
Thank you @plamen. Please remember that some of us have brax3’s gathering dust because the workarounds aren’t viable for one reason or another, so PLEASE give updates regularly (weekly!). I think you guys owe us that.
Also, because mine’s gathering dust as is, once lineageos or another aosp variant is ready for testing, I’ll volunteer to test as long as the wifi bug is expected to not be present. I’m already familiar with lineageos and I degoogled my old phone myself so I have a reasonably good skill level with this stuff if that matters at all. As an aside, I like to root my phones so I would hope to do that during testing if that’s okay.
FWIW I am experiencing an issue since I did the 6.8 update last Sunday that causes my internet access to constantly drop out (and also randomly locks my physical SIM) - I can connect to wi-fi fine and get DHCP (IP address assigned, gateway, DNS server IPs, etc) but multiple times a day the phone reports no internet on either of my 2 SIMs or any wi-fi I am connected to or connect to - but not 100% sure it’s OS related could be something else. But I presume you are specifically not connecting to your wi-fi to start with so they won’t be related…?
If not related to what I’ve experienced then maybe they have inadvertently reverted something (minor?) they had in 6.7 or 6.6 when trying to fix something else in 6.8?
I see no mention of the Actiontec MI424WR-GEN2, in the chart, above, despite my detailed post made to this thread, 17 days ago:
Also: The chart , above, reports that FIVE different routers made by GL-iNet are working as expected with the Brax3 (green symbols), so I’ve just stupidly spent good money after bad, purchasing a GLi-Net GL-X3000NR (a.k.a. Spitz AX), only to discover that the BRAX3 cannot complete a WiFi connection, no matter how I configure this new router, EVEN THOUGH every other WiFi device in my house CAN connect to the NEW router, just as readily as they CAN connect to the old router. Arrrrgh!
So, at this point, I am ONLY asking that TWO ROUTERS be added to the chart, above, BOTH with big, fat, red dots:
Actiontec MI424WR-GEN2 Version F
And
GLi-Net GL-X3000NR (a.k.a. Spitz AX)
Meanwhile, as others have mentioned, when I travel, the BRAX3 connects to some public WiFi, but not to others… Uggh!
I’m glad to hear you are still pursuing a solution.
Update, issue now fixed. It was some kind of glitch on the wi-fi Repeater resolved by a full reset.
Strange how come some devices still connected to the repeater whilst the Brax3 and one other device would not
Yay! My Brax3 WiFi is now working fine with the GLi-Net GL-X3000NR (a.k.a. Spitz AX)
Please put a big fat green dot next to this router, in the chart above.
(I changed the password to 8 characters - it worked. Changed back to the intended 24 character password - it worked. I must have been making a “typo” repeatedly with my new GLi router, but no such luck with my Actiontec MI424WR-GEN2 that still has not been added to the chart above, with a red dot.)
I’m posting a new update regarding the wifi issue.
The issue is still not fixed on iodeOS.
We’re progressing with LineageOS port and expect to have a port done by early next week. The port will be in early stage, so it won’t be fully functional, but it will serve as the base for lineage devs to work on the wifi issues. As mentioned previously, once the issue gets fixed, iode devs will have an easy time applying the fix to their OS, considering they are forking lineage.
We’re very confident in the capabilities of the lineage OS devs. They have already done successful ports to MediaTek powered devices, including some of Nothing’s phones - which we share the solution house (dealing with low level drivers) supplier with.
I have the issue using an ASUS RT-AC66U B1 router on [3.0.0.4.386_51733] firmware and WPA2-Personal security. I can connect if I disable security and have an open access port.
At present, the Brax3 is an extra phone for me and I don’t rely on it for daily usage. A Google search of iodéOS vs LineageOS gives this AI overview:
“iodéOS is a privacy-focused, deGoogled custom ROM built on top of LineageOS, adding a built-in ad and tracker blocker, MicroG, and other privacy-friendly apps. LineageOS is a more general-purpose custom ROM that provides the base for iodéOS and serves as a base for many other ROMs. The main difference is that iodéOS is a specialized, more opinionated fork that prioritizes privacy by default, while LineageOS is a more stripped-down, stock Android experience that users can customize themselves.”
If this is a fair comparison, I’m inclined to wait for iodéOS to fix the problem rather than to install LineageOS and have to reconfigure everything.
This is a rational choice. I am working on an Linux Arch version for a portable “Smart Manjaro”. Not many dev’s working on this solution. If you have not tried Linux Distros I recommend Manjaro to try first. It will urge you to refrain from Distro hopping the many Deb/Ubuntu based distros like most “normies”.
