Closed jidanni closed 1 year ago
Without details from debug log it's impossible to tell the reason for that case.
OK, today I think I found the answer, in this log,
It is throwing away "invalid 5G cells".
Here I notice no points collected for the last 21 minutes.
So I turned on logging, and the only points recorded are the blue, but my real path was the red dots I added to the map.
Before 11:30 all the cells were rejected.
Then a mile east, at 11:32, it started rejecting cells again.
These are good Tmobile cells.
Here I have lined up a bad one and a good one from the log,
Cell invalid: CellNr (network=Network(mcc=310, mnc=260, iso=US), nci=4303061294, tac=10623744, pci=295,
Cell valid: CellLte(network=Network(mcc=310, mnc=260, iso=US), eci=30857584, tac=41602, pci=208,
band=BandNr (downlinkArfcn=520110, downlinkFrequency=2600550, number=38, name=2600),
band=BandLte(downlinkEarfcn=854, number=2, name=1900), aggregatedBands=[], bandwidth=null,
signal=SignalNr ( csiRsrp=null, csiRsrq=null, csiSinr=null, ssRsrp=-123, ssRsrq=-15, ssSinr=-2),
signal=SignalLte(rssi=-103, rsrp=-116.0, rsrq=-13.0, cqi=null, snr=null, timingAdvance=0),
connectionStatus=NoneConnection(), subscriptionId=4, timestamp=8058520)
connectionStatus=PrimaryConnection(), subscriptionId=4, timestamp=8060170)
Maybe related to https://github.com/mroczis/netmonster-core/issues/3 ?
@zamojski Maybe add a preference to override "NoneConnection()", else vast swaths of the United States will get rejected.
Here's some screenshots of other apps handling the cells TowerCollector rejects,
NetMonster,
Netmonitor,
I've discovered a bug in 5G parameters validator which doesn't accept some TAC values. The accepted value should be between 0 and 16777215 inclusive. Whenever I find some time to fix and publish the update you'll get it working.
I am investigating why, when simply driving down suburban streets at 30 mph, sometimes no points are recorded.
As you see, it is not a lack of coverage.
The final point is when, parked, I apparently woke it up temporarily.
I have turned off battery optimization, etc. as much as I can for this app here on Samsung Android 13.
Turning on debugging logging solved it, but that is a lot of overhead.