How Jitter works, to the line of source.
- The gate
- decides whether you may be in an app at all. It stands at the door, and lets you in on a lease.
- Friction
- decides what a scroll costs while you are inside.
You open an app you have chosen to track.
Jitter gives you a few minutes in it, and you choose how many.
Coming back does not start you over: the minutes add up, and scrolling gets less reliable as they do.
It keeps building for hours, then the count goes back to zero.
Eventually every scroll stalls, and staying stops being worth it.
Nothing is blocked unless you ask, and you can always leave.
Two systems, and they do not talk.
The two share no state, and neither reads the other.
The lease runs on real elapsed time, not on time in the app, and it is checked at its deadline whether or not you are scrolling. Changing the system clock does not move it, and a reboot ends every lease.
Friction runs on each app’s accumulated foreground time inside the cycle. One number crosses between them, in one direction: the accumulated total at the moment a lease is granted, so that friction can find where “past the lease you took” begins in its own time.
A lease buys time in the app and nothing else. It never resets accumulated time and never lowers a stall. Gates are a toll, not a refund.
The door has a price, and it rises.
Jitter replaces your home screen. When you open an app you track, a black page comes up in front of it first: how long you have spent in it today, how many times you have opened it, and a countdown. Eight seconds the first time.

At zero you choose how long you are staying: 5, 10 or 15 minutes. There is no unlimited option. Each lease you take makes the next wait longer, twelve seconds, then sixteen, then twenty, up to thirty, for as long as the cycle lasts. Leaving costs nothing.

When the time runs out, the app goes to the background and the gate comes back.
You can also lock an app yourself, or every app you track. From the gate, when a lease runs out, you can block it for one, four or twelve hours, or a day; longer locks, up to thirty days, are set in settings, where the decision is calmer and a confirmation applies. Once a lock is set, nobody can lift it before it expires. There is no control for it anywhere in the app, and Jitter has no internet permission, so nothing can reach it from outside. The only way out is to turn Jitter off or uninstall it, and nothing in it tries to stop you.
Underneath all of it is a plain text home screen: your apps as words, and a command line.

