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

Fix wrong "changing LAC" alerts #863

Open
3 tasks done
He3556 opened this issue Apr 21, 2016 · 2 comments
Open
3 tasks done

Fix wrong "changing LAC" alerts #863

He3556 opened this issue Apr 21, 2016 · 2 comments

Comments

@He3556
Copy link
Collaborator

He3556 commented Apr 21, 2016

The characteristic of a true "changing LAC" alert is, that the LAC value of one certain cell is changing once or maybe a few times in short intervals (1-10 minutes).
But it makes no sense to raise the alarm when the LAC of many Cells are changing over the day. And that is what happens if the phone can't read the correct LAC or has timing problems in general. So we need to filter these (yellow) alarm if this conditions are true.

1.1. Maybe add a value "false changing LAC alarms present = True/False", to decide if the yellow alarm will really be shown on the display. We can discuss how this can be implemented.
(EventLog, i would leave it like it is, so we have the data of false alarm for research...)

Next problem will be - after the App is installed, it will still show the (false) yellow alarm until it detects more ch. LACs in other CellIDs and will switch to "false ch... = True"

1.2. We start with "false changing LAC alarms present = True" as default.
After 24hour "exploration time" and if there were no false alarms, we switch to "False"

I never got these false alarms so i can not check it with my device.


Agreements

Please check these boxes to ensure you've actually read and understood these important rules!

@SecUpwN SecUpwN changed the title 1. Fix wrong "changing LAC" alerts (i have an idea how to fix it - let me know if you want to help) Fix wrong "changing LAC" alerts Apr 23, 2016
@SecUpwN
Copy link
Member

SecUpwN commented Apr 24, 2016

@He3556, thanks for proposing a fix. Please confirm that this is no duplicate of #91.

@He3556
Copy link
Collaborator Author

He3556 commented May 9, 2016

This should become a list of Smartphones, where this false Alarm happens.

Samsung s4mini GT-19195, Android 4.4.2 (thx to @ciarankilbride)
Samsung A5 (2016) Issue #879 might be another problem (stuck on the same CID)

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

No branches or pull requests

2 participants