Sigh. In attempting to put the database back on my phone this evening after doing an update, it obliterated the database again. It had been working as normal for several weeks.
I think I'm going to [finally] apply the Android 10 update and see what happens. Maybe it'll help...
EDIT: When I rebooted, it came back up with data included. No idea what to make of it. Reimported from the file just in case, and it remained present, so we'll see, I guess.
Separately, how hard would it be to make it possible to filter the Neighbor Notes? I noticed earlier today that I'm seeing neighbors on Bands 12 and 2 pretty often. Naturally, it tries to look for notes for those PCIs with PLMN 310120, even though they're clearly T-Mobile neighbors. Would it be possible to add a "Sprint transition mode" or something where it matches Band 25/26/41 neighbor notes to 310120 and other neighbor notes to 310260?
Interesting to read an update. But I remember a lot of people back then said, 'I will believe it when I see it.' Now, 5 years later, I can't help but hear those voices even louder now. They were certainly proven right. Even if it does eventually happen.
I know that. I'm talking about further down the line for 5G. What I'm saying is that with the addition of Sprint's PCS, they can expand LTE on PCS and shift HSPA from AWS to the remaining 5MHz in PCS-B so that they can have a 25MHz n66 carrier down the line and a 20MHz n2 carrier since n2 is not currently registered for greater than 20MHz carriers.
The other solution would be to simply get rid of HSPA altogether and have two 25MHz n66 and n25 carriers since n25 allows for 25MHz carriers. Then T-Mobile could retain the 5MHz PCS-G for legacy LTE service.