First issue is the wifi issue that I was first made aware of
Second issue is the phone will not access the internet using the sim card from Tmobile - makes calls and text messages but the browser will not work. Different browser, same thing. Works fine on the “old” calyX OS cell - a Google Pixel 4a
Third possible issue is - I think - really a question. Do these phones work with Verizon yet?
MY provider is US Mobile and we have several T Mobile SIM’s and one Verizon SIM phone.
Onward and upward,
Curt
1 Like
This is an iodéOS issue not a BraX3 one. They are working on it and issuing updates as they resolve things. You may want to have a look on the iodé community forum?
Several other people have had similar random issues. It’s likely your settings in iodéOS or a faulty SIM card. Have you searched this forum for the other previous discussions of this issue? There’s definitely a couple that included solutions for some people. I think one or two others haven’t been able to resolve it as yet because they haven’t identified the actual cause yet…
It has been made clear repeatedly they will pretty much never work with Verizon due to the cost of trying to get them approved and the fact, I believe, that they lack a couple of the required radio frequencies Verizon insist on.
2 Likes
Thanks for the response. That is very helpful. I will continue to learn more about the phones and their strengths and weaknesses. I knew this was a beta project so it is what it is.
Might have to do another de googled pixel or two until these are ready for prime time.
Onward and upward,
Curt
3 Likes
Need to make sure to enable mobile data. If it’s already enabled, make sure your APN settings are set correctly
5 Likes
That is a good call to check the APN settings. Thanks.
1 Like
This is not entirely correct. Iode has many phones that are working just fine, all based off Lineage. This issue does revolve are the BraX3 choice of hardware, which is MediaTek. As it was explained during the beta, it’s a fairly involved issue. To put it entirely on Iode would not be a fair statement.
4 Likes
I have not seen anyone getting Vzn to work. I tried, it saw the sim and that it was Vzn, all settings/procedures as recommended on this forum. I then flashed LunarOS, my Pxl IMEIs, reflashed iode with no change. I tested my sim while Lunar was installed, it worked with Vzn without doing anything, I could call and text. So I re-flashed Lunar (Android 14) and that is what I am using. It’s great, and I get to use my beautiful BraX3. I know of 2 other users who had the same results.
My observations: BraX3 has the required Vzn bands for LTE, but not 5G. Lunar does not have an option for 5G, just 4G (which is fine with me). Iode has option for 5G (I had selected “use 4G” when I tested). The version of Lunar I’m running is on Android 14. Iode is on Android 16 [edit: 15]. Main point is the IMEI’s are not on Vzn’s “OK List”, so it will never work out of the box - as stated.
Queries unanswered: With IMEI’s Vzn recognized, why did it not work on iode? Does Vzn see the phone is 5G capable, but without the proper bands? Or is there something different between Android 14 and Android 16 [edit: 15] that prevents it working in iode? I know that Brax2 OS is able to use Vzn with pxl IMEIs and it is on a lower version of Android.
2 Likes
Fair point @xancudo I forgot it’s specifically related to the MediaTek hardware, and in fact meant the comment more in the sense that it’s reliant on iodé OS updates/fixes to resolve, not that it was iodé’s fault; so their forum might be better place to look for discussion? So my bad.
Where did you find LunarOS ?
How did you change the IMEI ?
There is an article somewhere on this forum, I think @rik shared it, with a link to Lunr.
@xancudo OK, I already asked him and I also found plamen’s post about flashing the IMEI
No, don’t take it like that.
What I meant is that traditionally, many of the degoogled OS systems get their code from Lineage upstream, correct? And Lineage seems to drive the device support (new Iode Pixel 9 as an example).
What I feel has happened is that the BraX3 was kinda sorta maybe a first device for Iode that isn’t supported at the top by Lineage. So what is being experienced is something new, and the Iode folks are having to work, build, etc entirely on their own, with no upstream support, and probably minimal assistance from MediaTek directly (there are some known bugs that only MediaTek can resolve). Ultimately, this was a model chosen by the Brax folks with the hardware they selected.
That’s what I meant…lol
4 Likes
Per Plamen:
https://community.braxtech.net/t/how-to-manually-install-or-update-your-os-on-your-brax3/46
https://community.braxtech.net/t/how-to-change-the-imei-number-on-your-brax3/30
These are my journeys in the process (it is NOT simple):
https://community.braxtech.net/t/brax3-in-hand-imei-needed/1116
https://community.braxtech.net/t/help-please-with-sp-flash-tool-in-linux-and-terminal-commands/1816
EDIT: Be aware, the version of LunarOS that is provided is a “userdebug” version, which has a “watermark” on the phone upper left corner at all times. It is a bit in the way for browser address bar entry, but I’m living with it because the phone works. Instructions were provided for removing it but it requires rooting the phone, which I am not doing at this point.
Serial Console is enabled, which directs you to check bootloader to disable…it appears on the notification screen also at all times, like Trebuchet does in iode. Again, living with this after doing a bit of research.
I asked Rob on brax.me if there was someone I could ask a few questions of (re: Lunar) he said “wait for the project open source to be published shortly and you can interact with the devs”. So this is what I am waiting for, hoping there is resolution for those 2 issues without rooting the phone.
4 Likes
…
Wow… It’s worse than I knew…
I want to use the Brax3 as a WiFi-only device, but I am among those who can’t connect to my home network, or randomly elsewhere (hit-or-miss).
This is the first I’ve read about browsers not working with T-Mobile SIM cards - an issue I might never experience (not wanting to buy a SIM card) - but what else is lurking in the shadows?
Where is the well-maintained list of KNOWN issues?
Why do we have to hunt through a lot of separate threads to learn what problems other customers are having, to find tested workarounds, to find OS versions in which issues have been fixed, and to find updated status reports on open issues?
It’s called a KEDB (Known Error Database).
User forums and support emails that refer customers to various threads make a very poor substitute - forcing customers to incessantly return to the forum, search for any evidence of progress, or… to patiently wait, without wasting time, torturing oneself, or … to throw in the towel and demand a refund. NONE of those choices are good for future business.
For now, I’m going for the second option, leaving my Brax3 in the box, in Mint++ condition, while I wait for the dust to settle. I won’t be checking these threads nearly as often.
2 Likes
I understand your pain. I face these types of issues DAILY. WHY? I speculate that the User Interface is to blame. I do not believe that ALL users are “ignorant”, “stupid”, “lazy”, normies ( My N word), or refuse to read instructions. Many developers get in the habit of blaming the customer. Yes it is true some customers may need an instruction manual ( which they refuse to read) just to open the package. However this should not be an excuse to ‘HIDE’ solutions, errors, defects, compatibility problems, As-Built electrical, mechanical, troubleshooting schematics and diagrams. I also look forward to my Brax3 phones, but now I am a little concerned that I might be forced into developing a solution that works only for my needs. This reminds me of the HUGE issue of finding a GNU Linux tablet that actually works. It has been over 10 years and no one has developed what should be a simple solution.
Bravo on the KEDB! I also encourage AS BUILT wiring diagrams, details including Test and calibration points on each component. These must have been developed BEFORE the first devices were manufactured.
You have to be accustomed to the project, the user base exploded suddenly after the users started receiving their phones and problems started to appear, many people report problems like the mobile internet which most of the times is wrong APN settings, some phones have hardware problems like the bootloops and the WiFi problem is still of unknown origin, it is said to have started after the migration to Android 15. In terms of organization it seems that something more centralized is needed. We talk about a device that it was built to be degoogled since its inception by a small number of ordinary people who may also have a day job.
2 Likes
It is unfortunate, but you are observing the facts. It is late enough here so I guess “next week” which was over a month ago has extended at least one more “X” weeks. Question for you: Are you in CONUS? What happens after you receive an email listing your order number and shipping soon? Is this email just a teaser? What is next?
I forgot to mention “Last week” is no longer " …next week" and the new “next week” is in the unknown future? I am not being sarcastic just quoting from sources. Like a robot pretend I am stupid. But this “stupid” does not understand words like Maybe, coulda, shoulda, woulda and next week. They are not programmed into my vocabulary. Maybe I should ask ChatGPT? for assistance?