-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid WCDMA reports #88
Comments
I'm able to reproduce this at home by forcing my phone to use 3G in settings. |
Cell tower data depends a lot on your device and operating system. It seems that many devices only give the full set of values for the first cell tower Unfortunately there's not much that can be done about this. Cell towers without useful data (i.e. at least MCC, MNC and cell ID) could be filtered out. We could also use data from the first cell tower to fill the missing values in other cell towers, if we can assume that all cell towers in the report belong to the same network |
Now I've managed to get a WCDMA tower without a cell id, without any other cell towers to fill missing values from: "cellTowers": [
{
"age": 6452,
"asu": 96,
"locationAreaCode": 37265,
"mobileCountryCode": 505,
"mobileNetworkCode": 2,
"primaryScramblingCode": 223,
"radioType": "wcdma",
"serving": 0,
"signalStrength": -24
}
], I'm pretty confident that this was observed when I made a call. Given that this is more of a device/OS and data cleaning issue, I think I'll close this. |
When multiple WCDMA towers are recorded in the same report, only the first tower is valid:
I've noticed that my phone only seems to find exactly 1 or 32 wcdma cell towers. This does not occur when only 1 cell tower is recorded.
The text was updated successfully, but these errors were encountered: