MeWe#643
Merged
Merged
Conversation
Parses external.db located at com.android.providers.media
Contributor
Author
Collaborator
|
@charpy4n6 do you think we need to account for -SHM, -WAL for these? it doesn't appear we do currently |
Addresses changes with the databases and the application capabilities itself. Tested on my Life360 test data.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The application updated and the database related to MeWe messages is now called app_v3.db. It is in the same location and its tables and columns still match the original mewe.py.
mewe.py