Flash Utility Post-Installation issues

Librem Phones (Librem 5)
#1

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.
Data Works.

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.

#2

Bluetooth won’t work unless you install some sort of non-free something first.
Have you tried manually setting the time and then tried updating the phone via the Software app?

1 Like
#3

Number 2 has been solved. Thanks. Setting it manually solved the issue.

1 Like
#5

Did you update the system? That might help #3.

#6

be sure that you have systemd-timesyncd installed. Some of the images have been missing that.

sudo apt install systemd-timesyncd

from terminal

Otherwise your manually set time may drift over time.

1 Like
Clock app with seconds && ntp
Initial Librem5/Nexdock360 impression
#7

I appreciate your thoughtfulness, you’ve made my day!

#8

Can you provide the output of the following for chatty:
killall -9 chatty
chatty -d -vvv

1 Like
#10

e[Ke[Ae[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Cakillall -9 chatty
e[?2004l
chatty: no process found
e[?2004he]0;purism@pureos: ~ae[01;32mpurism@pureose[00m:e[01;34m~e[00m$ chatty -d -vvv
e[?2004l
16:52:20.6586 e[1;95m chatty-folkse[0m[ 3199]: e[1;32mDEBUGe[0m: Loading eds
16:52:20.9380 e[1;36m chatty-applicatione[0m[ 3199]: e[1;32mINFOe[0m: chatty 0.6.7, git version: 0.6.7
16:52:20.9628 e[1;95m chatty-folkse[0m[ 3199]: e[1;32mDEBUGe[0m: Loading eds, get source registry e[1;32msucceedede[0m
16:52:20.9688 e[1;95m chatty-folkse[0m[ 3199]: e[1;32mDEBUGe[0m: Loading eds source: Personal
16:52:20.9719 e[1;33m chatty-purplee[0m[ 3199]: e[1;32mINFOe[0m: Loading purple, auto login: 1
16:52:20.9723 e[1;33m chatty-purplee[0m[ 3199]: e[1;32mDEBUGe[0m: chatty_purple_enable():2081: Enabling purple
[0:30:06.014221738] [3199] e[1;32m INFO e[1;37mCamera e[1;34mcamera_manager.cpp:293 e[0mlibcamera v0.0.0
[0:30:06.034229579] [3210] e[1;33m WARN e[1;37mCameraSensorProperties e[1;34mcamera_sensor_properties.cpp:174 e[0mNo static properties available for ‘s5k3l6xx’
[0:30:06.034372019] [3210] e[1;33m WARN e[1;37mCameraSensorProperties e[1;34mcamera_sensor_properties.cpp:176 e[0mPlease consider updating the camera sensor properties database
16:52:21.3946 e[1;92m GStreamere[0m[ 3199]:e[1;35mCRITICALe[0m: gst_element_message_full_with_details: assertion ‘GST_IS_ELEMENT (element)’ failed
16:52:21.3952 e[1;92m GStreamere[0m[ 3199]:e[1;35mCRITICALe[0m: gst_element_message_full_with_details: assertion ‘GST_IS_ELEMENT (element)’ failed
16:52:21.3991 e[1;92m GStreamere[0m[ 3199]:e[1;35mCRITICALe[0m: gst_element_message_full_with_details: assertion ‘GST_IS_ELEMENT (element)’ failed
16:52:21.3999 e[1;92m GStreamere[0m[ 3199]:e[1;35mCRITICALe[0m: gst_element_message_full_with_details: assertion ‘GST_IS_ELEMENT (element)’ failed
16:52:21.4003 e[1;92m GStreamere[0m[ 3199]:e[1;35mCRITICALe[0m: gst_element_message_full_with_details: assertion ‘GST_IS_ELEMENT (element)’ failed
16:52:21.4007 e[1;92m GStreamere[0m[ 3199]:e[1;35mCRITICALe[0m: gst_element_message_full_with_details: assertion ‘GST_IS_ELEMENT (element)’ failed
16:52:21.4023 e[1;92m GStreamere[0m[ 3199]:e[1;35mCRITICALe[0m: gst_element_message_full_with_details: assertion ‘GST_IS_ELEMENT (element)’ failed
16:52:21.4027 e[1;92m GStreamere[0m[ 3199]:e[1;35mCRITICALe[0m: gst_element_message_full_with_details: assertion ‘GST_IS_ELEMENT (element)’ failed
16:52:21.4690 e[1;94m chatty-xepse[0m[ 3199]: e[1;32mDEBUGe[0m: xmpp receipt feature added
16:52:21.4696 e[1;33m chatty-purplee[0m[ 3199]: e[1;32mDEBUGe[0m: Loaded purple plugins: prpl-aim:2.14.1 prpl-bonjour:2.14.1 prpl-gg:2.14.1 prpl-novell:2.14.1 prpl-icq:2.14.1 prpl-irc:2.14.1 ssl-nss:2.14.1 core-perl:2.14.1 prpl-simple:2.14.1 core-ssl:2.14.1 prpl-meanwhile:2.14.1 prpl-jabber:2.14.1 xep-http-file-upload:0.1.0 prpl-zephyr:2.14.1 core-riba-lurch:0.6.9-dev
16:52:21.4697 e[1;33m chatty-purplee[0m[ 3199]: e[1;32mDEBUGe[0m: libpurple initialized. Running version 2.14.1.
16:52:22.0730 e[1;36m chatty-applicatione[0m[ 3199]: e[1;32mINFOe[0m: New main window created
(16:52:22) mediamanager: Registered Audio/Source device Built-in Audio Headset Microphone + Internal Microphone
16:52:22.1347 e[1;95m chatty-folkse[0m[ 3199]: e[1;32mDEBUGe[0m: Loading eds, getting ebook client ‘Personal’ e[1;32msucceedede[0m
(16:52:22) mediamanager: Registered Audio/Source device Modem Stereo
(16:52:22) mediamanager: Registered Audio/Sink device Built-in Audio Headphones + Speaker + Handset
(16:52:22) mediamanager: Registered Audio/Sink device Modem Stereo
16:52:22.1592 e[1;95m chatty-folkse[0m[ 3199]: e[1;32mDEBUGe[0m: Loading eds, getting ebook client view ‘Personal’ e[1;32msucceedede[0m
16:52:22.1624 e[1;91m chatty-utilse[0m[ 3199]: e[1;32mDEBUGe[0m: checking number “redacted my phone number”
16:52:22.2803 e[1;93m chatty-mmsde[0m[ 3199]: e[1;32mDEBUGe[0m: MMSD appeared
16:52:22.2815 e[1;92m chatty-mm-accounte[0m[ 3199]: e[1;32mDEBUGe[0m: Modem Manager appeared
16:52:22.2858 e[1;93m chatty-mmsde[0m[ 3199]: e[1;32mDEBUGe[0m: chatty_mmsd_get_mmsd_modemmanager_settings_cb
16:52:22.2860 e[1;93m chatty-mmsde[0m[ 3199]: e[1;32mDEBUGe[0m: CarrierMMSC is set to http://mms.invalid
16:52:22.2861 e[1;93m chatty-mmsde[0m[ 3199]: e[1;32mDEBUGe[0m: MMS_APN is set to apn.invalid
16:52:22.2861 e[1;93m chatty-mmsde[0m[ 3199]: e[1;32mDEBUGe[0m: CarrierMMSProxy is set to (null)
16:52:22.2861 e[1;93m chatty-mmsde[0m[ 3199]: e[1;32mDEBUGe[0m: default_modem_number is set to (null)
16:52:22.2862 e[1;93m chatty-mmsde[0m[ 3199]: e[1;32mDEBUGe[0m: AutoProcessOnConnection is set to True!
16:52:22.2862 e[1;93m chatty-mmsde[0m[ 3199]: e[1;32mDEBUGe[0m: AutoProcessSMSWAP is set to True!
16:52:22.2937 e[1;93m chatty-mmsde[0m[ 3199]: e[1;32mDEBUGe[0m: Got MMSD Manager
16:52:22.2978 e[1;93m chatty-mmsde[0m[ 3199]: e[1;32mDEBUGe[0m: No default MMSD Modem Number Set
16:52:22.2980 e[1;93m chatty-mmsde[0m[ 3199]: e[1;32mDEBUGe[0m: Service Path: /org/ofono/mms/modemmanager
16:52:22.2980 e[1;93m chatty-mmsde[0m[ 3199]: e[1;32mDEBUGe[0m: Identity: modemmanager
16:52:22.3491 e[1;93m chatty-mmsde[0m[ 3199]: e[1;32mDEBUGe[0m: Got MMSD Service
16:52:22.3600 e[1;93m chatty-mmsde[0m[ 3199]: e[1;32mDEBUGe[0m: chatty_mmsd_get_all_mms_cb
16:52:22.3602 e[1;93m chatty-mmsde[0m[ 3199]: e[1;32mDEBUGe[0m: Have 0 MMS messages to process
16:52:22.3603 e[1;93m chatty-mmsde[0m[ 3199]: e[1;32mDEBUGe[0m: chatty_mmsd_get_mmsd_service_settings_cb
16:52:22.3604 e[1;93m chatty-mmsde[0m[ 3199]: e[1;32mDEBUGe[0m: TotalMaxAttachmentSize is set to 1100000
16:52:22.3605 e[1;93m chatty-mmsde[0m[ 3199]: e[1;32mDEBUGe[0m: MaxAttachments is set to 25
16:52:22.3605 e[1;93m chatty-mmsde[0m[ 3199]: e[1;32mDEBUGe[0m: AutoCreateSMIL is set to 0
16:52:22.5752 e[1;92m chatty-mm-accounte[0m[ 3199]: e[1;32mDEBUGe[0m: parsing sms, id: 0, path: /org/freedesktop/ModemManager1/SMS/38
16:52:22.5754 e[1;91m chatty-utilse[0m[ 3199]: e[1;32mDEBUGe[0m: checking number
16:52:22.5755 e[1;95m chatty-mm-chate[0m[ 3199]:e[1;35mCRITICALe[0m: chatty_mm_chat_find_user: assertion ‘CHATTY_IS_MM_CHAT (self)’ failed
**
chatty-mm-account:ERROR:…/src/mm/chatty-mm-account.c:385:chatty_mm_account_append_message: assertion failed: (CHATTY_IS_CHAT (chat))
Bail out! chatty-mm-account:ERROR:…/src/mm/chatty-mm-account.c:385:chatty_mm_account_append_message: assertion failed: (CHATTY_IS_CHAT (chat))
Aborted
e[?2004he]0;purism@pureos: ~ae[01;32mpurism@pureose[00m:e[01;34m~e[00m$
e[Ke]0;purism@pureos: ~ae[01;32mpurism@pureose[00m:e[01;34m~e[00m$ exit
e[?2004l
exit

Script done on 2022-08-14 16:52:26-05:00 [COMMAND_EXIT_CODE=“134”]

#11

Hmm I don’t know how to fix that. Could you create an account at source.puri.sm (you’ll also need to email support@puri.sm to get your account approved).

Then submit a bug about it here: https://source.puri.sm/Librem5/chatty/-/issues
I think this is a bug.

#12

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).

Please open and read: “This can be skipped if MMS is not needed.”

#13

This quite similar subject might be easily related to the chosen variant of the modem you are using over there: “Just because the phone is capable, does NOT mean it will work on a particular carrier. If the phone doesn’t have full LTE bands for any carrier, it hasn’t a snowballs chance of working.”

#14

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.

1 Like
#15

For Librem laptops, true. I don’t believe this applies to the Librem 5.

This is perhaps more likely to be the complication over exact card firmware version + card operating mode + actual hardware that needs to work: Wifi/bluetooth issues

To be clear, with my Librem 5 still running Amber … Bluetooth and WiFi both work fine with no card firmware in the root file system at all and with default operating mode.

#16 
 1.  first command:
> > > > > >
> > > > > >     wget https://source.puri.sm/angus.ainslie/firmware-rs9116-nonfree/-/raw/debian/master/Firmware/RS9116_NLINK_WLAN_BT_IMAGE.rps
> > > > > >
> > > > > > 2.  second command:
> > > > > >
> > > > > >     sudo mv RS9116_NLINK_WLAN_BT_IMAGE.rps /lib/firmware
> > > > > >
> > > > > > 3.  reboot the phone.

Through searching forums, it appears nonfree rps firmware was the solution. I ran the command above, i was able to do a test connect to my Android phone, and it connected. Number 1 has been resolved.

John was correct, this resolved the bluetooth 1.) issue.

1 Like
#17

Does anyone have the previous build of Chatty by chance? chatty_0.6.6-1pureos1_arm64.deb instead of chatty_0.6.7-1pureos1_arm64.deb? The repo doesnt list it in main.

#18

Not really.

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.

1 Like
#19

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.

2 Likes
#20

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.

1 Like