Is Galileo supported or not? - Redmi Note 9S / Note 9 Pro (Indian Model) Question

Hello, please can you report your experience with Galileo reception and custom ROMs?
Development team reported, through official forum, that Galileo is not supported but smartphone was advertised with Galileo support.
It is still advertised as supported in italian, spanish and indian page. It has been removed from all the other pages (de, fr, uk, se, cn, id, ru and global).
According to european laws, advertising a product with different real specification is prohibited and sanctioned and customer have the right to ask for a replacement of refund.
Please, if you have a custom ROM, can you check if it is supported or not?

---

Interesting, the official galileo webpage still lists the note 9 pro as supported device. The GPStest app shows no usage of galileo satellites on my phone.

---

Thank you very much for sharing this link! The same for me with GPSTest. Attached you can find a screenshot. Once I saw a satellite with PRN 236, which is unknown and I can't find any reference about it using google.
Leni_YO said:
Interesting, the official galileo webpage still lists the note 9 pro as supported device. The GPStest app shows no usage of galileo satellites on my phone.
Click to expand...
Click to collapse

---

simone982 said:
Hello, please can you report your experience with Galileo reception and custom ROMs?
Development team reported, through official forum, that Galileo is not supported but smartphone was advertised with Galileo support.
It is still advertised as supported in italian, spanish and indian page. It has been removed from all the other pages (de, fr, uk, se, cn, id, ru and global).
According to european laws, advertising a product with different real specification is prohibited and sanctioned and customer have the right to ask for a replacement of refund.
Please, if you have a custom ROM, can you check if it is supported or not?
Click to expand...
Click to collapse
according to qualcomm-snapdragon-720g-mobile-platform-product-brief.pdf it is supported by hardware
Code:
GPS, Glonass, BeiDou, Galileo, QZSS,
and SBAS
• NavIC support
• Dual-Frequency GNSS (L1 + L5)
According to Xiaomi_Kernel_OpenSource xiaomi use (qcom) source branch
Code:
Branch: curtana-q-oss
Base tag: LA.UM.8.9.r1-07100-SM6xx.0
Looking into GPS relevant source code at hardware/qcom/gps/tree/?h=LA.UM.8.9.r1-07100-SM6xx.0 and compare it with e.g. newer branch sm8150 (Snapdragon 855) hardware/qcom/gps/tree/?h=LA.UM.8.1.r1-14500-sm8150.0
there is missing code for dual frequency GNSS support for branch SM6xx
Code:
...
void
+GnssAdapter::requestSvPolyForClient(LocationAPI* client, const LocationCallbacks& callbacks) {
+ if (callbacks.gnssSvPolynomialCb) {
+ LocationCallbacks oldCallbacks = getClientCallbacks(client);
+ if (!oldCallbacks.gnssSvPolynomialCb) {
+ LOC_LOGd("request sv poly");
+ GnssAidingDataSvMask svDataMask = GNSS_AIDING_DATA_SV_POLY_BIT;
+ mLocApi->requestForAidingData(svDataMask);
+ }
+ }
+}
+
+void
+GnssAdapter::reportSvPolynomial(const GnssSvPolynomial &svPolynomial)
+{
+ for (auto it=mClientData.begin(); it != mClientData.end(); ++it) {
+ if (nullptr != it->second.gnssSvPolynomialCb) {
+ it->second.gnssSvPolynomialCb(svPolynomial);
+ }
+ }
+}
+
+void
...
+typedef uint32_t LocSvDgnssMeasStatusMask;
+#define LOC_MASK_DGNSS_EPOCH_TIME_VALID 0x1 /**< DGNSS Epoch time is valid */
+#define LOC_MASK_DGNSS_MEAS_STATUS_PR_VALID 0x2 /**< Pseudo Range correction is valid */
+#define LOC_MASK_DGNSS_MEAS_STATUS_PRR_VALID 0x4 /**< Pseudo Range rate correction is valid */
...
+#define GNSS_SV_MEAS_HEADER_HAS_DGNSS_CORRECTION_SOURCE_TYPE 0x08000000
+#define GNSS_SV_MEAS_HEADER_HAS_DGNSS_CORRECTION_SOURCE_ID 0x010000000
+#define GNSS_SV_MEAS_HEADER_HAS_DGNSS_REF_STATION_ID 0x020000000
+#define GNSS_SV_MEAS_HEADER_HAS_REF_COUNT_TICKS 0x040000000
...
+ /** Unique SV Identifier.
+ * SV Range for supported constellation is specified as below:
+ * - For GPS: 1 to 32
+ * - For GLONASS: 65 to 96
+ * - For SBAS: 120 to 158 and 183 to 191
+ * - For QZSS: 193 to 197
+ * - For BDS: 201 to 237
+ * - For GAL: 301 to 336
+ * - For NAVIC: 401 to 414 */
...
+// carrier frequency of the signal tracked
+#define GPS_L1CA_CARRIER_FREQUENCY (1575420000.0)
+#define GPS_L1C_CARRIER_FREQUENCY (1575420000.0)
+#define GPS_L2C_L_CARRIER_FREQUENCY (1227600000.0)
+#define GPS_L5_Q_CARRIER_FREQUENCY (1176450000.0)
+#define GLONASS_G1_CARRIER_FREQUENCY (1602000000.0)
+#define GLONASS_G2_CARRIER_FREQUENCY (1246000000.0)
+#define GALILEO_E1_C_CARRIER_FREQUENCY (1575420000.0)
+#define GALILEO_E5A_Q_CARRIER_FREQUENCY (1176450000.0)
+#define GALILEO_E5B_Q_CARRIER_FREQUENCY (1207140000.0)
+#define BEIDOU_B1_I_CARRIER_FREQUENCY (1561098000.0)
+#define BEIDOU_B1C_CARRIER_FREQUENCY (1575420000.0)
+#define BEIDOU_B2_I_CARRIER_FREQUENCY (1207140000.0)
+#define BEIDOU_B2A_I_CARRIER_FREQUENCY (1176450000.0)
+#define BEIDOU_B2A_Q_CARRIER_FREQUENCY (1176450000.0)
+#define QZSS_L1CA_CARRIER_FREQUENCY (1575420000.0)
+#define QZSS_L1S_CARRIER_FREQUENCY (1575420000.0)
+#define QZSS_L2C_L_CARRIER_FREQUENCY (1227600000.0)
+#define QZSS_L5_Q_CARRIER_FREQUENCY (1176450000.0)
+#define SBAS_L1_CA_CARRIER_FREQUENCY (1575420000.0)
+#define NAVIC_L5_CARRIER_FREQUENCY (1176450000.0)
...
maybe Xiaomi use custom branch of LA.UM.8.9.r1-07100-SM6xx.0
doubt, if snapdragon 720G (sm7125) really based on sm6xx/atoll source code branch