Friction, in sequence.
- You scroll, and the app scrolls. The feed moves as it always does.
- Android then reports the scroll to Jitter’s accessibility service.
- Jitter rolls once against the friction curve for that app at that minute: a chance, not a schedule.
- On a hit, it arms a full-screen overlay for the length of the stall.
- While the overlay is armed it swallows every touch, taps included. Nothing is queued or replayed: a swipe made during a stall is gone.
- Then it disarms, and touches reach the app again.
A stall is the consequence of a scroll that worked, never the cause of one that failed.
While a stall is armed, a 2dp line runs along the top edge of the screen in grey, 0xFF8C8C96 at alpha 89 of 255. At the ceiling it turns red, 0xFFFF5555 at the same alpha: the one hue break in the app. No setting removes it, so you always know it is Jitter and not your phone failing.
Four taps inside the top-left 64dp of the screen within a second and a half release a stall at once.
The cost of staying.
What changes is what each scroll costs. Friction is a function of two numbers: the time you have spent in the app this cycle, and the penalty for staying past a lease you took. Below 40% of the app’s horizon it is zero, and past the horizon it stays at the ceiling. In between, the longer you stay, the longer a stall lasts and the more often one comes.
| Time in the app | Stall | Chance a scroll stalls | In other words |
|---|---|---|---|
| 10 min | 450 ms | 10% | one scroll in ten stalls, for under half a second |
| 20 min | 2950 ms | 91.3% | about nine scrolls in ten stall, for about three seconds |
| 25 min | 5000 ms | 100% | every scroll stalls, for five seconds |
Three points from the curve, not the whole of it. Friction begins at ten minutes, 40% of the default horizon. The twenty-minute figures are interpolated, not stated in the source. All three assume the default 25-minute horizon, which is set per app, from ten minutes to sixty.
Around sixteen minutes a stall is more than a second, on seven scrolls in ten.
No stall shorter than 450 milliseconds is commanded. It sits just above 406 milliseconds, a delay measured on one phone, below which a stall arrives after the scroll it was meant for and is never felt.
Five seconds is the longest stall, at the default horizon, on every scroll. However stalls follow one another, the overlay is never armed for more than eight seconds in a row.
The horizon and the cycle.
Each tracked app has a horizon: the length of session it is for. The offered steps are 10, 15, 18, 20, 25, 30, 40, 50 and 60 minutes, and a newly tracked app gets 25.
Friction starts at 40% of the horizon: at four minutes on the shortest, at twenty-four on the longest. Above the default the ceiling tapers, linearly from 25 to 60 minutes, down to three seconds on seven scrolls in ten.
| Horizon | Friction starts | Ceiling stall | Ceiling chance |
|---|---|---|---|
| 10 min, the shortest | 4 min | 5000 ms | 100% |
| 25 min, the default | 10 min | 5000 ms | 100% |
| 60 min, the longest | 24 min | 3000 ms | 70% |
Narrowing a horizon applies at once. Widening one waits for the next cycle, and takes a trip to settings and a confirmation first: a wider horizon is relief, and relief does not arrive on demand. Setting it back to the current value is the only way to cancel a pending widen.
Time is counted per app, and kept.
Each app’s time is its own, counted while it is in the foreground. If Jitter is killed mid-session, usage access replays the app’s resumed and paused events so that the time is not lost.
The cycle starts the first time you open a tracked app from a clean state and ends six hours later, whether you kept using the apps or not. There is no setting for it.
Inside the cycle nothing goes down. Leaving and coming back does not reset an app’s minutes: minute eleven, home, reopen, minute eleven. At the rollover the minutes, the leases and the penalty go to zero and a pending wider horizon takes effect. Locks are not part of it.
Overdue minutes count twice.
Take a lease and stay in the app past it, and every further minute in that app is charged again as penalty, on top of the minute itself. Only minutes in the app count; time anywhere else costs nothing. With no lease taken, nothing accrues.
Ignore a five-minute lease completely and the curve reaches its ceiling at fifteen real minutes instead of twenty-five: five minutes inside the lease, then ten more that count as twenty.
The penalty only ever grows. It does not come back down until the cycle ends.
What Jitter does not do.
Jitter runs as an Android accessibility service. That is a serious permission.
It never reads the screen. canRetrieveWindowContent="false" in the service configuration. Android’s documentation says a service must declare that capability to retrieve a window’s content.
app/
It cannot tap or swipe for you. canPerformGestures="false", and Android’s documentation says a service must declare that capability to dispatch gestures. The one action it takes is Home, to send an app back behind the gate.
app/
It asks only about the apps you pick. The service’s package list is your targets and Jitter itself, re-pushed when you change it.
app/
There is no network. No INTERNET permission in the manifest.
app/
Every permission Jitter requests, and nothing else: usage access, activity recognition for the optional movement gate, boot completed to re-arm reminders, vibrate, and exact alarms for reminders. ReadmePermissionsTest fails the build if that list and the manifest ever differ.
app/
A stall also lets go when the screen turns off, when you leave the app, and when a call arrives.
app/
There is also a pause. CFG, Safety, Pause friction (15m) stops stalls, gates and overlays for fifteen minutes, for the times something else needs the screen. It is not a reset: the clock keeps running underneath, locks stay locked, and the friction comes back on its own.
app/
Payment apps are never drawn over. Touches that pass through an overlay are flagged as obscured, and a payment app can check that flag and refuse them, so the set of sensitive packages outranks even a lock.
Jitter will never ask you for a PIN, a password, an OTP or any banking detail. The one link out is a report-a-problem row that hands the issue tracker to your browser. Anything claiming to be Jitter that asks for a credential is not Jitter.
app/
Every permission and service flag, and what each is for
PACKAGE_USAGE_STATS- Usage access. Replays
ACTIVITY_RESUMEDandACTIVITY_PAUSEDafter a process death, so a session’s time is not lost. ACTIVITY_RECOGNITION- The step sensor for the optional movement gate. Without it the gate falls back to motion analysis.
RECEIVE_BOOT_COMPLETED- Re-arms pending
$ remalarms after a reboot. VIBRATE$ remvibrates once when the ringer is on vibrate.USE_EXACT_ALARM- Lets
$ remuse exact alarms on Android 13 and later. SCHEDULE_EXACT_ALARM- The same on Android 12 and 12L, where the system or you can revoke it; capped at
maxSdkVersion="32".
Not requested: READ_PHONE_STATE (the call check uses AudioManager), QUERY_ALL_PACKAGES, SYSTEM_ALERT_WINDOW, INTERNET, POST_NOTIFICATIONS (nothing posts a notification, $ rem included) and HIGH_SAMPLING_RATE_SENSORS. ReadmePermissionsTest fails the build if this list and the manifest differ.
accessibilityEventTypestypeViewScrolled|: that a scroll happened and which window is in front. Nothing else.typeWindowStateChanged| typeWindowsChanged canRetrieveWindowContentfalse. Android’s documentation says a service must declare this capability to retrieve a window’s content.canPerformGesturesfalse. Android’s documentation says a service must declare this capability to dispatch gestures, such as a tap or a swipe.isAccessibilityToolfalse. It does not declare itself an accessibility tool.notificationTimeout0, so a burst of scrolls is not coalesced into one event.packageNames- Your tracked apps and Jitter itself, re-pushed when you change them: the packages it asks Android for events from.
Every claim, to its line.
Every number on this page is the number in the app’s source at commit f9b5b9f, and the table below cites each one to its file and line. It is dense on purpose: it is for checking, not for persuading.
What the published APK declares, as aapt prints it:
$ aapt dump badging jitter-v1.0.3.apk | grep "^package" package: name='org.jitteros.app' versionCode='10003' versionName='1.0.3' platformBuildVersionName='16' platformBuildVersionCode='36' compileSdkVersion='36' compileSdkVersionCodename='16' $ aapt dump permissions jitter-v1.0.3.apk package: org.jitteros.app uses-permission: name='android.permission.PACKAGE_USAGE_STATS' uses-permission: name='android.permission.ACTIVITY_RECOGNITION' uses-permission: name='android.permission.RECEIVE_BOOT_COMPLETED' uses-permission: name='android.permission.VIBRATE' uses-permission: name='android.permission.USE_EXACT_ALARM' uses-permission: name='android.permission.SCHEDULE_EXACT_ALARM' maxSdkVersion='32' permission: org.jitteros.app.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION uses-permission: name='org.jitteros.app.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION' $ aapt dump badging jitter-v1.0.3.apk | grep INTERNET $
The last permission in the aapt output, DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION, is added by the AndroidX library Jitter is built with, for a receiver that is not exported; it is not in Jitter’s manifest.
The source is public under GPL-3.0-or-later.
249 rows, each held to its line at f9b5b9f by tools/check-trace.sh before every deploy.
| § | Claim | Source | Symbol | Value |
|---|---|---|---|---|
| 14 | ... 91.3% of scrolls stall, for 2950 ms: between the knot at(18.0) | app/ | Knot(at(18.0), 2700, 0.90f) | f = (20 - 10) / 15 = 2/3, past 12/19 |
| 13 | 5: while armed it swallows every touch | app/ | Swallows every touch. | FLAG_NOT_TOUCHABLE removed while armed |
| 16 | No INTERNET permission in the manifest | app/ | INTERNET stays out | absent |
All 249 rows, by section
| § | Claim | Source | Symbol | Value |
|---|---|---|---|---|
| 1 | "Jitter never blocks anything you didn't ask it to." Tracked apps are never blocked by the friction | README.md:6 | are never | "are never / blocked", lines 6-7 (reflowed upstream) |
| 1 | ... "never blocked", the second line of the sentence | README.md:7 | blocked: the longer you stay | "blocked:" |
| 1 | ... you didn't ask it to: a lock is set by the user, from an hour to thirty days | app/ | val STEPS_MS | 1h, 4h, 12h, 1d, 3d, 7d, 14d, 30d |
| 1 | ... you didn't ask it to: [ BLOCK THIS APP ] on the lease-expired gate | app/ | [ BLOCK THIS APP ] | user-chosen block |
| 1 | An Android launcher | README.md:5 | home screen | "a home screen and a set of speed bumps for Android" |
| 1 | Hero panel: a stall follows a scroll that has already happened. Android reports the scroll to the service after the app performed it | app/ | AccessibilityEvent.TYPE_VIEW_SCROLLED -> WindowEvent.Kind.VIEW_SCROLLED | the scroll event, not the gesture |
| 1 | ... the service asks the friction engine on that scroll | app/ | engine.onScroll(pkg, now()) | per scroll event |
| 1 | ... which rolls once against the curve (a Bernoulli trial) | app/ | FrictionCurve.shouldStall(friction, roll()) | roll = Random.nextFloat() |
| 1 | ... a hit when the roll is under the curve's probability | app/ | roll < point.probability | stall only if stallMs > 0 and roll < p |
| 1 | ... and on a hit the full-screen overlay is armed for the stall | app/ | val armed = shutter.arm( | arm(ms = decision.stallMs) |
| 1 | Hero panel: while armed the overlay swallows every touch | app/ | Swallows every touch. | FLAG_NOT_TOUCHABLE removed while armed |
| 1 | ... taps included: every touch event is consumed, none is passed on or queued | app/ | override fun onTouchEvent(event: MotionEvent): Boolean | returns true for every action while armed (line 507) |
| 1 | ... (the consuming return) | app/ | return true | consumed |
| 1 | Hero panel: never armed for more than eight seconds in a row | app/ | MAX_CONTINUOUS_ARMED_MS = 8_000L | 8 s |
| 1 | ... the ceiling holds whatever the tier or the scroll rate | app/ | never armed for more than 8 s continuously | quoted |
| 1 | Hero panel: the tell is grey | app/ | TELL_COLOR = 0xFF8C8C96 | 0xFF8C8C96; red is the terminal tier only (line 437), which the panel never reaches |
| 1 | Small print: default settings: the default horizon | app/ | DEFAULT_HORIZON_MS | 25 min |
| 1 | ... friction starts at 40% of it: ten minutes | app/ | ONSET_FRACTION | 0.40 x 25 = 10 min |
| 1 | ... the horizon is per app, from ten minutes | app/ | MIN_HORIZON_MS | 10 min |
| 1 | ... to sixty | app/ | MAX_HORIZON_MS | 60 min |
| 1 | At ten minutes, one scroll in ten stalls | app/ | Knot(at(6.0), 150, 0.10f) | at 10 min the ramp fraction f = (10 - 10) / (25 - 10) = 0: the first knot, p 0.10 |
| 1 | ... for half a second: its 150 ms is raised to the floor | app/ | private fun clampFloor( | max(150, 450) = 450 ms |
| 1 | ... the floor: no non-zero stall below 450 ms | app/ | DEFAULT_FLOOR_MS | 450 |
| 1 | At twenty: the knots sit on the source table's own 6-to-25 scale, not on real minutes | app/ | private fun at(minute: Double) | at(m) = (m - 6) / 19, a fraction of the onset-to-horizon ramp; on the default horizon at(18) = 12/19 lands at 10 + 15 x 12/19 = 19.47 real minutes, at(22) = 16/19 at 22.63 |
| 1 | ... nine in ten stall for three: between the knot at(18.0) | app/ | Knot(at(18.0), 2700, 0.90f) | f = (20 - 10) / 15 = 2/3, past 12/19 |
| 1 | ... and the knot at(22.0) | app/ | Knot(at(22.0), 4200, 0.98f) | t = (2/3 - 12/19) / (16/19 - 12/19) = 1/6; 2700 + 1500 x 1/6 = 2950 ms; 0.90 + 0.08 x 1/6 = 0.913 (verify-curve.py: 2950 ms, 91.3%) |
| 1 | At twenty-five (the horizon, not stated in the panel): five seconds | app/ | TERMINAL_STALL_MS | 5000 |
| 1 | ... on every scroll | app/ | TERMINAL_PROBABILITY = | 1.00f |
| 1 | Closing: "Jitter doesn't block you." | README.md:6 | are never | the claim above it, restated |
| 1 | Closing: "It makes staying harder." | README.md:105 | only ever | "Within a cycle the friction only ever increases" |
| 2 | By default, your first ten minutes in an app cost nothing | app/ | DEFAULT_HORIZON_MS | 25 min |
| 2 | By default, your first ten minutes in an app cost nothing | app/ | ONSET_FRACTION | 0.40 x 25 = 10 min |
| 2 | The app ignores your finger | README.md:55 | touches in that app do nothing | blackout |
| 2 | 450 milliseconds | app/ | DEFAULT_FLOOR_MS | 450 |
| 2 | At first, about one scroll in ten | app/ | Knot(at(6.0) | p 0.10 at onset (its 150 ms is clamped to the 450 floor) |
| 2 | At twenty-five minutes, five seconds | app/ | TERMINAL_STALL_MS | 5000 |
| 2 | on every scroll | app/ | TERMINAL_PROBABILITY = | 1.00f |
| 2 | Across a six-hour cycle | app/ | WINDOW_MS | 6 h |
| 2 | Counted for each app; leaving and coming back does not reset them | app/ | accumulatedMs = 0 | per-app snapshot, zeroed only here, at rollover (the only assignment in app/src/main) |
| 2 | Inside that cycle they only go up | README.md:105 | only ever | "Within a cycle the friction only ever increases" |
| 2 | A scroll goes through, then stalls: Android reports the scroll after the app performed it | app/ | AccessibilityEvent.TYPE_VIEW_SCROLLED -> WindowEvent.Kind.VIEW_SCROLLED | the scroll event, not the gesture |
| 2 | ... and on a hit the overlay is armed | app/ | val armed = shutter.arm( | arm(ms = decision.stallMs) |
| 2 | The app ignores your finger, taps included | app/ | override fun onTouchEvent(event: MotionEvent): Boolean | returns true for every action while armed |
| 2 | ... (the consuming return) | app/ | return true | consumed |
| 2 | At the default settings: 20 minutes, nine in ten, for nearly three seconds: the knots on the source table's 6-to-25 scale | app/ | private fun at(minute: Double) | at(m) = (m - 6) / 19; at(18) lands at 19.47 real minutes on the default horizon, at(22) at 22.63 |
| 2 | ... between at(18.0) | app/ | Knot(at(18.0), 2700, 0.90f) | f = (20 - 10) / 15 = 2/3 |
| 2 | ... and at(22.0) | app/ | Knot(at(22.0), 4200, 0.98f) | t = 1/6: 2950 ms (nearly three seconds), 0.913 (nine in ten) |
| 3 | Android 11 and later | app/ | minSdk | 30 |
| 3 | Plain step: download the APK | README.md:165 | Download the APK | quoted |
| 3 | Plain step: Android asks you to let your browser install apps | README.md:175 | install unknown apps | quoted |
| 3 | Plain step: Play Protect may warn you or block the install | README.md:178 | If Play Protect blocks | quoted |
| 3 | Plain step: Android may block the accessibility switch until you allow restricted settings (it did on Android 16) | README.md:183 | Restricted settings (Android 13 and later) | quoted |
| 3 | Plain step: then accessibility and usage access | README.md:190 | accessibility, usage access | quoted |
| 3 | Plain step: your old launcher stays installed; switch back any time | README.md:262 | Default apps, Home app | quoted |
| 3 | Flow 1, check: its SHA-256 matches the one on the release page | README.md:168 | SHA-256, and yours should match exactly | quoted |
| 3 | Flow 2, check: opening Jitter shows its SETUP screen (shown until setup is complete) | app/ | shown until setup is complete | the first-run flow |
| 3 | ... its SETUP screen | app/ | name="onboarding_title">SETUP | SETUP |
| 3 | Flow 3, check: a satisfied step shows [✓] | app/ | name="setup_mark_done" | [✓] |
| 3 | ... ACCESSIBILITY, satisfied only when the service is working | app/ | Step.ACCESSIBILITY -> facts.serviceWorking | detected |
| 3 | ... USAGE ACCESS | app/ | Step.USAGE_ACCESS -> facts.usageAccess | detected |
| 3 | Flow 4, check: HOME APP shows [✓] when Jitter is the default home app | app/ | Step.HOME -> facts.defaultHome | detected |
| 3 | ... HOME APP | app/ | name="onboarding_home_name">HOME APP | HOME APP |
| 3 | Jitter is sideloaded: the download is the APK attached to a GitHub release | worker/ | const PINNED_APK | the jitter-v1.0.3.apk release asset |
| 3 | Each release page lists the file's SHA-256 | README.md:168 | SHA-256 | quoted |
| 3 | certutil -hashfile jitter-v1.0.3.apk SHA256 | README.md:170 | certutil -hashfile jitter-v1.0.3.apk SHA256 | verbatim |
| 3 | shasum -a 256 jitter-v1.0.3.apk | README.md:171 | shasum -a 256 jitter-v1.0.3.apk | verbatim |
| 3 | sha256sum jitter-v1.0.3.apk | README.md:172 | sha256sum jitter-v1.0.3.apk | verbatim |
| 3 | More details / Install anyway | README.md:178 | Install anyway | quoted |
| 3 | There is no way around a block from inside Jitter | README.md:179 | no in-app way around | quoted |
| 3 | App info, three-dot menu; on other phones the menu item may read Allow restricted settings | README.md:185 | three-dot menu | quoted |
| 3 | Jitter's setup guide walks through this too | README.md:186 | setup guide walks | quoted |
| 3 | Two of the things it warns about are switched off (retrieve window content) | app/ | canRetrieveWindowContent="false" | false |
| 3 | ... (tap or swipe for you) | app/ | canPerformGestures="false" | false |
| 3 | What it does use the permission for is knowing which app is in front | README.md:205 | It sees which app is in front | quoted |
| 3 | Instagram, X, YouTube and Snapchat by default | app/ | val DEFAULT_TARGETS: List<String> = DefaultTargets.CURRENT | the defaults are DefaultTargets.CURRENT |
| 3 | ... Instagram, X and YouTube | app/ | val BEFORE_SNAPCHAT | com.instagram.android, com.twitter.android, com.google.android.youtube (lines 23-25) |
| 3 | ... and Snapchat | app/ | val CURRENT: List<String> = BEFORE_SNAPCHAT + "com.snapchat.android" | 4 packages |
| 3 | You can switch back any time in Android's settings | README.md:262 | Default apps, Home app | quoted |
| 3 | Untracking waits two and a half minutes | app/ | DURATION_MS | 150_000 |
| 3 | Instagram, Facebook, X, TikTok, Snapchat (named) | README.md:125 | TikTok, Snapchat | quoted |
| 3 | and any app that declares itself a social app | app/ | CATEGORY_SOCIAL | the app's own declared category, read by Jitter |
| 3 | after three days, or at the next restart if that is sooner | README.md:126 | at the next restart | quoted |
| 3 | after three days | app/ | GRACE_DAYS | 3 |
| 3 | Old tester build (dev.molasses): uninstall it first | README.md:196 | Moving from the old tester build | quoted |
| 3 | Jitter is not on Google Play; you install the APK yourself | README.md:162 | It is not on the Play Store | quoted |
| 4 | Footer: Jitter 1.0.3 | gradle/ | appVersion = "1.0.3" | 1.0.3 |
| 4 | Footer: Android 11 and later | app/ | minSdk | 30 = Android 11 |
| 4 | Footer: open source under GPL-3.0-or-later | README.md:11 | GPL--3.0--or--later | the licence badge |
| 4 | The app's issue tracker, the address its report-a-problem row opens | app/ | ISSUES_URL | https://github.com/keerthanpragnay1728-prog/jitter/issues |
| § | Claim | Source | Symbol | Value |
|---|---|---|---|---|
| 11 | Plain layer: an app you have chosen to track | app/ | val DEFAULT_TARGETS | defaults; you pick |
| 11 | Plain layer: a few minutes in it, and you choose how many | app/ | OFFERED_MS | 5, 10, 15 min |
| 11 | Plain layer: coming back does not start you over; the minutes add up | app/ | accumulatedMs = 0 | zeroed only at rollover |
| 11 | Plain layer: scrolling gets less reliable as they do | README.md:105 | only ever | "Within a cycle the friction only ever increases" |
| 11 | Plain layer: it keeps building for hours, then the count goes back to zero | app/ | WINDOW_MS | 6 h |
| 11 | Plain layer: eventually every scroll stalls | app/ | TERMINAL_PROBABILITY = | 1.00f |
| 11 | Plain layer: nothing is blocked unless you ask | README.md:6 | are never | "are never / blocked", lines 6-7 (reflowed upstream) |
| 11 | ... the second line of the sentence | README.md:7 | blocked: the longer you stay | "blocked:" |
| 11 | The lease and friction share no state; neither reads the other | README.md:1151 | share no state | quoted |
| 11 | The lease runs on real elapsed time, checked at its deadline | README.md:344 | A lease runs on real elapsed time | quoted |
| 11 | Changing the system clock does not move it | README.md:347 | system clock does not move it | quoted |
| 11 | A reboot ends every lease | README.md:347 | a reboot ends every lease | quoted |
| 11 | One number crosses, in one direction: the accumulated total at the grant | README.md:1154 | One number crosses | quoted |
| 11 | A lease never resets accumulated time, never lowers a stall; a toll, not a refund | README.md:353 | Gates are a toll | quoted |
| 11 | Block 1, the contrast: the gate decides whether you may be in an app at all | README.md:1149 | System A is the lease | "permission to be in an app" |
| 11 | ... it stands at the door, and lets you in on a lease | README.md:155 | What stands in front of a tracked app | the lease gate |
| 11 | Friction decides what a scroll costs while you are inside | README.md:1150 | System B is friction | "accumulated foreground time, which decides what a scroll costs" |
| 12 | Jitter replaces your home screen | README.md:5 | home screen | a home screen |
| 12 | A black page in front of it: time today, times opened, a countdown | README.md:72 | full-screen black page | the gate |
| 12 | Eight seconds the first time | app/ | FIRST_MS | 8_000 |
| 12 | 5, 10 or 15 minutes (text and plate 02 caption) | app/ | OFFERED_MS | 5, 10, 15 min |
| 12 | There is no unlimited option | README.md:82 | There is no unlimited option | quoted |
| 12 | Twelve seconds, then sixteen, then twenty | app/ | STEP_MS | 4_000 |
| 12 | up to thirty | app/ | CAP_MS | 30_000 |
| 12 | for as long as the cycle lasts; leaving costs nothing | README.md:99 | Backing out costs nothing | only leases taken lengthen it |
| 12 | When the time runs out, the app goes to the background and the gate comes back | README.md:86 | goes home under the gate | lease expiry |
| 12 | Lock an app, or every app you track | README.md:35 | Locks you cannot undo | "Lock an app, or every tracked app" |
| 12 | From the gate, when a lease runs out, up to a day | app/ | const val CAP_MS | 24 h, offered on the lease-expired gate only |
| 12 | From settings, for up to thirty days | app/ | 30 * DAY | MAX_MS |
| 12 | Nobody can lift it before it expires; no control for it anywhere in the app | app/ | There is no unlock control | "at any depth" |
| 12 | Nobody can lift it before it expires | app/ | There is deliberately no unlock | no unlock in the store |
| 12 | Nothing can reach it from outside: Jitter has no internet permission | app/ | INTERNET stays out | no INTERNET uses-permission |
| 12 | The only way out is to turn Jitter off or uninstall it | README.md:44 | uninstall | "You can always turn off its accessibility service or uninstall it" |
| 12 | and nothing in it tries to stop you | README.md:45 | nothing in it tries to stop you | quoted |
| 12 | for as long as the cycle lasts: the count resets with the cycle | README.md:100 | The count resets when the | quoted |
| 12 | Block from the gate for one, four or twelve hours, or a day | app/ | val RUNGS_MS | 1h, 4h, 12h, 1d |
| 12 | Longer locks are set in settings, where a confirmation applies | app/ | confirmation step applies | quoted |
| 12 | A plain text home screen: your apps as words, and a command line | README.md:38 | A console launcher | console |
| 13 | So you always know it is Jitter | README.md:60 | thin grey | "So you can always tell it is us" |
| 13 | At the ceiling it turns red: the terminal tier, effective time at or past the horizon | app/ | fun isTerminal | effective time >= horizon |
| 13 | Four taps | app/ | PANIC_TAPS | 4 |
| 13 | within a second and a half | app/ | PANIC_WINDOW_MS | 1_500 |
| 13 | in the top-left corner | README.md:65 | top-left corner | quoted |
| 13 | A 2dp line along the top edge | app/ | TELL_DP | 2f |
| 13 | grey, 0xFF8C8C96 | app/ | TELL_COLOR | 0xFF8C8C96 |
| 13 | at alpha 89 of 255 | app/ | TELL_ALPHA | 89 |
| 13 | At the ceiling it turns red, 0xFFFF5555 | app/ | TELL_COLOR_TERMINAL | 0xFFFF5555 |
| 13 | the one hue break in the app | app/ | The one hue break | quoted |
| 13 | Four taps inside the top-left 64dp | app/ | PANIC_REGION_DP | 64f |
| 13 | 1-2: you scroll and the app scrolls; Android then reports the scroll to the service | app/ | AccessibilityEvent.TYPE_VIEW_SCROLLED -> WindowEvent.Kind.VIEW_SCROLLED | the scroll event, after the app performed it |
| 13 | 3: Jitter asks the friction engine on that scroll | app/ | engine.onScroll(pkg, now()) | per scroll event |
| 13 | ... and rolls once: a chance, not a schedule | app/ | FrictionCurve.shouldStall(friction, roll()) | roll = Random.nextFloat() |
| 13 | ... a hit when the roll is under the curve's probability | app/ | roll < point.probability | stall only if stallMs > 0 and roll < p |
| 13 | 4: on a hit, a full-screen overlay is armed for the length of the stall | app/ | val armed = shutter.arm( | arm(ms = decision.stallMs) |
| 13 | 5: while armed it swallows every touch | app/ | Swallows every touch. | FLAG_NOT_TOUCHABLE removed while armed |
| 13 | ... taps included; nothing is queued or replayed | app/ | override fun onTouchEvent(event: MotionEvent): Boolean | every action consumed while armed |
| 13 | ... (the consuming return) | app/ | return true | consumed |
| 13 | 6: then it disarms, at the end of the stall | app/ | val target = minOf(now + ms, ceiling) | armed until now + stall, capped at the 8 s ceiling |
| 14 | Around sixteen minutes, more than a second, on seven scrolls in ten | app/ | Knot(at(14.0) | 1202 ms / 0.70 at minute 16.32; 1120 ms / 0.68 at 16.0 (verify-curve.py) |
| 14 | 450ms, the shortest stall | app/ | DEFAULT_FLOOR_MS | 450 |
| 14 | Just above a delay measured on one phone, 406 milliseconds | app/ | MEASURED_SEGMENT_D_P50_MS | 406 |
| 14 | measured on one phone | app/ | reference device | "on the reference device" |
| 14 | below which a stall arrives after the scroll it was meant for and is never felt | app/ | never felt | quoted |
| 14 | 5s; at the default horizon | app/ | TERMINAL_STALL_MS | 5000 |
| 14 | every scroll stalls | app/ | TERMINAL_PROBABILITY = | 1.00f |
| 14 | Never armed for more than eight seconds in a row | app/ | MAX_CONTINUOUS_ARMED_MS | 8_000 |
| 14 | Friction reads two numbers: time this cycle plus penalty | app/ | fun effectiveMs | accumulated + penalty |
| 14 | Below 40% of the horizon it is zero | app/ | if (accumulatedMs < onset) | 0 ms, 0% |
| 14 | Past the horizon both stay at the ceiling | app/ | if (accumulatedMs >= horizon) | ceiling |
| 14 | No stall shorter than 450 milliseconds is commanded | app/ | private fun clampFloor( | max(stall, floor) |
| 14 | At the default 25-minute horizon | app/ | DEFAULT_HORIZON_MS | 25 min |
| 14 | ... friction starts at 40% of it: ten minutes | app/ | ONSET_FRACTION | 0.40 x 25 = 10 min |
| 14 | 10 minutes: one scroll in ten stalls | app/ | Knot(at(6.0), 150, 0.10f) | f = 0 at 10 min: the first knot, p 0.10 |
| 14 | ... for 450 ms: its 150 ms raised to the floor | app/ | private fun clampFloor( | max(150, 450) = 450 ms |
| 14 | 20 minutes: the knots sit on the source table's own 6-to-25 scale, not on real minutes | app/ | private fun at(minute: Double) | at(m) = (m - 6) / 19, a fraction of the onset-to-horizon ramp; on the default horizon at(18) = 12/19 lands at 10 + 15 x 12/19 = 19.47 real minutes, at(22) = 16/19 at 22.63 |
| 14 | ... 91.3% of scrolls stall, for 2950 ms: between the knot at(18.0) | app/ | Knot(at(18.0), 2700, 0.90f) | f = (20 - 10) / 15 = 2/3, past 12/19 |
| 14 | ... and the knot at(22.0) | app/ | Knot(at(22.0), 4200, 0.98f) | t = (2/3 - 12/19) / (16/19 - 12/19) = 1/6; 2700 + 1500 x 1/6 = 2950 ms; 0.90 + 0.08 x 1/6 = 0.913 (verify-curve.py: 2950 ms, 91.3%) |
| 14 | 25 minutes: every scroll stalls, for 5000 ms | app/ | TERMINAL_STALL_MS | 5000 |
| 14 | ... every scroll | app/ | TERMINAL_PROBABILITY = | 1.00f |
| 14 | In between, the longer you stay, the longer a stall lasts and the more often one comes | README.md:105 | only ever | "Within a cycle the friction only ever increases" |
| 14 | Qualification: the twenty-minute figures are interpolated, not stated in the source | app/ | fun frictionAt( | interpolates between control points; none at 20 min (they fall at 19.47 and 22.63 min, rows above) |
| 14 | Qualification: the default horizon is set per app | app/ | listOf(10L, 15L, 18L, 20L, 25L, 30L, 40L, 50L, 60L) | 9 steps |
| 14 | ... from ten minutes | app/ | MIN_HORIZON_MS | 10 min |
| 14 | ... to sixty | app/ | MAX_HORIZON_MS | 60 min |
| 15 | 25m, the default horizon | app/ | DEFAULT_HORIZON_MS | 25 min |
| 15 | the length of session an app is for | README.md:23 | the length of session it is for | quoted |
| 15 | from ten minutes | app/ | MIN_HORIZON_MS | 10 min |
| 15 | to sixty | app/ | MAX_HORIZON_MS | 60 min |
| 15 | A trip to settings, a confirmation, and a wait for the next cycle | app/ | a wait for the next cycle | quoted |
| 15 | 6h, the cycle | app/ | WINDOW_MS | 6 h |
| 15 | It starts the first time you open an app you track | README.md:119 | from a clean state | cycle anchor |
| 15 | the minutes ... go back to zero | app/ | accumulatedMs = 0 | rollover |
| 15 | the leases ... go back to zero | app/ | leasesTaken = 0 | rollover |
| 15 | the waits ... go back to zero | README.md:100 | The count resets when the | gate length resets with the cycle |
| 15 | There is no setting for it | README.md:120 | There is no setting | quoted |
| 15 | and it never ends a lock | app/ | Stored locks are deadlines | locks are deadlines, outside the rollover |
| 15 | and it never ends a lock | app/ | no lock changes state | only expiry drops a lock |
| 15 | Offered horizons: 10, 15, 18, 20, 25, 30, 40, 50, 60 minutes | app/ | listOf(10L, 15L, 18L, 20L, 25L, 30L, 40L, 50L, 60L) | 9 steps |
| 15 | Friction starts at four minutes on the shortest | README.md:335 | 10 min (minimum) | 4 min |
| 15 | ... at twenty-four on the longest, three seconds on seven scrolls in ten | README.md:337 | 60 min (maximum) | 24 min, 3000 ms, 70% |
| 15 | The ceiling tapers linearly from 25 | app/ | TAPER_FROM_HORIZON_MS = DEFAULT_HORIZON_MS | 25 min |
| 15 | ... to 60 minutes | app/ | TAPER_TO_HORIZON_MS = 60L * 60 * 1000 | 60 min |
| 15 | Three seconds | app/ | TERMINAL_STALL_TAPERED_MS | 3000 |
| 15 | seven scrolls in ten | app/ | TERMINAL_PROBABILITY_TAPERED | 0.70f |
| 15 | Widening waits for the next cycle | app/ | stored as pending | promoted at rollover |
| 15 | Narrowing applies at once | app/ | A narrow applies immediately | quoted |
| 15 | Setting it back is the only way to cancel a pending widen | app/ | A request equal to the current horizon cancels | quoted |
| 15 | Each app's time is counted while it is in the foreground | README.md:318 | accumulated foreground time | quoted |
| 15 | Usage access replays resumed and paused events after a process death | README.md:216 | Replays | quoted |
| 15 | At the rollover the minutes go to zero | app/ | accumulatedMs = 0 | 0 |
| 15 | ... the leases | app/ | leasesTaken = 0 | 0 |
| 15 | ... and the penalty | app/ | penaltyMs = 0 | 0 |
| 15 | A pending wider horizon takes effect | app/ | HorizonPolicy.promote | promote |
| 15 | Every overdue minute in the app is charged again as penalty; time elsewhere costs nothing | app/ | overdue minutes count double | quoted |
| 15 | With no lease taken, nothing accrues | app/ | if (app.leasesTaken > 0) | guard |
| 15 | Ceiling at fifteen real minutes instead of twenty-five | app/ | fifteen real minutes | quoted |
| 15 | The penalty only ever grows | app/ | Monotonic by construction | quoted |
| 16 | It never reads the screen: canRetrieveWindowContent="false" | app/ | canRetrieveWindowContent="false" | false |
| 16 | It cannot tap or swipe for you: canPerformGestures="false" | app/ | canPerformGestures="false" | false |
| 16 | The one action it takes is Home, to send an app back behind the gate | app/ | performGlobalAction(GLOBAL_ACTION_HOME) | the only global action |
| 16 | The package list is your targets and Jitter itself | app/ | android:packageNames= | targets plus org.jitteros.app |
| 16 | ... and re-pushed when you change it | app/ | re-pushed via | setServiceInfo() |
| 16 | No INTERNET permission in the manifest | app/ | INTERNET stays out | absent |
| 16 | Every permission, and nothing else (usage, activity recognition, boot, vibrate, exact alarms) | app/ | PACKAGE_USAGE_STATS | first uses-permission |
| 16 | ReadmePermissionsTest fails the build if the list and the manifest differ | README.md:214 | ReadmePermissionsTest | quoted |
| 16 | A stall lets go when the screen turns off, you leave the app, a call arrives | README.md:67 | releases when the screen turns off | quoted |
| 16 | Pause friction (15m) | app/ | Pause friction (15m) | UI string |
| 16 | for fifteen minutes | app/ | DURATION_MS | 15 min |
| 16 | stops stalls, gates and overlays | app/ | A pause suspends graduated friction, stalls | friction, stalls, checkpoints |
| 16 | locks stay locked | app/ | paused -> Decision.Enforce | lock enforced while paused |
| 16 | The one link out is a report-a-problem row that hands the issue tracker to your browser | app/ | fun spec() | ACTION_VIEW + BROWSABLE + ISSUES_URL |
| 16 | Payment apps are never drawn over; the sensitive set outranks even a lock | app/ | The suppression set outranks a lock | quoted |
| 16 | USE_EXACT_ALARM | app/ | USE_EXACT_ALARM | uses-permission |
| 16 | SCHEDULE_EXACT_ALARM capped at maxSdkVersion 32 | app/ | android:maxSdkVersion="32" | 32 |
| 16 | Not requested: READ_PHONE_STATE, QUERY_ALL_PACKAGES, SYSTEM_ALERT_WINDOW, INTERNET, POST_NOTIFICATIONS, HIGH_SAMPLING_RATE_SENSORS | README.md:226 | Not requested: | quoted |
| 16 | accessibilityEventTypes: scrolls and window changes | app/ | typeViewScrolled | scrolls, window state, windows changed |
| 16 | isAccessibilityTool false | app/ | android:isAccessibilityTool="false" | false |
| 16 | notificationTimeout 0, so scroll bursts are not coalesced | app/ | android:notificationTimeout="0" | 0 |
| 16 | notificationTimeout 0, why | app/ | notificationTimeout stays 0 | comment |
| 17 | The source is public under GPL-3.0-or-later | README.md:11 | GPL--3.0--or--later | badge |
| 18 | YouTube is lease-gated only; feed and Shorts send no scroll events | README.md:239 | YouTube is lease-gated only | quoted |
| 18 | Paytm blocks payments while Jitter is enabled; Disable for payments in CFG, Safety | app/ | onboarding_limit_paytm | UI string |
| 18 | It checks for the presence of any accessibility service | README.md:526 | getEnabledAccessibilityServiceList | quoted |
| 18 | after one confirmation | app/ | settings_disable_confirm | "Disable now" |
| 18 | Google Pay and PhonePe work normally | README.md:517 | payments complete normally | table |
| 18 | Play Protect blocks the install outright on some phones | README.md:178 | If Play Protect blocks | quoted |
| 18 | Tracking comes back by itself after three days | app/ | GRACE_DAYS | 3 |
| 18 | Timing was measured on one (phone) | app/ | reference device | quoted |
| § | Claim | Source | Symbol | Value |
|---|---|---|---|---|
| 03 | Ten minutes before stalls begin | app/ | DEFAULT_HORIZON_MS | 25 min |
| 03 | Ten minutes before stalls begin | app/ | ONSET_FRACTION | 0.40 |
| 03 | Demo stall 1200 ms, "roughly sixteen minutes" | app/ | Knot(at(14.0) | 1200 ms / 0.70 at minute 16.32 (verify-curve.py); 1200 was a constant in the previous site's js/site.js |
| 03 | Grey bar, 2px | app/ | TELL_DP | 2f |
| 03 | Grey bar colour | app/ | TELL_COLOR | 0xFF8C8C96 |
| 06 | 25m DEFAULT HORIZON constant; "Default 25-minute horizon" | app/ | DEFAULT_HORIZON_MS | 25 min |
| 06 | Two numbers: time in the app plus time past a lease | app/ | fun effectiveMs | accumulated + penalty |
| 06 | Overdue minutes count twice; ceiling at fifteen real minutes | app/ | fun accruePenalty | +1 ms penalty per overdue in-app ms (comment lines 379-384) |
| 06 | Does not come back down until the cycle ends | app/ | penaltyMs = 0 | reset at rollover |
| 06 | Sixty-minute ceiling: three seconds | app/ | TERMINAL_STALL_TAPERED_MS | 3000 |
| 06 | seven scrolls in ten | app/ | TERMINAL_PROBABILITY_TAPERED | 0.70f |
| 07 | Bit: three times an hour | app/ | MAX_PER_HOUR | 3 |
Where it does not work.
It does not work everywhere.
YouTube is lease-gated only. Its home feed and Shorts send no scroll events to Android, so stalls never start there. The lease still expires on time, even mid-video.
Paytm blocks payments while Jitter is enabled. It checks for the presence of any accessibility service, not for what that service does, so nothing Jitter can do reaches it. In CFG, Safety, Disable for payments turns Jitter off for a payment after one confirmation; you re-enable it in Android Settings afterwards. Google Pay and PhonePe work normally.
app/
Play Protect blocked the install outright on the phone the screenshots come from. The install steps say exactly what you will see, and how to turn it back on afterwards.
Untracking a social app is temporary. Tracking comes back by itself after three days.
app/
Tested on a small number of devices. Timing was measured on one.
app/