Cell towers, Location on new engine, low accuracy.

Describe the bug
microG with new location engine (v0.3.2) send only one cell tower on mozilla location server -> location low accuracy.

To Reproduce
Steps to reproduce the behavior:

1. Go to microG Settings
2. Click on "Location"
3. Enable only one point "Mobile network location" - "Request from Mozilla", other point - turn off. See screen1.
4. Start logcat
5. Request location in any app
6. Grub logcat tag IchnaeaLocation an see request with only one cell tower and response with location low accuracy:

D IchnaeaLocation: GeolocateRequest(carrier=null, considerIp=false, homeMobileCountryCode=null, homeMobileNetworkCode=null, radioType=null, bluetoothBeacons=null, cellTowers=[CellTower(radioType=lte, mobileCountryCode=DELETED, mobileNetworkCode=DELETED, locationAreaCode=DELETED, cellId=DELETED, age=20, psc=null, signalStrength=-104, timingAdvance=null)], wifiAccessPoints=null, fallbacks=Fallback(lacf=true, ipf=false)) -> GeolocateResponse(location=ResponseLocation(lat=DELETED, lng=DELETED), accuracy=50000.0, fallback=lacf, error=null)

If you don't see geolocation request in logcat, you may force geolocation request. I do not know a guaranteed method to force geolocation request, but you may change network type in SIMs setting or insert other SIM and request location again.

Expected behavior
microG with old location engine (v0.2.7) with MozillaNlpBackend send many towers on mozilla server -> location higher accuracy.

D/IchnaeaBackendService request: {"radioType":"gsm","cellTowers":[{"radioType":"gsm","mobileCountryCode":DELETED,"mobileNetworkCode":DELETED,"locationAreaCode":DELETED,"cellId":DELETED,"signalStrength":-77,"asu":18},{"radioType":"gsm","mobileCountryCode":DELETED,"mobileNetworkCode":DELETED,"locationAreaCode":DELETED,"cellId":DELETED,"signalStrength":-73,"asu":20},{"radioType":"gsm","mobileCountryCode":DELETED,"mobileNetworkCode":DELETED,"locationAreaCode":DELETED,"cellId":DELETED,"signalStrength":-77,"asu":18},{"radioType":"gsm","mobileCountryCode":DELETED,"mobileNetworkCode":DELETED,"locationAreaCode":DELETED,"cellId":DELETED,"signalStrength":-81,"asu":16},{"radioType":"gsm","mobileCountryCode":DELETED,"mobileNetworkCode":DELETED,"locationAreaCode":DELETED,"cellId":DELETED,"signalStrength":-53,"asu":30},{"radioType":"gsm","mobileCountryCode":DELETED,"mobileNetworkCode":DELETED,"locationAreaCode":DELETED,"cellId":DELETED,"signalStrength":-77,"asu":18}],"wifiAccessPoints":[],"fallbacks":{"lacf":true,"ipf":false}}

[D/IchnaeaBackendService] response: {"location": {"lat": DELETED, "lng": DELETED}, "accuracy": 1000.0, "fallback": "lacf"}

Screenshots
**

System
Two devices:

1. Android Version: 13, Custom ROM: LineageOS 20 Official
2. Android Version: 14, Custom ROM: LineageOS 21 Official

Additional context
microG pushed as priv-app with granted all required priv-app premissions throu xml (because LineageOS Official don't have location patch) and granted all premissions at runtime in selfcheck and system settings app.
I read earlier that some devices by design can get only one tower, but the old version 0.2.7 of the microG get many towers on the same device. Maybe I need setup ROM setting?

Start by reproducing the report with the new location engine and inspect logcat entries for IchnaeaLocation. Compare its Mozilla request with the older MozillaNlpBackend example and verify which available cell towers are included. Done means the request behavior is explained and, if appropriate, a regression test or fix demonstrates the expected higher-accuracy result.