---

Thank you for your answer. I'll try to ask also on ROM threads if someone with different kernel can give us feedback

---

Oh, there is a newer branch LA.UM.8.9.r1-08900-SM6xx.0 from April 29, 2020 which add more DGNSS stuff

---

moreroid said:
Oh, there is a newer branch LA.UM.8.9.r1-08900-SM6xx.0 from April 29, 2020 which add more DGNSS stuff
Click to expand...
Click to collapse
I have rooted redmi note 9s.
Maybe someone knows how to modify the kernel or gps.confg or some other way.
To improve the handling of gps galileo and dual gps.
How someone knows how to do it.
Then I can test it.
That's a question for developers anyway.

---

sad, current xiaomi.eu V11.0.10.0.QJWMIXM (curtana) release don't include latest gps related source branch
one change between LA.UM.8.9.r1-07100-SM6xx.0 and LA.UM.8.9.r1-08900-SM6xx.0 was:
Code:
- LOC_LOGD("%s]: Delta:%" PRIi64 "ns time too large, retry number #%u...",
- __FUNCTION__, sinceBootTimeDeltaNanos, i+1);
+ LOC_LOGd("Delta:%" PRIi64 "ns time too large, retry number #%u...",
+ sinceBootTimeDeltaNanos, i + 1);
but old result was found
Code:
curtana:/ # getprop ro.build.fingerprint_real
Redmi/curtana_global/curtana:10/QKQ1.191215.002/V11.0.10.0.QJWMIXM:user/release-keys/1595409748
curtana:/ # strings /vendor/lib64/hw/[email protected] | grep Delta:
%s]: Delta:%lins time too large, retry number #%u...

---

Same (previous) version in 11.0.4.0 joyeuse.
A developer here said that something should be enabled by Xiaomi in boot/vendor
https://forum.xda-developers.com/showpost.php?p=83170851&postcount=739
moreroid said:
sad, current xiaomi.eu V11.0.10.0.QJWMIXM (curtana) release don't include latest gps related source branch
one change between LA.UM.8.9.r1-07100-SM6xx.0 and LA.UM.8.9.r1-08900-SM6xx.0 was:
Code:
- LOC_LOGD("%s]: Delta:%" PRIi64 "ns time too large, retry number #%u...",
- __FUNCTION__, sinceBootTimeDeltaNanos, i+1);
+ LOC_LOGd("Delta:%" PRIi64 "ns time too large, retry number #%u...",
+ sinceBootTimeDeltaNanos, i + 1);
but old result was found
Code:
curtana:/ # getprop ro.build.fingerprint_real
Redmi/curtana_global/curtana:10/QKQ1.191215.002/V11.0.10.0.QJWMIXM:user/release-keys/1595409748
curtana:/ # strings /vendor/lib64/hw/[email protected] | grep Delta:
%s]: Delta:%lins time too large, retry number #%u...
Click to expand...
Click to collapse

---

