Jitter

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.

Jitter's gate the first time Instagram is opened in a cycle: a small face, today 0 minutes, this cycle 0 minutes, opens today 1, the line next scroll, no stall yet, a countdown at 8, and a single leave button labelled Architect's Space.
01 · The gate, first open · 8 seconds

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.

Jitter's lease-expired gate for Instagram after its countdown: today 39 minutes, this cycle 19 minutes, opens today 18, next scroll a 91 percent chance of a 2901 millisecond stall, and three lease buttons for 5, 10 and 15 minutes above Block this app and Architect's Space.
02 · Lease expired, at zero · 5, 10 or 15 minutes

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.

Jitter's console home screen: a battery bar at 67 percent, the time and date, Bit's face, five favourite apps as bracketed text rows, and a prompt reading type question mark for commands.
The console · your apps, as text

Friction, in sequence.

  1. You scroll, and the app scrolls. The feed moves as it always does.
  2. Android then reports the scroll to Jitter’s accessibility service.
  3. Jitter rolls once against the friction curve for that app at that minute: a chance, not a schedule.
  4. On a hit, it arms a full-screen overlay for the length of the stall.
  5. While the overlay is armed it swallows every touch, taps included. Nothing is queued or replayed: a swipe made during a stall is gone.
  6. 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.

On the default 25-minute horizon
Time in the appStallChance a scroll stallsIn other words
10 min450 ms10%one scroll in ten stalls, for under half a second
20 min2950 ms91.3%about nine scrolls in ten stall, for about three seconds
25 min5000 ms100%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.

Three horizons.
HorizonFriction startsCeiling stallCeiling chance
10 min, the shortest4 min5000 ms100%
25 min, the default10 min5000 ms100%
60 min, the longest24 min3000 ms70%

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/src/main/res/xml/accessibility_service_config.xml

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/src/main/res/xml/accessibility_service_config.xml

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/src/main/java/dev/molasses/monitor/MolassesAccessibilityService.kt

There is no network. No INTERNET permission in the manifest.

app/src/main/AndroidManifest.xml

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/src/main/AndroidManifest.xml

A stall also lets go when the screen turns off, when you leave the app, and when a call arrives.

app/src/main/java/dev/molasses/overlay/ShutterOverlayManager.kt

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/src/main/java/dev/molasses/core/safety/PauseWindow.kt

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/src/main/java/dev/molasses/core/support/ReportProblem.kt

Every permission and service flag, and what each is for
PACKAGE_USAGE_STATS
Usage access. Replays ACTIVITY_RESUMED and ACTIVITY_PAUSED after 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 $ rem alarms after a reboot.
VIBRATE
$ rem vibrates once when the ringer is on vibrate.
USE_EXACT_ALARM
Lets $ rem use 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.

accessibilityEventTypes
typeViewScrolled|typeWindowStateChanged|typeWindowsChanged: that a scroll happened and which window is in front. Nothing else.
canRetrieveWindowContent
false. Android’s documentation says a service must declare this capability to retrieve a window’s content.
canPerformGestures
false. Android’s documentation says a service must declare this capability to dispatch gestures, such as a tap or a swipe.
isAccessibilityTool
false. It does not declare itself an accessibility tool.
notificationTimeout
0, 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.

app/src/main/res/xml/accessibility_service_config.xml

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.

LICENSE

249 rows, each held to its line at f9b5b9f by tools/check-trace.sh before every deploy.

Three of them, as they appear in the full table.
§ClaimSourceSymbolValue
14... 91.3% of scrolls stall, for 2950 ms: between the knot at(18.0)app/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:295Knot(at(18.0), 2700, 0.90f)f = (20 - 10) / 15 = 2/3, past 12/19
135: while armed it swallows every touchapp/src/main/java/dev/molasses/overlay/ShutterOverlayManager.kt:562Swallows every touch.FLAG_NOT_TOUCHABLE removed while armed
16No INTERNET permission in the manifestapp/src/main/AndroidManifest.xml:138INTERNET stays outabsent
All 249 rows, by section
The main page, by block: 1 the hero, 2 how it works, 3 install, 4 the closing line and the footer. 89 rows.
§ClaimSourceSymbolValue
1"Jitter never blocks anything you didn't ask it to." Tracked apps are never blocked by the frictionREADME.md:6are never"are never / blocked", lines 6-7 (reflowed upstream)
1... "never blocked", the second line of the sentenceREADME.md:7blocked: the longer you stay"blocked:"
1... you didn't ask it to: a lock is set by the user, from an hour to thirty daysapp/src/main/java/dev/molasses/core/lock/LockLadder.kt:30val STEPS_MS1h, 4h, 12h, 1d, 3d, 7d, 14d, 30d
1... you didn't ask it to: [ BLOCK THIS APP ] on the lease-expired gateapp/src/main/java/dev/molasses/core/lock/GateBlock.kt:6[ BLOCK THIS APP ]user-chosen block
1An Android launcherREADME.md:5home screen"a home screen and a set of speed bumps for Android"
1Hero panel: a stall follows a scroll that has already happened. Android reports the scroll to the service after the app performed itapp/src/main/java/dev/molasses/monitor/MolassesAccessibilityService.kt:708AccessibilityEvent.TYPE_VIEW_SCROLLED -> WindowEvent.Kind.VIEW_SCROLLEDthe scroll event, not the gesture
1... the service asks the friction engine on that scrollapp/src/main/java/dev/molasses/monitor/MolassesAccessibilityService.kt:766engine.onScroll(pkg, now())per scroll event
1... which rolls once against the curve (a Bernoulli trial)app/src/main/java/dev/molasses/engine/FrictionEngine.kt:307FrictionCurve.shouldStall(friction, roll())roll = Random.nextFloat()
1... a hit when the roll is under the curve's probabilityapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:375roll < point.probabilitystall only if stallMs > 0 and roll < p
1... and on a hit the full-screen overlay is armed for the stallapp/src/main/java/dev/molasses/monitor/MolassesAccessibilityService.kt:798val armed = shutter.arm(arm(ms = decision.stallMs)
1Hero panel: while armed the overlay swallows every touchapp/src/main/java/dev/molasses/overlay/ShutterOverlayManager.kt:562Swallows every touch.FLAG_NOT_TOUCHABLE removed while armed
1... taps included: every touch event is consumed, none is passed on or queuedapp/src/main/java/dev/molasses/overlay/ShutterOverlayManager.kt:482override fun onTouchEvent(event: MotionEvent): Booleanreturns true for every action while armed (line 507)
1... (the consuming return)app/src/main/java/dev/molasses/overlay/ShutterOverlayManager.kt:507return trueconsumed
1Hero panel: never armed for more than eight seconds in a rowapp/src/main/java/dev/molasses/overlay/ShutterOverlayManager.kt:570MAX_CONTINUOUS_ARMED_MS = 8_000L8 s
1... the ceiling holds whatever the tier or the scroll rateapp/src/main/java/dev/molasses/overlay/ShutterOverlayManager.kt:266never armed for more than 8 s continuouslyquoted
1Hero panel: the tell is greyapp/src/main/java/dev/molasses/overlay/ShutterOverlayManager.kt:582TELL_COLOR = 0xFF8C8C960xFF8C8C96; red is the terminal tier only (line 437), which the panel never reaches
1Small print: default settings: the default horizonapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:143DEFAULT_HORIZON_MS25 min
1... friction starts at 40% of it: ten minutesapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:156ONSET_FRACTION0.40 x 25 = 10 min
1... the horizon is per app, from ten minutesapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:150MIN_HORIZON_MS10 min
1... to sixtyapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:153MAX_HORIZON_MS60 min
1At ten minutes, one scroll in ten stallsapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:285Knot(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 floorapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:362private fun clampFloor(max(150, 450) = 450 ms
1... the floor: no non-zero stall below 450 msapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:119DEFAULT_FLOOR_MS450
1At twenty: the knots sit on the source table's own 6-to-25 scale, not on real minutesapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:270private 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/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:295Knot(at(18.0), 2700, 0.90f)f = (20 - 10) / 15 = 2/3, past 12/19
1... and the knot at(22.0)app/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:297Knot(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%)
1At twenty-five (the horizon, not stated in the panel): five secondsapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:228TERMINAL_STALL_MS5000
1... on every scrollapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:230TERMINAL_PROBABILITY =1.00f
1Closing: "Jitter doesn't block you."README.md:6are neverthe claim above it, restated
1Closing: "It makes staying harder."README.md:105only ever"Within a cycle the friction only ever increases"
2By default, your first ten minutes in an app cost nothingapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:143DEFAULT_HORIZON_MS25 min
2By default, your first ten minutes in an app cost nothingapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:156ONSET_FRACTION0.40 x 25 = 10 min
2The app ignores your fingerREADME.md:55touches in that app do nothingblackout
2450 millisecondsapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:119DEFAULT_FLOOR_MS450
2At first, about one scroll in tenapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:285Knot(at(6.0)p 0.10 at onset (its 150 ms is clamped to the 450 floor)
2At twenty-five minutes, five secondsapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:228TERMINAL_STALL_MS5000
2on every scrollapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:230TERMINAL_PROBABILITY =1.00f
2Across a six-hour cycleapp/src/main/java/dev/molasses/core/model/CycleResetPolicy.kt:33WINDOW_MS6 h
2Counted for each app; leaving and coming back does not reset themapp/src/main/java/dev/molasses/core/friction/CycleRollover.kt:28accumulatedMs = 0per-app snapshot, zeroed only here, at rollover (the only assignment in app/src/main)
2Inside that cycle they only go upREADME.md:105only ever"Within a cycle the friction only ever increases"
2A scroll goes through, then stalls: Android reports the scroll after the app performed itapp/src/main/java/dev/molasses/monitor/MolassesAccessibilityService.kt:708AccessibilityEvent.TYPE_VIEW_SCROLLED -> WindowEvent.Kind.VIEW_SCROLLEDthe scroll event, not the gesture
2... and on a hit the overlay is armedapp/src/main/java/dev/molasses/monitor/MolassesAccessibilityService.kt:798val armed = shutter.arm(arm(ms = decision.stallMs)
2The app ignores your finger, taps includedapp/src/main/java/dev/molasses/overlay/ShutterOverlayManager.kt:482override fun onTouchEvent(event: MotionEvent): Booleanreturns true for every action while armed
2... (the consuming return)app/src/main/java/dev/molasses/overlay/ShutterOverlayManager.kt:507return trueconsumed
2At the default settings: 20 minutes, nine in ten, for nearly three seconds: the knots on the source table's 6-to-25 scaleapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:270private 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/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:295Knot(at(18.0), 2700, 0.90f)f = (20 - 10) / 15 = 2/3
2... and at(22.0)app/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:297Knot(at(22.0), 4200, 0.98f)t = 1/6: 2950 ms (nearly three seconds), 0.913 (nine in ten)
3Android 11 and laterapp/build.gradle.kts:61minSdk30
3Plain step: download the APKREADME.md:165Download the APKquoted
3Plain step: Android asks you to let your browser install appsREADME.md:175install unknown appsquoted
3Plain step: Play Protect may warn you or block the installREADME.md:178If Play Protect blocksquoted
3Plain step: Android may block the accessibility switch until you allow restricted settings (it did on Android 16)README.md:183Restricted settings (Android 13 and later)quoted
3Plain step: then accessibility and usage accessREADME.md:190accessibility, usage accessquoted
3Plain step: your old launcher stays installed; switch back any timeREADME.md:262Default apps, Home appquoted
3Flow 1, check: its SHA-256 matches the one on the release pageREADME.md:168SHA-256, and yours should match exactlyquoted
3Flow 2, check: opening Jitter shows its SETUP screen (shown until setup is complete)app/src/main/java/dev/molasses/core/setup/Onboarding.kt:8shown until setup is completethe first-run flow
3... its SETUP screenapp/src/main/res/values/strings.xml:692name="onboarding_title">SETUPSETUP
3Flow 3, check: a satisfied step shows [✓]app/src/main/res/values/strings.xml:701name="setup_mark_done"[✓]
3... ACCESSIBILITY, satisfied only when the service is workingapp/src/main/java/dev/molasses/core/setup/Onboarding.kt:53Step.ACCESSIBILITY -> facts.serviceWorkingdetected
3... USAGE ACCESSapp/src/main/java/dev/molasses/core/setup/Onboarding.kt:54Step.USAGE_ACCESS -> facts.usageAccessdetected
3Flow 4, check: HOME APP shows [✓] when Jitter is the default home appapp/src/main/java/dev/molasses/core/setup/Onboarding.kt:55Step.HOME -> facts.defaultHomedetected
3... HOME APPapp/src/main/res/values/strings.xml:706name="onboarding_home_name">HOME APPHOME APP
3Jitter is sideloaded: the download is the APK attached to a GitHub releaseworker/index.js:13const PINNED_APKthe jitter-v1.0.3.apk release asset
3Each release page lists the file's SHA-256README.md:168SHA-256quoted
3certutil -hashfile jitter-v1.0.3.apk SHA256README.md:170certutil -hashfile jitter-v1.0.3.apk SHA256verbatim
3shasum -a 256 jitter-v1.0.3.apkREADME.md:171shasum -a 256 jitter-v1.0.3.apkverbatim
3sha256sum jitter-v1.0.3.apkREADME.md:172sha256sum jitter-v1.0.3.apkverbatim
3More details / Install anywayREADME.md:178Install anywayquoted
3There is no way around a block from inside JitterREADME.md:179no in-app way aroundquoted
3App info, three-dot menu; on other phones the menu item may read Allow restricted settingsREADME.md:185three-dot menuquoted
3Jitter's setup guide walks through this tooREADME.md:186setup guide walksquoted
3Two of the things it warns about are switched off (retrieve window content)app/src/main/res/xml/accessibility_service_config.xml:25canRetrieveWindowContent="false"false
3... (tap or swipe for you)app/src/main/res/xml/accessibility_service_config.xml:26canPerformGestures="false"false
3What it does use the permission for is knowing which app is in frontREADME.md:205It sees which app is in frontquoted
3Instagram, X, YouTube and Snapchat by defaultapp/src/main/java/dev/molasses/data/datastore/CycleStateSerializer.kt:42val DEFAULT_TARGETS: List<String> = DefaultTargets.CURRENTthe defaults are DefaultTargets.CURRENT
3... Instagram, X and YouTubeapp/src/main/java/dev/molasses/core/session/DefaultTargets.kt:22val BEFORE_SNAPCHATcom.instagram.android, com.twitter.android, com.google.android.youtube (lines 23-25)
3... and Snapchatapp/src/main/java/dev/molasses/core/session/DefaultTargets.kt:28val CURRENT: List<String> = BEFORE_SNAPCHAT + "com.snapchat.android"4 packages
3You can switch back any time in Android's settingsREADME.md:262Default apps, Home appquoted
3Untracking waits two and a half minutesapp/src/main/java/dev/molasses/core/settings/UntrackCoolingOff.kt:33DURATION_MS150_000
3Instagram, Facebook, X, TikTok, Snapchat (named)README.md:125TikTok, Snapchatquoted
3and any app that declares itself a social appapp/src/main/java/dev/molasses/core/settings/UntrackSunset.kt:76CATEGORY_SOCIALthe app's own declared category, read by Jitter
3after three days, or at the next restart if that is soonerREADME.md:126at the next restartquoted
3after three daysapp/src/main/java/dev/molasses/core/settings/UntrackSunset.kt:57GRACE_DAYS3
3Old tester build (dev.molasses): uninstall it firstREADME.md:196Moving from the old tester buildquoted
3Jitter is not on Google Play; you install the APK yourselfREADME.md:162It is not on the Play Storequoted
4Footer: Jitter 1.0.3gradle/libs.versions.toml:13appVersion = "1.0.3"1.0.3
4Footer: Android 11 and laterapp/build.gradle.kts:61minSdk30 = Android 11
4Footer: open source under GPL-3.0-or-laterREADME.md:11GPL--3.0--or--laterthe licence badge
4The app's issue tracker, the address its report-a-problem row opensapp/src/main/java/dev/molasses/core/support/ReportProblem.kt:26ISSUES_URLhttps://github.com/keerthanpragnay1728-prog/jitter/issues
This page, by block: 11 the two systems, 12 the gate, 13 friction in sequence, 14 what friction costs, 15 the horizon and the cycle, 16 what Jitter does not do, 17 evidence, 18 limitations. 148 rows.
§ClaimSourceSymbolValue
11Plain layer: an app you have chosen to trackapp/src/main/java/dev/molasses/data/datastore/CycleStateSerializer.kt:42val DEFAULT_TARGETSdefaults; you pick
11Plain layer: a few minutes in it, and you choose how manyapp/src/main/java/dev/molasses/core/lease/GatePolicy.kt:82OFFERED_MS5, 10, 15 min
11Plain layer: coming back does not start you over; the minutes add upapp/src/main/java/dev/molasses/core/friction/CycleRollover.kt:28accumulatedMs = 0zeroed only at rollover
11Plain layer: scrolling gets less reliable as they doREADME.md:105only ever"Within a cycle the friction only ever increases"
11Plain layer: it keeps building for hours, then the count goes back to zeroapp/src/main/java/dev/molasses/core/model/CycleResetPolicy.kt:33WINDOW_MS6 h
11Plain layer: eventually every scroll stallsapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:230TERMINAL_PROBABILITY =1.00f
11Plain layer: nothing is blocked unless you askREADME.md:6are never"are never / blocked", lines 6-7 (reflowed upstream)
11... the second line of the sentenceREADME.md:7blocked: the longer you stay"blocked:"
11The lease and friction share no state; neither reads the otherREADME.md:1151share no statequoted
11The lease runs on real elapsed time, checked at its deadlineREADME.md:344A lease runs on real elapsed timequoted
11Changing the system clock does not move itREADME.md:347system clock does not move itquoted
11A reboot ends every leaseREADME.md:347a reboot ends every leasequoted
11One number crosses, in one direction: the accumulated total at the grantREADME.md:1154One number crossesquoted
11A lease never resets accumulated time, never lowers a stall; a toll, not a refundREADME.md:353Gates are a tollquoted
11Block 1, the contrast: the gate decides whether you may be in an app at allREADME.md:1149System A is the lease"permission to be in an app"
11... it stands at the door, and lets you in on a leaseREADME.md:155What stands in front of a tracked appthe lease gate
11Friction decides what a scroll costs while you are insideREADME.md:1150System B is friction"accumulated foreground time, which decides what a scroll costs"
12Jitter replaces your home screenREADME.md:5home screena home screen
12A black page in front of it: time today, times opened, a countdownREADME.md:72full-screen black pagethe gate
12Eight seconds the first timeapp/src/main/java/dev/molasses/core/lease/GatePolicy.kt:122FIRST_MS8_000
125, 10 or 15 minutes (text and plate 02 caption)app/src/main/java/dev/molasses/core/lease/GatePolicy.kt:82OFFERED_MS5, 10, 15 min
12There is no unlimited optionREADME.md:82There is no unlimited optionquoted
12Twelve seconds, then sixteen, then twentyapp/src/main/java/dev/molasses/core/lease/GatePolicy.kt:125STEP_MS4_000
12up to thirtyapp/src/main/java/dev/molasses/core/lease/GatePolicy.kt:132CAP_MS30_000
12for as long as the cycle lasts; leaving costs nothingREADME.md:99Backing out costs nothingonly leases taken lengthen it
12When the time runs out, the app goes to the background and the gate comes backREADME.md:86goes home under the gatelease expiry
12Lock an app, or every app you trackREADME.md:35Locks you cannot undo"Lock an app, or every tracked app"
12From the gate, when a lease runs out, up to a dayapp/src/main/java/dev/molasses/core/lock/GateBlock.kt:29const val CAP_MS24 h, offered on the lease-expired gate only
12From settings, for up to thirty daysapp/src/main/java/dev/molasses/core/lock/LockLadder.kt:3830 * DAYMAX_MS
12Nobody can lift it before it expires; no control for it anywhere in the appapp/src/main/java/dev/molasses/ui/settings/SettingsScreen.kt:1793There is no unlock control"at any depth"
12Nobody can lift it before it expiresapp/src/main/java/dev/molasses/data/datastore/CycleStateStore.kt:455There is deliberately no unlockno unlock in the store
12Nothing can reach it from outside: Jitter has no internet permissionapp/src/main/AndroidManifest.xml:138INTERNET stays outno INTERNET uses-permission
12The only way out is to turn Jitter off or uninstall itREADME.md:44uninstall"You can always turn off its accessibility service or uninstall it"
12and nothing in it tries to stop youREADME.md:45nothing in it tries to stop youquoted
12for as long as the cycle lasts: the count resets with the cycleREADME.md:100The count resets when thequoted
12Block from the gate for one, four or twelve hours, or a dayapp/src/main/java/dev/molasses/core/lock/GateBlock.kt:32val RUNGS_MS1h, 4h, 12h, 1d
12Longer locks are set in settings, where a confirmation appliesapp/src/main/java/dev/molasses/core/lock/GateBlock.kt:22confirmation step appliesquoted
12A plain text home screen: your apps as words, and a command lineREADME.md:38A console launcherconsole
13So you always know it is JitterREADME.md:60thin grey"So you can always tell it is us"
13At the ceiling it turns red: the terminal tier, effective time at or past the horizonapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:192fun isTerminaleffective time >= horizon
13Four tapsapp/src/main/java/dev/molasses/overlay/ShutterOverlayManager.kt:578PANIC_TAPS4
13within a second and a halfapp/src/main/java/dev/molasses/overlay/ShutterOverlayManager.kt:579PANIC_WINDOW_MS1_500
13in the top-left cornerREADME.md:65top-left cornerquoted
13A 2dp line along the top edgeapp/src/main/java/dev/molasses/overlay/ShutterOverlayManager.kt:581TELL_DP2f
13grey, 0xFF8C8C96app/src/main/java/dev/molasses/overlay/ShutterOverlayManager.kt:582TELL_COLOR0xFF8C8C96
13at alpha 89 of 255app/src/main/java/dev/molasses/overlay/ShutterOverlayManager.kt:583TELL_ALPHA89
13At the ceiling it turns red, 0xFFFF5555app/src/main/java/dev/molasses/overlay/ShutterOverlayManager.kt:591TELL_COLOR_TERMINAL0xFFFF5555
13the one hue break in the appapp/src/main/java/dev/molasses/overlay/ShutterOverlayManager.kt:437The one hue breakquoted
13Four taps inside the top-left 64dpapp/src/main/java/dev/molasses/overlay/ShutterOverlayManager.kt:580PANIC_REGION_DP64f
131-2: you scroll and the app scrolls; Android then reports the scroll to the serviceapp/src/main/java/dev/molasses/monitor/MolassesAccessibilityService.kt:708AccessibilityEvent.TYPE_VIEW_SCROLLED -> WindowEvent.Kind.VIEW_SCROLLEDthe scroll event, after the app performed it
133: Jitter asks the friction engine on that scrollapp/src/main/java/dev/molasses/monitor/MolassesAccessibilityService.kt:766engine.onScroll(pkg, now())per scroll event
13... and rolls once: a chance, not a scheduleapp/src/main/java/dev/molasses/engine/FrictionEngine.kt:307FrictionCurve.shouldStall(friction, roll())roll = Random.nextFloat()
13... a hit when the roll is under the curve's probabilityapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:375roll < point.probabilitystall only if stallMs > 0 and roll < p
134: on a hit, a full-screen overlay is armed for the length of the stallapp/src/main/java/dev/molasses/monitor/MolassesAccessibilityService.kt:798val armed = shutter.arm(arm(ms = decision.stallMs)
135: while armed it swallows every touchapp/src/main/java/dev/molasses/overlay/ShutterOverlayManager.kt:562Swallows every touch.FLAG_NOT_TOUCHABLE removed while armed
13... taps included; nothing is queued or replayedapp/src/main/java/dev/molasses/overlay/ShutterOverlayManager.kt:482override fun onTouchEvent(event: MotionEvent): Booleanevery action consumed while armed
13... (the consuming return)app/src/main/java/dev/molasses/overlay/ShutterOverlayManager.kt:507return trueconsumed
136: then it disarms, at the end of the stallapp/src/main/java/dev/molasses/overlay/ShutterOverlayManager.kt:271val target = minOf(now + ms, ceiling)armed until now + stall, capped at the 8 s ceiling
14Around sixteen minutes, more than a second, on seven scrolls in tenapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:293Knot(at(14.0)1202 ms / 0.70 at minute 16.32; 1120 ms / 0.68 at 16.0 (verify-curve.py)
14450ms, the shortest stallapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:119DEFAULT_FLOOR_MS450
14Just above a delay measured on one phone, 406 millisecondsapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:116MEASURED_SEGMENT_D_P50_MS406
14measured on one phoneapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:113reference device"on the reference device"
14below which a stall arrives after the scroll it was meant for and is never feltapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:114never feltquoted
145s; at the default horizonapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:228TERMINAL_STALL_MS5000
14every scroll stallsapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:230TERMINAL_PROBABILITY =1.00f
14Never armed for more than eight seconds in a rowapp/src/main/java/dev/molasses/overlay/ShutterOverlayManager.kt:570MAX_CONTINUOUS_ARMED_MS8_000
14Friction reads two numbers: time this cycle plus penaltyapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:183fun effectiveMsaccumulated + penalty
14Below 40% of the horizon it is zeroapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:321if (accumulatedMs < onset)0 ms, 0%
14Past the horizon both stay at the ceilingapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:322if (accumulatedMs >= horizon)ceiling
14No stall shorter than 450 milliseconds is commandedapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:362private fun clampFloor(max(stall, floor)
14At the default 25-minute horizonapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:143DEFAULT_HORIZON_MS25 min
14... friction starts at 40% of it: ten minutesapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:156ONSET_FRACTION0.40 x 25 = 10 min
1410 minutes: one scroll in ten stallsapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:285Knot(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 floorapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:362private fun clampFloor(max(150, 450) = 450 ms
1420 minutes: the knots sit on the source table's own 6-to-25 scale, not on real minutesapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:270private 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/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:295Knot(at(18.0), 2700, 0.90f)f = (20 - 10) / 15 = 2/3, past 12/19
14... and the knot at(22.0)app/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:297Knot(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%)
1425 minutes: every scroll stalls, for 5000 msapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:228TERMINAL_STALL_MS5000
14... every scrollapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:230TERMINAL_PROBABILITY =1.00f
14In between, the longer you stay, the longer a stall lasts and the more often one comesREADME.md:105only ever"Within a cycle the friction only ever increases"
14Qualification: the twenty-minute figures are interpolated, not stated in the sourceapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:311fun frictionAt(interpolates between control points; none at 20 min (they fall at 19.47 and 22.63 min, rows above)
14Qualification: the default horizon is set per appapp/src/main/java/dev/molasses/core/friction/HorizonPolicy.kt:38listOf(10L, 15L, 18L, 20L, 25L, 30L, 40L, 50L, 60L)9 steps
14... from ten minutesapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:150MIN_HORIZON_MS10 min
14... to sixtyapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:153MAX_HORIZON_MS60 min
1525m, the default horizonapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:143DEFAULT_HORIZON_MS25 min
15the length of session an app is forREADME.md:23the length of session it is forquoted
15from ten minutesapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:150MIN_HORIZON_MS10 min
15to sixtyapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:153MAX_HORIZON_MS60 min
15A trip to settings, a confirmation, and a wait for the next cycleapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:141a wait for the next cyclequoted
156h, the cycleapp/src/main/java/dev/molasses/core/model/CycleResetPolicy.kt:33WINDOW_MS6 h
15It starts the first time you open an app you trackREADME.md:119from a clean statecycle anchor
15the minutes ... go back to zeroapp/src/main/java/dev/molasses/core/friction/CycleRollover.kt:28accumulatedMs = 0rollover
15the leases ... go back to zeroapp/src/main/java/dev/molasses/core/friction/CycleRollover.kt:30leasesTaken = 0rollover
15the waits ... go back to zeroREADME.md:100The count resets when thegate length resets with the cycle
15There is no setting for itREADME.md:120There is no settingquoted
15and it never ends a lockapp/src/main/java/dev/molasses/core/lock/LockLadder.kt:18Stored locks are deadlineslocks are deadlines, outside the rollover
15and it never ends a lockapp/src/main/java/dev/molasses/data/datastore/CycleStateStore.kt:453no lock changes stateonly expiry drops a lock
15Offered horizons: 10, 15, 18, 20, 25, 30, 40, 50, 60 minutesapp/src/main/java/dev/molasses/core/friction/HorizonPolicy.kt:38listOf(10L, 15L, 18L, 20L, 25L, 30L, 40L, 50L, 60L)9 steps
15Friction starts at four minutes on the shortestREADME.md:33510 min (minimum)4 min
15... at twenty-four on the longest, three seconds on seven scrolls in tenREADME.md:33760 min (maximum)24 min, 3000 ms, 70%
15The ceiling tapers linearly from 25app/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:223TAPER_FROM_HORIZON_MS = DEFAULT_HORIZON_MS25 min
15... to 60 minutesapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:226TAPER_TO_HORIZON_MS = 60L * 60 * 100060 min
15Three secondsapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:229TERMINAL_STALL_TAPERED_MS3000
15seven scrolls in tenapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:231TERMINAL_PROBABILITY_TAPERED0.70f
15Widening waits for the next cycleapp/src/main/java/dev/molasses/core/friction/HorizonPolicy.kt:11stored as pendingpromoted at rollover
15Narrowing applies at onceapp/src/main/java/dev/molasses/core/friction/HorizonPolicy.kt:14A narrow applies immediatelyquoted
15Setting it back is the only way to cancel a pending widenapp/src/main/java/dev/molasses/core/friction/HorizonPolicy.kt:77A request equal to the current horizon cancelsquoted
15Each app's time is counted while it is in the foregroundREADME.md:318accumulated foreground timequoted
15Usage access replays resumed and paused events after a process deathREADME.md:216Replaysquoted
15At the rollover the minutes go to zeroapp/src/main/java/dev/molasses/core/friction/CycleRollover.kt:28accumulatedMs = 00
15... the leasesapp/src/main/java/dev/molasses/core/friction/CycleRollover.kt:30leasesTaken = 00
15... and the penaltyapp/src/main/java/dev/molasses/core/friction/CycleRollover.kt:32penaltyMs = 00
15A pending wider horizon takes effectapp/src/main/java/dev/molasses/core/friction/CycleRollover.kt:25HorizonPolicy.promotepromote
15Every overdue minute in the app is charged again as penalty; time elsewhere costs nothingapp/src/main/java/dev/molasses/engine/FrictionEngine.kt:381overdue minutes count doublequoted
15With no lease taken, nothing accruesapp/src/main/java/dev/molasses/engine/FrictionEngine.kt:394if (app.leasesTaken > 0)guard
15Ceiling at fifteen real minutes instead of twenty-fiveapp/src/main/java/dev/molasses/engine/FrictionEngine.kt:383fifteen real minutesquoted
15The penalty only ever growsapp/src/main/java/dev/molasses/engine/FrictionEngine.kt:386Monotonic by constructionquoted
16It never reads the screen: canRetrieveWindowContent="false"app/src/main/res/xml/accessibility_service_config.xml:25canRetrieveWindowContent="false"false
16It cannot tap or swipe for you: canPerformGestures="false"app/src/main/res/xml/accessibility_service_config.xml:26canPerformGestures="false"false
16The one action it takes is Home, to send an app back behind the gateapp/src/main/java/dev/molasses/monitor/MolassesAccessibilityService.kt:335performGlobalAction(GLOBAL_ACTION_HOME)the only global action
16The package list is your targets and Jitter itselfapp/src/main/res/xml/accessibility_service_config.xml:28android:packageNames=targets plus org.jitteros.app
16... and re-pushed when you change itapp/src/main/java/dev/molasses/monitor/MolassesAccessibilityService.kt:628re-pushed viasetServiceInfo()
16No INTERNET permission in the manifestapp/src/main/AndroidManifest.xml:138INTERNET stays outabsent
16Every permission, and nothing else (usage, activity recognition, boot, vibrate, exact alarms)app/src/main/AndroidManifest.xml:20PACKAGE_USAGE_STATSfirst uses-permission
16ReadmePermissionsTest fails the build if the list and the manifest differREADME.md:214ReadmePermissionsTestquoted
16A stall lets go when the screen turns off, you leave the app, a call arrivesREADME.md:67releases when the screen turns offquoted
16Pause friction (15m)app/src/main/res/values/strings.xml:197Pause friction (15m)UI string
16for fifteen minutesapp/src/main/java/dev/molasses/core/safety/PauseWindow.kt:45DURATION_MS15 min
16stops stalls, gates and overlaysapp/src/main/java/dev/molasses/core/lock/LockEnforcement.kt:51A pause suspends graduated friction, stallsfriction, stalls, checkpoints
16locks stay lockedapp/src/main/java/dev/molasses/core/lock/LockEnforcement.kt:58paused -> Decision.Enforcelock enforced while paused
16The one link out is a report-a-problem row that hands the issue tracker to your browserapp/src/main/java/dev/molasses/core/support/ReportProblem.kt:51fun spec()ACTION_VIEW + BROWSABLE + ISSUES_URL
16Payment apps are never drawn over; the sensitive set outranks even a lockapp/src/main/java/dev/molasses/core/lock/LockEnforcement.kt:43The suppression set outranks a lockquoted
16USE_EXACT_ALARMapp/src/main/AndroidManifest.xml:33USE_EXACT_ALARMuses-permission
16SCHEDULE_EXACT_ALARM capped at maxSdkVersion 32app/src/main/AndroidManifest.xml:36android:maxSdkVersion="32"32
16Not requested: READ_PHONE_STATE, QUERY_ALL_PACKAGES, SYSTEM_ALERT_WINDOW, INTERNET, POST_NOTIFICATIONS, HIGH_SAMPLING_RATE_SENSORSREADME.md:226Not requested:quoted
16accessibilityEventTypes: scrolls and window changesapp/src/main/res/xml/accessibility_service_config.xml:22typeViewScrolledscrolls, window state, windows changed
16isAccessibilityTool falseapp/src/main/res/xml/accessibility_service_config.xml:29android:isAccessibilityTool="false"false
16notificationTimeout 0, so scroll bursts are not coalescedapp/src/main/res/xml/accessibility_service_config.xml:27android:notificationTimeout="0"0
16notificationTimeout 0, whyapp/src/main/res/xml/accessibility_service_config.xml:6notificationTimeout stays 0comment
17The source is public under GPL-3.0-or-laterREADME.md:11GPL--3.0--or--laterbadge
18YouTube is lease-gated only; feed and Shorts send no scroll eventsREADME.md:239YouTube is lease-gated onlyquoted
18Paytm blocks payments while Jitter is enabled; Disable for payments in CFG, Safetyapp/src/main/res/values/strings.xml:729onboarding_limit_paytmUI string
18It checks for the presence of any accessibility serviceREADME.md:526getEnabledAccessibilityServiceListquoted
18after one confirmationapp/src/main/res/values/strings.xml:195settings_disable_confirm"Disable now"
18Google Pay and PhonePe work normallyREADME.md:517payments complete normallytable
18Play Protect blocks the install outright on some phonesREADME.md:178If Play Protect blocksquoted
18Tracking comes back by itself after three daysapp/src/main/java/dev/molasses/core/settings/UntrackSunset.kt:57GRACE_DAYS3
18Timing was measured on one (phone)app/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:113reference devicequoted
Carried from the previous site, not published now; still checked against the source. 12 rows.
§ClaimSourceSymbolValue
03Ten minutes before stalls beginapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:143DEFAULT_HORIZON_MS25 min
03Ten minutes before stalls beginapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:156ONSET_FRACTION0.40
03Demo stall 1200 ms, "roughly sixteen minutes"app/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:293Knot(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
03Grey bar, 2pxapp/src/main/java/dev/molasses/overlay/ShutterOverlayManager.kt:581TELL_DP2f
03Grey bar colourapp/src/main/java/dev/molasses/overlay/ShutterOverlayManager.kt:582TELL_COLOR0xFF8C8C96
0625m DEFAULT HORIZON constant; "Default 25-minute horizon"app/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:143DEFAULT_HORIZON_MS25 min
06Two numbers: time in the app plus time past a leaseapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:183fun effectiveMsaccumulated + penalty
06Overdue minutes count twice; ceiling at fifteen real minutesapp/src/main/java/dev/molasses/engine/FrictionEngine.kt:389fun accruePenalty+1 ms penalty per overdue in-app ms (comment lines 379-384)
06Does not come back down until the cycle endsapp/src/main/java/dev/molasses/core/friction/CycleRollover.kt:32penaltyMs = 0reset at rollover
06Sixty-minute ceiling: three secondsapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:229TERMINAL_STALL_TAPERED_MS3000
06seven scrolls in tenapp/src/main/java/dev/molasses/core/friction/FrictionCurve.kt:231TERMINAL_PROBABILITY_TAPERED0.70f
07Bit: three times an hourapp/src/main/java/dev/molasses/core/console/ConsoleSpeech.kt:41MAX_PER_HOUR3

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.

README.md

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/src/main/res/values/strings.xml

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/src/main/java/dev/molasses/core/settings/UntrackSunset.kt

Tested on a small number of devices. Timing was measured on one.

app/src/main/java/dev/molasses/core/friction/FrictionCurve.kt