Senator Kennedy's bill to grant the FCC temporary auction authority to finish processing the Auction 108 licenses it has sold to their proper licensees. This would greatly benefit T-Mobile. This delayed process took what would have been a strategic advantage for T-Mobile (1 one year plus head start) and turned into catch-up, since AT&T and Verizon haven been busy installing their c-band n77 in rural areas.
I configured -44/-3 scenarios on an Edge 2022 to be an invalid connection, so yes, it would show no service.. I didn't realize it was a frequent issue though. How certain are you about the other values? Perhaps they are just unchanged from the previous array of signal information that was reported? If that is the case, I can try to have the app discard -44/-3 datapoints and leave the screen unchanged. I worry about the slippery slope of having it display as -140, because that leads users to believe there is a -140 signal present, when in reality we don't know what the actual reading is.
Haha me and you both wish this!!!
Following up, I've gone into the office in person today and took my Edge with me. It looks like it now shows "No service" instead of the -44/-3 value. I saw a lot of "no service" because it apparently does it a lot. I'll check again on the train ride home later.
Assuming I'm correct, is it possible to have some kind of middle ground on this? I think it was showing other legitimate values, like the TA, even when it was showing -44/-3. I'd prefer it show the data it has but at -140 dBm in those cases. I recognize this could be a pain to implement, and if it is, then no worries, mostly curious.
EDIT: But now I'm sitting here thinking "what if the PCI is bad and I don't know it?" But that can just as easily be the case on other phones that aren't caught. I do regularly see bad PCI entries on my other devices, so maybe this isn't the best option. Bleh, I wish this stuff just worked properly!