With continued reference to FIG. 3, the memory hardware 322 of the UE 300 may store a data source 400 (e.g., CC-KPI log) that includes a mapping of: the current location 430 to corresponding CCs 220 that the UE 300 (i.e., transceiver 302) previously connected to at the current location 430 while operating in a non-CA mode; and the corresponding CCs 220 to values of corresponding expected KPIs 450. Each time the UE 300 connects to a CC 220 at the current location 430 while operating in the non-CA mode, the UE 300 may map the current location 430 to the corresponding CC 220 and measure one or more of the KPI values for that CC 220 to build the CC-KPI log 400. Multiple CC-KPI logs 400 each associated with a different location may be stored in the memory hardware 322. As the UE 300 is connected to only one CC 220 during operation in the non-CA mode, the UE 300 is using all the available transceiver resources 310 on that CC 220. The CC-KPI log 400 compile average KPI values for the CC 220 at the current location 430 based on the number of times the UE 300 connects to the CC 220 and the corresponding measured KPI values of the CC 220 during each of the connections. For instance, the UE 300 may measure one or more of the number of MIMO spatial layers used by the CC 220 at the current location 430, the SINR of the CC 220 at the current location 430, the RSRP of the CC 220 at the current location 430, and the CQI of the CC 220 at the current location 430. Accordingly, the term ‘expected KPI’ may refer to a historical average of the corresponding KPI value measured over multiple connections to a corresponding CC 220 at the current location 430. In some examples, a value of SINR exceeding 30 decibels (dB) is indicative of rich MIMO operating conditions on the given CC 220.