Developers: Bug Fix Priority List (alpha)

[E3V3A]

After some brief voting on current and outstanding issues, we think we have reached a consensus that the following issues should receive the highest priority and in this order.

• 1. Open Cell ID Data is not shown in DB viewer, thus blocking many other functions such as proper map view. Bug report: 0.1.24.alpha-b13 #153 and this comment.

• 2. Fix Map Viewer, as described in issue Maps Viewer #13, so that BTS/towers are color-coded as:

  BLUE = currently connected BTS,
  GREEN = other nearby BTS's.
  RED = new or previously unknown BTS.

• 3. Since (1) and (2) are intimately related to "Detection-1: Changing LAC/CID": Changing LAC on same CID #91 .

• 4. Remake the "About Menu" by adding buttons in: Refreshing About-Menu with Buttons #132 .

Other suggestions are welcome.

IFF all these can be resolved for the next release, that release will be our First Public BETA!
IF NOT all can be resolved, the next working release will be another Public ALPHA.

[SecUpwN]

Thanks. Note: @tobykurien currently has very little time. Linking to #105 and #156.

[tobykurien]

Thanks, this is helpful! Will get to it ASAP.

[SecUpwN]

@E3V3A, I noticed you said public Alpha. Does that mean I shall activate our official F-Droid and Aptoide store for it, or shall that mean "just" another fresh upload to our GitHub WIP-Releases?

[E3V3A]

If it's an alpha, I don't think it's appropriate to release on the F-Droid and Aptoide stores, especially since they're not very fond of having beta apps on there. If we can get (3) to work, I guess a beta release would be ok, since we'll probably remain in beta for quite some time.

[SecUpwN]

@E3V3A, it appears to me as if this Issue is a dupe of #105, except for that #23 has not been added to this list. How come it's not a priority? Nevertheless, I agree with you - if this one is solved, we are about ready to rumble and I will push the APK to the stores I already created. Thank you for working on it!

[E3V3A]

I closed that issue as outdated. Also since nobody have been able to make any progress on testing and getting somewhere on #23, it will be downgraded and possibly abandoned in favor of a real RF debug interface.

[SecUpwN]

Ok, fair @E3V3A. The empire strikes back, huh? ;-) What will happen to the AT Command Processor then? Will it be renamed again so that we have to change all documentation and links.. again?

[E3V3A]

@SecUpwN This is for an internal OT discussion, not for GH.

[SecUpwN]

@tobykurien, thank you for that awesome pull request! Does it solve all Issues in here? I would like @E3V3A to confirm here if only #91 persists, which would mean we could finally move on to that one.

[E3V3A]

Hi @tobykurien, I just submitted #168, and things look promising.

[tobykurien]

That's yet another overwhelming list, please add things here one-by-one so that I can knock them off. Also, I'm not sure what I'm meant to do with #91 - is it already implemented and needs fixing, or is it not implemented at all and I need to implement it? That looks like more work than I have time for right now.

[He3556]

I was looking at the code last week and found "contentText = "Hostile Service Area: Changing LAC Detected!";" line 597 in CellTracker.java

and on line 657 "tickerText= ...changig LAC" but ? i never saw a ticker text in out APP!?

... and "CHANGING LAC!!! - Current LAC: " on line 310 in
AIMSICDDbAdapter.java

I don't know when this happened and why + i can't find any information in the changelog, sorry

EDIT: well, it happened on 08.09.2014
Added: Initial Implementation of Detection Method 1: Changing LAC
So at least the part "CellID check" is missing. In the Issue #91 we started wit the "changing LAC" (see post from 08.Aug) - so this should be the part that is already implemented. But i had to look later, to be sure about it.
And later we added the "CellID check" into the flow chart - you see when you scroll down open

[E3V3A]

updated list with #132.

[SecUpwN]

@E3V3A, just merged the latest pull request. Are the other things from this list solved? If so, please close this Issue and I will be working hard to resolve #156. Biggest hurdle before opening our stores seems to be the missing private key for creating the fresh APK now. @tobykurien please leave your ideas regarding this hurdle in #156 so that we can continue there. Thank you everyone!

[E3V3A]

I don't know the status of (3), and (2) is not complete, due to #168.

[SecUpwN]

@E3V3A, please note that #65 must be completely solved until we go into BETA stage. Also, please grab a coffee and revalidate your open bugs with WIP-Internal v0.1.25-alpha-build-3. Thanks.

[E3V3A]

@He3556 Can you please review this and give some feedback. AFAICT, # (2) has it's own issue and the rest seem fixed or outdated/non-relevant?

[He3556]

yes i agree, let's close it