Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Yes we often know the neighbors' cell ID all along #94

Closed
jidanni opened this issue Feb 23, 2024 · 1 comment
Closed

Yes we often know the neighbors' cell ID all along #94

jidanni opened this issue Feb 23, 2024 · 1 comment

Comments

@jidanni
Copy link

jidanni commented Feb 23, 2024

In the first image, all we know is the PCI, 357. We don't know the cell ID (eNb).
Screenshot_20240221_175103_NetMonster.jpg

Well, in fact we really do know the Cell ID (eNb). It's right there in the log, from a little earlier!

Screenshot_20240221_175158_NetMonster.jpg

So you really should show it to the user too, when displaying that PCI, as it's not just some unknown quantity.

In fact, all the other cell ID apps out there make the same sad mistake too.

It's just like, "What is this weird phone number that is calling me?"

Well, if you remembered (via a database), it's your grandmother who just called you earlier this afternoon!

"Are you sure? Maybe it's the same number but a different area code?"

Yes even the area code matches.

Even if they called you 5 years ago, it's still your grandmother probably...

@jidanni jidanni changed the title We know the cell ID all along Yes we often know the neighbors' cell ID all along Feb 23, 2024
@ExperiencersInternational

NetMonster already does this, but you have to locate sites. For some reason, doesn't do this on 2G though.

I don't know whether this is necessary on premium plans given that it automatically located stuff.

I've censored some information for privacy information but when you've located neighbouring cells, it'll show:

PCI eNB:Sector EARFCN RSRP/RSRQ
[Band] Location

Screenshot_20240731-134640

@mroczis mroczis closed this as completed Aug 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants