I saw this all the time with Byzantium. No change in Crimson.
3 Likes
What is the deal with Firefox versions between Byzantium and Crimson?
I have a web page thing from a prop shop company I have to use on my phone sometimes. Iāve been using Firefox on Byzantium for a long time but these goobers updated the web site/webapp thing so now it has a banner on Byzantium that they detected/decided my browser is incompatible. They say this even if I hack the user agent string to match a PC that was compatible.
Now, I tried reimaging my Librem 5 to crimson so I could try this important webapp/site.
For some reason it DOES work on Crimson but the Firefox user agent says it is the same version 140 that we had on Byzantium. What is the difference? Why does this version or configuration of Firefox work? Could I backport the difference to Byzantium somehow?
1 Like
I used to see this happen every so often but these days I donāt see this now. I wish I could tell you how it got resolved but generally, I keep the modem unpowered.
If I had to guess, they could be running some JavaScript tests on what browser API features are available.
If you needed to, you could manually install Firefox ESR with the various installation methods Mozilla supports instead of using the one that Purism provides, though you probably wonāt get the firefox-mobile-config benefits without additional tweaking.
I have noticed that on Crimson, the phoneās clock seems to slowly fall behind. Does anyone else have this issue? It seems to fix itself (in the short term) by toggling network time sync on and back off.
2 Likes
Interesting. I believe you can blame the replacement of NTP daemon with systemd-timesyncd.
There are possibly three mechanisms at work with NTP:
- Discrete time adjustment.
- Slewing. Slow adjustment until one has arrived at Network Time.
- Clock adjustment factor (clock hardware drift).
If your internal clock is far enough away from āNetwork Timeā, it will correct with 1 or 1 combined with 2. If itās reasonably close, it will only correct with 2. Some systems (which have frequent contact with Network Time will also notice the consistent rate of slowing/speeding of the internal clock vs. Network Time and will always have that factor incorporated to stop your problem (3).
I believe the latter (3) used to be stored in /var/lib/ntp/ntp.drift ā¦ but now that systemd has taken over with systemd-timesyncd ā¦ Iām not sure that happens any more or whether any of the above is true anymore.
Interestingly, I just searched and found out that it was Debian 12 where Debian switched from ntpd to systemd-timesyncd. So I believe you can blame systemd. I wonder whether systemd has an equivalent setting for (3). A simple search says that systemd-timesyncd doesnāt have that feature anymore. I donāt know how hard (or wise) it would be to drop systemd-timesyncd and use the old ntpd.
3 Likes
I imagine that you can disable the systemd-timesyncd service and just go ahead and install ntp if thatās what you want.
I donāt think it is as straightforward as this because seemingly byzantium (Debian 11) already uses only systemd-timesyncd and I have not noticed any time-keeping issue on byzantium.
In any case timedatectl and systemctl status systemd-timesyncd andcat /etc/default/timesyncd.conf would be useful starting points for investigation.
Obviously the kill switches work against time synchronisation, likewise a firewall. So there is plenty to check.
For what itās worth, I havenāt noticed any time-keeping issues on crimson either. Iād like to see whether anyone else experiences this, and whether @Dlonk can reproduce it on byzantium as well.
My Crimsonās time is correct.
My Crimsonās time is also correct.
1 Like
I am not able to set the layout of external (that is physical, as opposed to on-screen which work fine) keyboards.
I set the layout in the settings / keyboard (to Swiss-French, that is ch+fr), but the external keyboard is still a QWERTY US layout.
Does anyone have the same issue? I didnāt have to do anything in particular on Byzantiumā¦
For me it works fine, but never changed these settings since Crimson (so same config as on Byzantium).
But my modem seems to shut off from time to time - was the 2nd time now (and gyroscope was disconnected while other sensors were active). I probably should investigate this later.
Do you have network time sync on? Sounds like perhaps Dlonk has it off, and thatās when he sees the drift?
Maybe carrier dependent? I use Mint Mobile (T-Mobile MVNO).
For people running Crimson, do you also have no ring tone on call?
Most outbound calls have no ring, but occasionally, some do. I had the same issue on Byzantium.
Inbound calls trigger the ringtone just fine as far as Iāve noticed.
Was speaking about outbound, sorry for confusion. I just think it got worse and now all outbound calls have no ring tone with Crimson. On Byzantium it was randomly, thatās why I did not notice any change on the first call. But after a couple of calls without I wanted to ask here.
This has nothing to do with the installed OS (neither byzantium nor crimson do the ringing signal in software), and all to do with your cellular network.
So, maybe a Calls feature request to have an additional audio indication that a call attempt is in progress, or something like that, as a solution?
I think more detail has been posted elsewhere in this forum about this particular oddity - if you want to search.
1 Like
For me:
- Mobile calls, ring is inconsistent and rare.
- Calls to land lines, it rings (maybe mostly) all the time.
1 Like