simone982 said:
Same (previous) version in 11.0.4.0 joyeuse.
A developer here said that something should be enabled by Xiaomi in boot/vendor
https://forum.xda-developers.com/showpost.php?p=83170851&postcount=739
Click to expand...
Click to collapse
for curtana Xiaomi must take newer qcom source branch LA.UM.8.9.r1-08900-SM6xx.0 (April 29, 2020) compile it and provide it in usual way
current used(?) qcom source branch LA.UM.8.9.r1-07100-SM6xx.0 (December 25, 2019) is supposed to old for dgnss (dual-frequency gps) support
there is no excuse it wouldn't work for Xiaomi

---

There is a discussion here about the lack of galileo and dual gps.
https://c.mi.com/thread-3124154-5-1.html

---

Galileo support has been removed also from italian and spanish page

---

moreroid said:
for curtana Xiaomi must take newer qcom source branch LA.UM.8.9.r1-08900-SM6xx.0 (April 29, 2020) compile it and provide it in usual way
current used(?) qcom source branch LA.UM.8.9.r1-07100-SM6xx.0 (December 25, 2019) is supposed to old for dgnss (dual-frequency gps) support
there is no excuse it wouldn't work for Xiaomi
Click to expand...
Click to collapse
Moderator xiaomi handed over
this valuable information to xiaomi developers.
https://c.mi.com/thread-3124154-5-1.html

---

Yes, thanks, I saw
kriss3 said:
Moderator xiaomi handed over
this valuable information to xiaomi developers.
https://c.mi.com/thread-3124154-5-1.html
Click to expand...
Click to collapse

---

Italian customer service told me that Galileo is not supported in Redmi Note 9 Pro. That's disappointing and what a shame for Xiaomi!

---

I've also have a Mi A2 and developers are able to update Qualcomm drivers by themselves, is it because this super partition system that they're not able to do this for curtana/joyeuse?

---

It seems that kernel source for joyeuse has been published here:
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/gram-q-oss
I'll dig into this

---

simone982 said:
It seems that kernel source for joyeuse has been published here:
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/gram-q-oss
I'll dig into this
Click to expand...
Click to collapse
I have xiaomi eu miui 12 i used the cortana kernel
Kernel] [MIUI-AOSP] Yuki- ユ キ Kernel [curtana, excalibur, gram, joyeuse]
The aosp kernel seems to have a newer branch
maybe galileo and dual gps would work
Unfortunately, I do not have aosp.
https://c.mi.com/thread-3424963-1-0.html
https://forum.xda-developers.com/redmi-note-9-pro/development/kernel-yuki-kernel-3-0-t4182393
Rebased over LA.UM.8.9.r1-10600-SM6xx.0 (AOSP variant only)
Merge tag 'LA.UM.8.1.r1-16200-sm8150.0'
Wifi, Audio tag used LA.UM.8.9.r1-10600-SM6xx.0
Net Wireward
Enable PSI monitor
Add pidfd backport
Fixed boot on Joyeuse (Miui variant)
Last xiaomi changes (Miui variant)
Disable LMK
Removed
[TESTING] exec: Add node tampering blacklist function
[TESTING] allow power @ 2 and perf 2 to tampering blacklist

---

https://forum.xda-developers.com/showpost.php?p=83804167&postcount=15
I asked already if someone can check
kriss3 said:
I have xiaomi eu miui 12 i used the cortana kernel
Kernel] [MIUI-AOSP] Yuki- ユ キ Kernel [curtana, excalibur, gram, joyeuse]
The aosp kernel seems to have a newer branch
maybe galileo and dual gps would work
Unfortunately, I do not have aosp.
https://c.mi.com/thread-3424963-1-0.html
https://forum.xda-developers.com/redmi-note-9-pro/development/kernel-yuki-kernel-3-0-t4182393
Rebased over LA.UM.8.9.r1-10600-SM6xx.0 (AOSP variant only)
Merge tag 'LA.UM.8.1.r1-16200-sm8150.0'
Wifi, Audio tag used LA.UM.8.9.r1-10600-SM6xx.0
Net Wireward
Enable PSI monitor
Add pidfd backport
Fixed boot on Joyeuse (Miui variant)
Last xiaomi changes (Miui variant)
Disable LMK
Removed
[TESTING] exec: Add node tampering blacklist function
[TESTING] allow power @ 2 and perf 2 to tampering blacklist
Click to expand...
Click to collapse

---

simone982 said:
https://forum.xda-developers.com/showpost.php?p=83804167&postcount=15
I asked already if someone can check
Click to expand...
Click to collapse
I have miui 12 europe redmi note 9s
This is the newest one I downloaded from November 14 Cortana.
Everything's fine with the kernel.
The GPS works.
It does not detect only galileo and dual gps frequency,
but never detected it.
Although the 720g snapdragon supports
Someone needs to do a gps fix to detect galileo and dual gps