Skip to content
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

Mi 8 Beidou signal marked as B1C instead of B1I #538

Closed
Jia-le-wang opened this issue Jul 3, 2021 · 3 comments
Closed

Mi 8 Beidou signal marked as B1C instead of B1I #538

Jia-le-wang opened this issue Jul 3, 2021 · 3 comments
Labels

Comments

@Jia-le-wang
Copy link

I noticed that the Beidou signal of the Mi 8 phone is marked as B1C signal, whose frequency is 1575420030Hz.However, from the data recorded by GNSSlogger, the Beidou signal captured by Mi 8 is still B1I, whose frequency is 1561097980Hz.

In brief, the Beidou B1C signal and B2a signal are new signals of the Beidou 3 system, which are transmitted from Beidou's C19-C46 satellite.In fact, only a few recent phones support these two new signals, such as the Mi 11, Huawei P40, Huawei Mate40, etc.

The attached file is a small piece of data collected with GNSSlogger. The constellation type 5 corresponds to the Beidou signal of MI8.

mi8-gnsslogger
MI8-gnsslogger.txt

@Jia-le-wang Jia-le-wang added the bug label Jul 3, 2021
@barbeau barbeau changed the title Is it a misjudgment that the Beidou signal of the Mi 8 in the GPSTest Database is marked as B1C instead of B1I? Mi 8 Beidou signal marked as B1C instead of B1I Jul 3, 2021
@barbeau
Copy link
Owner

barbeau commented Jul 3, 2021

@Jia-le-wang Thanks for opening this!

It looks like this is indeed a bug in the Mi 8. The display of carrier frequency bands in GPSTest (both the Status view and Database) is driven by data from the GnssStatus API:
https://developer.android.com/reference/android/location/GnssStatus

The log from GnssLogger and GPSTest uses the GNSS raw meaurements API:
https://developer.android.com/reference/android/location/GnssMeasurementsEvent

It looks like the GnssStatus API is erroneously reporting 1575420030Hz as the carrier frequency, while the raw measurements API is reporting 1561097980Hz as the carrier frequency. They don't agree with one another, so it appears the GnssStatus API is outputting bad data.

From a quick glance at the database it appears other devices with the Broadcom BCM4775 chips are reporting the same, so I wonder if this is actually a Broadcom bug.

Could you please report this to Xiaomi and let me know what they say?

@Jia-le-wang
Copy link
Author

OK,barbeau! I will try to give feedback on this issue, but I am not sure if Xiaomi will respond to me.Once I know the reason, I will reply here as soon as possible.

@barbeau
Copy link
Owner

barbeau commented Jan 25, 2022

Closing this for cleanup as it's not a GPSTest app issue, but I'd be interested in knowing if Xiaomi fixes (fixed?) this.

@barbeau barbeau closed this as completed Jan 25, 2022
@barbeau barbeau mentioned this issue Aug 4, 2022
15 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants