Closed coderbyheart closed 4 years ago
Not able to reproduce this issue. Related to a63805c3be70730582a5d9c2a8b29ddb542f115d?
So, what does your device report? Maybe it's a network provider specific thing?
My device reports "LTE-M GPS" when having CONFIG_LTE_NETWORK_MODE_LTE_M_GPS=y
From the looks of the output log I can see that the device is configured to use NB-IOT and GPS.
[00:00:00.288,940]
AT%XSYSTEMMODE= LTE-M, NB-IOT, GNSS, Preferred lte mode
In other words the device must have been configure with CONFIG_LTE_NETWORK_MODE_NBIOT_GPS=y
which it looks like was the default for LTE build before commit a63805c3be70730582a5d9c2a8b29ddb542f115d
By default the config file uses CONFIG_LTE_NETWORK_MODE_NBIOT_GPS=y
. For the LTE-M build the line must be replaced by CONFIG_LTE_NETWORK_MODE_LTE_M_GPS=y
In my understanding the build-and-release.yaml as of now patches the lte-m build by replacing CONFIG_LTE_NETWORK_MODE_LTE_M_GPS=y
with CONFIG_LTE_NETWORK_MODE_LTE_M_GPS=y
. So when it does not find this config it is never patched. Can this be the case?