v134 - bugfixes, SIGNIFICANT_MOTION sensor, passive filter #1217
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…es used to acquire a fix. Issue #1207
Restore GeneralLocationListener.java
… save battery This uses the TYPE_SIGNIFICANT_MOTION sensor. https://developer.android.com/develop/sensors-and-location/sensors/sensors_motion#sensors-motion-significant "A significant motion is a motion that might lead to a change in the user's location; for example walking, biking, or sitting in a moving car." I have no idea how I overlooked this for 10 years. The significant motion detection is provided by the OS itself, so it could be completely 'off' for some devices. Issue #223 Issue #1199 Issue #807 Issue #1208
Add a Mime-version header. https://datatracker.ietf.org/doc/html/rfc2045#page-8 : "Messages composed in accordance with this document MUST include such a header field, with the following verbatim text: MIME-Version: 1.0 The presence of this header field is an assertion that the message has been composed in compliance with this document." Rspamd for example add a 2 score to mime mails missing this header.
Fix: reverted unintended change to the file.
Add passive data collection interval setting to prevent excessive data generation.
mendhak
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bugfix: Auto send alarm should get cancelled when logging stops. #1196
Bugfix: Ignore stale locations. This seems to happen when screen is off. #1224
Bugfix for FAQ activity on edge to edge layout for Android 15.
"Ignore battery optimization" is now mandatory because the OS starts killing services without it.
PR #1213 Adding passive location filter
PR #1218 Email bugfixes:
Experimental: Using significant motion sensor to prevent logging, to save battery
This uses the TYPE_SIGNIFICANT_MOTION sensor. https://developer.android.com/develop/sensors-and-location/sensors/sensors_motion#sensors-motion-significant
"A significant motion is a motion that might lead to a change in the user's location; for example walking, biking, or sitting in a moving car."
I have no idea how I overlooked this for 10 years.
The significant motion detection is provided by the OS itself, so it could be completely 'off' for some devices.
Issue #223
Issue #1199
Issue #807
Issue #1208
However in my testing I keep running into this issue, where it stops updating after a while. Making the whole thing useless, as now logging doesn't work at all.