Android class 2: derived directions + conversation views for 6 chat artifacts#926
Merged
Conversation
Validated against the 12-image Android test set:
- WhatsApp One-To-One and Group Messages: views only; both already emit
Message Direction ('Outgoing') and a stable thread column (other
participant / conversation name). ~10k real rows verified.
- Google Voice Messages: view only; Direction/Conversation ID verified in
test data ('Outgoing'/'Incoming').
- Teleguard: owner serverId from the service table 'user' row (same db,
same source as iOS); adds chatId as Chat ID. Validated 19/21 split with
blanks on ownerless service rows.
- Facebook Messenger (msys): local uid read from the threads_db2-uid file
(added to the artifact's paths); direction = sender_id == uid. Validated
across 3 images (e.g. 14 Outgoing / 12 Incoming).
- IMO: emits buid as Chat Partner (thread was previously only derivable by
From/To swap); direction already existed. buid populated 22/22 in test
data.
New columns appended; existing column order unchanged.
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
1 participant
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.
Summary
Android counterpart to iLEAPP #1647/#1648: evidence-derived directions and LAVA conversation views, all validated against the 12-image Android test set before implementation.
serverIdfromservicetable 'user' row (same db, same source as the iOS artifact) +chatId→ Chat IDthreads_db2-uid(glob added to artifact paths); direction =sender_id == uidget_fb_user_idbuidemitted as Chat Partner (real thread key); direction existedWhen direction can't be established (missing uid file / ownerless rows), the column stays blank — never defaulted.
Testing
pylint 10.00/10 on all 5 files; byte-compile; PluginLoader 6/6 views registered; view column refs validated; derivation SQL/logic executed read-only against the real copied databases with the splits above.
Still on the Android backlog (need deeper source digging)
Google Messages RCS (Bugle self-participant), TikTok Android, Google Chat (owner row), Discord Android, Teams, GroupMe.