Deni- I have a second Brax3 running 6.9, and only using WiFi and I’m having the same issue. I even connected to the my other Brax3 hotspot to see if it was my AT&T router. But it didn’t work either.
You need a different updater to go to 7.x, beta/UpdaterBetaIode6v3.apk · master · ota / ota · GitLab , if it still doesn’t work download the update too and run it as a local update, brax3/iode-7.1-20251227-brax3-ota.zip · master · ota / release · GitLab , then remove the updater you just installed
Thank you George. The updater for 7.x is not working “There was a problem parsing the package” The local install worked. Thank you!
Probably the updater wasn’t downloaded correctly.
If it was already installed and your updater says “iodéOS beta” you should remove it so that you get only the official updates.
Long-tap on the updater icon, then App Info, 3 dots upper right corner and remove the update.
Hello, I am not sure if this is where this should go. I agree there are multiple issues now with the 7.0/7.1 version. The WiFi Calling is no longer working, it will not switch. It was working before. Now additionally, the WiFi is constantly saying it isn’t connected and you can browse for a little and then it has to be reset. I have walked through resetting the WiFi and the Mobile Data as instructed when the WiFi calling fix was released. Now, the problem is that the WiFi is just not connecting properly as it will not acknowledge the connection, but will allow browsing (for a little, but no WiFi calling). Again this started 7.0, but updated to 7.1 and is worse.
Update to my original post. I did a factory restore to the phone to see if there was an issue. But no the same issues. The WiFi calling no longer works, still gives an issue with connecting to the WiFi. Please advise to move this issue forward, there are a lot of issue that are causing problems with the general use of the phone. Even dialing it will give a connection error when on the T-Mobile network. Please note this all started around the 7.0 update.
Bizarre, do you think it just a Iode OS issue or not trying to be that person but a coordinated effort to deter open source projects from flourishing in the market since they are better in every sense and give you better autonomy over your personal items. Braxman should make a vid showing what a phone looks like or what can occur during malicious rooting attacks.
Maybe at this point send it in just budget for extra cost associated with repair process depending on where you bought it.
I browsed the Android code a bit and I noticed that Wi-Fi calling involves the IMS infrastructure, since many people solved their problems after updating to 7.0 by erasing all the APN settings and entering them again, have a look that your APN settings are still there and that you have an IMS APN setting correctly configured, even if they are there try to remove them, reboot to see if the phone will reconfigure them and if not enter them manually so get a screenshot first or search on the carrier’s website for the correct ones.
T-Mobile website says that you can try to reset the cellular settings
Settings > System > Reset options
Thank you for the response, but I did a factory reset. Which clears ALL settings. I did all the normal things. I am looking for a member of the IODE technical team to assist. The phone was working fine without incident. I am in FULL support of Open Source, I use Linux and feel this project is good (Brax3), IODE is making changes however that are not being fully tested or explored and they are causing these issues. Again, prior to these updates the phone was working perfectly without a hitch. I updated thinking it was going to just improve.
1 Like
Version 7.0 moved to Android 16 so the changes made in the AOSP code can cause problems, it seems to be something in the telephony stack and especially related to the IMS infrastructure because someone else had a similar problem where the carrier couldn’t connect the device to the IMS.
Since you have T-Mobile check the APNs you have and tell me if you can see an IMS one and what are its settings.
Ill give it a try and get back to you. thanks
This topic was automatically closed 4 days after the last reply. New replies are no longer allowed.