Skip to content

feat(privacy): per-contact Always Single Tick and per-contact call blocking type - #877

Open
hozin-king wants to merge 1 commit into
Dev4Mod:masterfrom
hozin-king:feature/per-contact-privacy
Open

hozin-king wants to merge 1 commit into
Dev4Mod:masterfrom
hozin-king:feature/per-contact-privacy

Conversation

@hozin-king

Copy link
Copy Markdown

What this adds

Two per-contact options in the Custom Privacy dialog (per contact, independent of the global settings):

  1. Always Single Tick — a new toggle for one contact. When enabled, the sender always sees a single tick for messages sent to you from that contact only: both the delivered tick and the blue (read) tick are hidden for that contact. It does not follow the global Hide Delivered / Hide Blue Ticks settings and does not affect other contacts. Implemented as a new AlwaysSingleTick key in the per-contact privacy JSON, checked in HideSeen alongside the existing HideSeen / HideReceipt checks.

  2. Per-contact call blocking type — previously, Block Call in the per-contact dialog was only on/off and the blocking method always came from the global call type. Now, when Block Call is checked for a contact and OK is pressed, a type picker appears for that contact only: No internet (Calling), Busy, Not answered, or Unable to receive WhatsApp calls. The choice is saved as BlockCallType in the same per-contact JSON. CallPrivacy uses the per-contact type when set, and falls back to the global call type when it is unset, cancelled, or when Block Call is turned off for that contact.

Files changed

  • CustomPrivacy.kt — new dialog item, per-contact type picker (shown only when Block Call is checked), save/clear helpers for BlockCallType
  • HideSeen.kt — AlwaysSingleTick forces both receipt and seen hiding for that contact
  • CallPrivacy.kt — per-contact reject type with fallback to the global call type (both incoming-call hooks)
  • strings.xml / strings-id — EN and ID strings for Always Single Tick

Testing

Static checks only so far: edited files have balanced braces/parens and the string XMLs parse. Not yet tested on a device with a real WhatsApp install — happy to test further if the maintainer wants changes.

Based on upstream master 36c22aed (1.6.2).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant