Librem 5 Evergreen Version 1, L5v1-05, BM818-E1 modem
Mint Mobile - United States
It appears to download the latest image. Not sure if that is the issue.
All Hardware Kill Switches are turned on.
Phone Calls work.
1.) No Bluetooth Found. All hardware kill switches on, restarted multiple times.
2.) PureOS Store Repo Issue: “The Certificate chain uses expired certificate”. Time is set to auto in settings with Location settings on as well.
3.) Chatty 0.6.7 crashes with cellular hardware kill switch on and I am unable to change the MMS APN settings from GUI unless I use nano in terminal to change them. It will still crash then if cellular hardware kill switch is turned on.
Might be but it is still quite logical to me (and should help) that if datum (date) on someones Linux smartphone is several weeks behind the actual date that telecommunications provider (MNO over valid SIM card connected) will not distribute or at least not save related message(s) as of today if it is having stamp form several weeks ago (current textual message coming “now” from the phone with the wrong/past date on it).
Therefore installing of systemd-timesyncd (and reboot) should solve all related issues? Especially chatty related ones, thanks @steve again therefore!
In short: when date & time indeed correct = there should no output happen from the above two commands (as I see things). Hoppefully @digitalprairie will confirm my thoughts here (after installing systemd-timesyncd).
I installed systemd-timesyncd and this didn’t resolve the issue unfortunately.
I am most likely going to do a fresh install using PureOS to flash a new image.
I will then try to build Chatty and install.
I am also going to submit a bug report and see if anything can be found.
I currently run a dual sim Note10 on Lineage OS + MicroG that doesn’t have VoLTE. 2G calls still work unlike most other carriers. Since VoLTE is not in operation I don’t have data during calls. My Librem5 A1 modem will arriving here soon. I don’t see how missing hardware radio bands could cause chatty to crash. The quoted Verizon article probably doesn’t have much basis for the carrier I’m running. I could be wrong though.
What firmware do you think is in the card if you take no action? The firmware that runs inside the card is always non-free (unfortunately). What you are doing there is choosing which version of the non-free firmware you want to load into the card, presumably because different firmware versions have different capabilities / bugs.
I state again: I have never done anything with the WiFi/BT firmware on my Librem 5 (i.e. I am using whatever is already loaded into the card out-of-the-box, and the directory /lib/firmware does not even exist) and Bluetooth works for me out-of-the-box.
I understand that. I will most likely keep tinkering around with this for a long time to come. I will most likely try the bluetooth again with a fresh install here soon without installing the firmware. Unrelated to that I was able to learn how to take git clones and build Chatty and install from terminal. I tried 0.6.4, 0.6.6, and 0.6.7 and was unable to get Chatty to keep from crashing while the modem hardware kill switch was set to on. systemd-timesyncd is installed as well. It’s been fun learning about this device in the last three days I’ve had it. I’ll eventually get there and iron it out in time. I’m new to the Librem platform.
Number 3 has been resolved out of pure luck. I went to the app store, selected Show Incompatible software, from there I was testing incompatible apps and stumbled upon Modem Manager GUI, from there I could see texts in that software, I then opened Chatty, it appears a missing dependency was met and I can send and receive sms now in Chatty.