Indoor Location new module #287
No reviewers
Labels
No Label
dependencies
info:feedback-needed
info:help-needed
prio:high
prio:low
prio:normal
status:confirmed
status:deferred
status:fix-committed
status:incomplete
status:in-progress
status:rejected
type:bug
type:discussion
type:feature
type:improvement
type:invalid
type:support
type:task
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Marown/SWADroid#287
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "develop"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What changes were proposed in this pull request?
Indoor Location based in WiFi signal power and mapping all physical addresses of routers in a center
How was this patch tested?
Manual testing in ETSIIT
Please review https://github.com/Amab/SWADroid/blob/develop/CONTRIBUTING.md before opening a pull request.
When the indoor location history is empty, the screen should be displayed with a message informing that the history is empty to prevent the user from thinking that a problem has occurred when loading the history.
Is the location history always downloaded from the server? If there is no connection to the server at the time the user checks the history, can't the history be checked?
What is the behavior of the indoor location in the following cases?
All these fields are already contained in the Location class. You can make
LocationTimestamp
extend fromLocation
to inherit those fields so you don't have to duplicate them.When you open the module, it closes immediately in some versions of Android:
java.lang.ClassNotFoundException: Didn't find class "android.view.View$OnUnhandledKeyEventListener"
)Update:
I have investigated the errors and they seem to have to do with the use of the
ACCESS_BACKGROUND_LOCATION
permission, which is only available from Android 10 (API 29) and higher. If this permission is removed, the module will work correctly in the three Android versions listed above.I think it would be necessary to remove the
@RequiresApi(api = Build.VERSION_CODES.Q)
annotation from theonStart
method of theIndoorLocation
class and manage the permissions taking into account that the application must run correctly in at least the three Android versions listed above.LGTM