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

No "Neighbouring Cells" displayed #630

Open
pyr8 opened this issue Oct 22, 2015 · 19 comments
Open

No "Neighbouring Cells" displayed #630

pyr8 opened this issue Oct 22, 2015 · 19 comments
Labels

Comments

@pyr8
Copy link

pyr8 commented Oct 22, 2015

No "Neighbouring Cells" displayed under "Current Threat Level"

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@agilob
Copy link
Contributor

agilob commented Oct 22, 2015

Yeah, I noticed the same recently, what device and ROM (version) do you have?
It worked on my S3 with stack android, but when I switched to CM AIMSICD became unusable, patch should be easy to make, but want to make sure it's not device or version dependent.

@pyr8
Copy link
Author

pyr8 commented Oct 22, 2015

Running latest nightly of cyanogenmod on Galaxy S4.

Yeah, I noticed the same recently, what device and ROM (version) do you
have?
It worked on my S3 with stack android, but when I switched to CM AIMSICD
became unusable, patch should be easy to make, but want to make sure it's
not device or version dependent.


Reply to this email directly or view it on GitHub
#630 (comment)
.

@agilob
Copy link
Contributor

agilob commented Oct 22, 2015

I think CM team removed one class in 10.2 release that provided required data. No proof, just speculations.

@pyr8
Copy link
Author

pyr8 commented Oct 22, 2015

???
On Oct 22, 2015 6:19 AM, "agilob" notifications@github.com wrote:

I think CM team removed one class in 10.2 release that provided required
data. No proof, just speculations.


Reply to this email directly or view it on GitHub
#630 (comment)
.

@SecUpwN SecUpwN added the bug label Nov 13, 2015
@smarek
Copy link
Member

smarek commented Nov 17, 2015

@agilob could you please look up what class should have been removed? Curious what this speculation is based on.

@lop1
Copy link
Contributor

lop1 commented Dec 14, 2015

Same thing here with my galaxy s4 mini stock rom 4.4.2

@Tonat
Copy link

Tonat commented Jan 3, 2016

Same issue with galaxy S3 on CM 12.1

@SecUpwN
Copy link
Member

SecUpwN commented Jan 5, 2016

@larsgrefer, is #630 (comment) really the case? How can we get back hands on that important data?

@ProGamerGov
Copy link

I am running stock Android and have the same issue. It's a bug in the app, not because of CM. I have a Galaxy Core LTE with Android version 4.x. 1-2 AIMSICD version ago, it worked perfectly, but now same issue as OP.

@fabifri
Copy link

fabifri commented Apr 26, 2016

I am using CyanogenMod 12.1 (Android 5.1.1) on OnePlus Two. Telefon/SIM-Details showing fine, but no neighboring Cells at Current Threat Level. OpenCellID API Key is good and data downloaded.

If a developer needs a OnePlus Two to investigate on the issue - it's lying around here, so i can lend it or hand it over...

@SecUpwN
Copy link
Member

SecUpwN commented Apr 27, 2016

Good morning @fabifri, welcome to our project and thanks for offering your device for testing! Please keep it and continue testing, a fresh version of our app will be released by the end of this week.

To everyone reading this Issue: Which network type do you use? Keep in mind that our app currently works best when locked on 3G. If you use LTE, our app will not throw an error, but will get no data (yet).

@agilob
Copy link
Contributor

agilob commented Apr 27, 2016

Telefon/SIM-Details showing fine, but no neighboring Cells at Current Threat Level

That's device-dependent. On some you will get neighbouring cells, on some you won't.

@fabifri
Copy link

fabifri commented Apr 27, 2016

I am only using 3G (and sometimes 2G Networks).
Thanks for your Answers. Yeah, i'll continue testing - of course. ;-)

So, the Detection / Thread-Level-Display does still work, even if i can't see any Neighboring Cell Data?

@agilob
Copy link
Contributor

agilob commented Apr 27, 2016

no...

@davidak
Copy link

davidak commented Apr 28, 2016

Same Problem on a Fairphone 2 with Fairphone OS 1.2.8 (Android 5.1), also locked to 3G.

@SecUpwN
Copy link
Member

SecUpwN commented Apr 28, 2016

Folks, what we need is LOGFILES. Otherwise our developers will not be able to trace down the Issue. So to everyone wanting to help solving this: Please be so kind and record a full logcat with working neighboring cells, then do another one without neighboring cells. Instructions can be found here. Please anonymize your logs by removing CID, LAC and other things and use PASTEBIN. Thank you.

@agilob
Copy link
Contributor

agilob commented Apr 28, 2016

@SecUpwN List of neighbouring cells is implemented correctly (still there is place for improvements), if there is no NC it means:

  1. device doesn't support it, eg. most Samsung, some LGs doesn't support it at all
  2. ROM doesn't support it, some ROMs removed that feature
  3. You're using connection that doesn't provide neighbouring cells like CDMA

It's normal, stop confusing people.

@SecUpwN SecUpwN changed the title No "Neighbouring Cells" displayed under "Current Threat Level" No "Neighbouring Cells" displayed Apr 28, 2016
@SecUpwN
Copy link
Member

SecUpwN commented Apr 28, 2016

  1. device doesn't support it, eg. most Samsung, some LGs doesn't support it at all
  2. ROM doesn't support it, some ROMs removed that feature

That is why I think we need #181 during which #269 should be executed to make that clear to our users.

@ProGamerGov
Copy link

On an older version of the app, I could see neighbouring cells. Not sure exactly what version changed that, but I can check if it would help fix this issue for some of the users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

9 participants