Sebastian Krzyszkowiak @dos@librem.one

@melroy > modern.IE

Oh wow, what a blast from the past. It still operates???

@beacondb Awesome, thanks! Works fine now:)

BTW. I've just looked into related MM code and APIs closer, and turns out that QMI modems report neighboring cell information with signal strength (RSRP/RSRQ). However, only the serving cell has its cellId available, the rest have only TAC/LAC (always the same for all seen cells, at least in case of LTE) and PCI. Could this potentially be used to improve estimation accuracy? Right now the endpoint outright rejects cells without cellId set.

@beacondb Ah, Geoclue doesn't include that field, and ModemManager doesn't expose it in its location API (it does in cell info API though). It used to work with MLS this way and still works with Google. Could this be handled on beaconDB side?

Ultimately Geoclue could do a much better job here, but this makes the versions currently out there incompatible with beaconDB...

@beacondb I'm trying with the first LTE cell from my operator in the dump and get 404:

$ zcat MLS-full-cell-export-final.csv.gz | grep LTE,260,3, | head -n 1
LTE,260,3,11,1306213,402,21.0048378,52.2180052,0,1,1,1670110185,1670110185,
$ curl -X POST https://beacondb.net/v1/geolocate -H "content-type:application/json" -d '{"cellTowers":[{"radioType":"lte","mobileCountryCode":260,"mobileNetworkCode":3,"locationAreaCode":11,"cellId":1306213}]}'

@rysiek @joearisia inb4 it was their custom signature verification code that crashed when fed with garbage 😈

@Andromxda @mobian @beacondb Geoclue can do it.

@rysiek Well, you linked to someone who claimed it wasn't. How trustworthy that report is? You tell me! 😁

@rysiek From what I've gathered so far from the ever reliable Social Media Feeds™ it appears that it wasn't a driver update, but rather a update data file that then caused the unchanged driver to crash when it tried to parse and apply it, which would effectively bypass the signing requirement.

@beacondb @nicorikken Is Mozilla's cell tower dataset actually in use? When I query beaconDB for an LTE cell I'm connected to right now (which is present in Mozilla's dump) I only get 404 responses.

@aho Potentially! It's kinda a PD MITM device (so you could provide power and use USB 2 while negotiating custom alt-mode or debug accessory mode, sending VDMs etc.), plus it exposes UART on SBU over USB. One possible use-case is to get convenient access to Librem 5's serial console, but it should also be useful with, say, Macbooks or plenty other stuff.

@josch Well, refunds are another matter... 😫 Just wanted to point out that manufacturing of the phones is a thing from the past, they've been already produced with a surplus, so if you actually wanted to receive one you could for a while now.

@josch @deshipu @mntmn Orders from 2019 have been manufactured and shipped two years ago already, and the whole queue was processed last year. They only get shipped after confirming shipping address, so if you didn't then your phone is still waiting in the warehouse.

I don't know yet if the board is going to work, but I know it's going to be pretty. #kicad #ee