Only load cells in range on map

[wvengen]

Currently all cells are loaded from the database and shown on the map view. This takes a lof of time when there are many cell points (ike from OCID). I suggest to add a where clause to the database query on a lat/lng window, and re-query when changing the view.

I can imagine that #272 would be solved by this as well.

[E3V3A]

The problem with "range" is that it could mean anything. Your phone could connect to towers 40+ km away... Not sure what to do here, but I guess once #215, #303 and subsequently #250 has been implemented it would be easier to deal with distant cells outside the view box.

[wvengen]

True. Though I fail to see why that would be an issue when showing the map - cells outside the view aren't shown anyway, right?

[SecUpwN]

Though I fail to see why that would be an issue when showing the map - cells outside the view aren't shown anyway, right?

Right. I added you to our Buildozer account to get the APK for testing. Please test and close if fixed.

[wvengen]

Thanks! I found it to be ok on the branch I was working on (local build), but I'll test again with the new APK.

[wvengen]

Works!

[E3V3A]

Which build are you using? The latest I just tested # 137 (issue #469) crashed, and Travis-CI shows failed build, so please state what you've tested and so on.

[SecUpwN]

@E3V3A, if #469 is now fixed for you and the latest build works, please test and close this. Thanks.

[E3V3A]

Unfortunately the side-effect of this PR is that the map view is wrong, laggy and unresponsive until DB query is updated. Not good.

[wvengen]

This will also be reverted in #541.

[E3V3A]

Please re-test this issue now. (Using Buildozer build >= 211)