The question should be: “Do I need to install the BM818 Tool to be able to enable VoLTE?”
Answer: Yes, if you want the easy way to enable it by simply checking a box. Or “no,” if you want to research how to do it via minicom/AT commands. (I’m only assuming that’s possible.)
Technically true that it shows a firmware entry, but it’s truncated. To see the entire string on the L5, you have to shrink the scale waaaaay down - so small you can’t read it without a magnifying glass, unless you have the phone docked and have access to a large screen. And anyway, mine only shows the original firmware number, not the upgraded one.
He meant the main Librem 5 Settings app, on the Modem page.
True, but for me, it shows the original firmware number, not the upgraded one.
It’s “0” for mine, also.
In addition to not having the hardware kill switch engaged (i.e. blocking the modem from connecting), you also need to have Mobile turned on in the Settings app.
To install the app: sudo apt install bm818-tools
(for some reason the package name is in the plural, but the app label, once installed, is in the singular: (“BM818 Tool.”)
To upgrade the modem’s firmware to the September 2022 version, Support has said to contact them for instructions, but as they’re so busy lately… Someone (@lakei ) posted the instructions here recently. (I just checked and verified that the package names to be downloaded from Purism’s site are still the same.) [EDIT: Don’t do this without first contacting Purism Support for correct/latest instructions.]
@Brad , if, after installing BM818 Tool and launching it, you see the following 20220930 firmware version, then you’re already running the latest firmware. No need to do anything further. [EDIT: To clarify for anyone visiting this comment in the future, that date is the date of the most recent modem firmware at this time, and the rest of the string may vary, based on the applicable region. I think it’s best to first check with Purism Support for the latest info.]
The Firmware Version value is truncated regardless of what scaling is used on Crimson, and the string itself is different than the one provided by bm818-tools, so refer to the latter for an authoritative source.
Thank you everyone. Basically I was trying to get around installing bm818 tools, but that is clearly not going to fly. I’ll get to this this afternoon and see what it gives me
I have installed the bm818 tool and it is telling me my FW as in the pic attached.
It gets confusing here. This is slightly different to what is current, as listed above, however, in this thread:VoLTE in Australia someone mentions that they updated their FW in April which is the same as mine.
I’m not sure if I should try and update or see if what I have is satisfactory.
You have the latest modem firmware version for your region variant. For future reference, you can use GNOME Screenshot to capture the entire screen, or a section of it:
So after installing the “latest” FW I had no mobile reception with a message telling me I had no modem account. So I bit the bullet (after wondering why I even touched it!), and rolled it back to where it was. Fortunately for me things seem to have reverted back to where I was.
So, I’m hearing that my current FW is the latest for my region which was obviously Australia as I referenced that Australian Volte thread.
While I have been helped a lot on this forum this episode tells me to just wait before going too early.
Hopefully I’m fine now to try volte when it comes along.
I updated the firmware after YOU posted a screenshot of the incorrect FW for my region. Foolishly I then updated my FW assuming you were giving me correct information. THEN @FranklyFlawless informed me thàt I had the correct FW all along. I didn’t do it after. Why would I? Then I rolled it back.
If you’re going to try and wriggle out of your mistake do it correctly, or better still, own it and think twice next time.
I should never have strayed from my original question and mucked around with FW installs, so its partly almost a nightmare of my making.
Get your facts and chronologies correct next time old mate.
My bad. I was going by the “20220930” part without realizing that the rest of the string might be different. (And logically, it should vary by region, looking at it in hindsight.)
