Channel
@mochi_vayu
On this record: Growth · Engagement · Posts · Cite this entry
603subscribers
-5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001533703974 |
|---|---|
| Type | Channel |
| Username | @mochi_vayu |
| Created | Between 1 August 2021 and 22 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/mochi_vayu |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 09:52 | 603 | -3 |
| 23 Aug 2026, 01:05 | 606 | -1 |
| 15 Aug 2026, 18:15 | 607 | -1 |
| 7 Aug 2026, 06:32 | 608 | no change |
| 7 Aug 2026, 06:22 | 608 | first reading |
20 posts held, back to 22 August 2021 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 28 July 2022. An engagement rate over an empty window would be a number about nothing.
https://t.me/mochivayu/131728 CL: Switched back to default defconfig for qcacld Recommended to flash to this one if older one was flashed and you had wifi issues GCC 9.3 Build, LA.UM.9.1.r1-12100-SMxxx0.QSSI12.0 branch Reply in group if you face any issues with it, thanks
https://t.me/mochivayu/131448 CL: Rebased to CLO base Minor charging fixes GCC 9.3 Build, LA.UM.9.1.r1-12100-SMxxx0.QSSI12.0 branch Reply in group if you face any issues with it, thanks
locking, futex, and mutex changes ln8000 charger support branch: r2, gcc12 lto build
* Fix boot time regression on clean flash of ROM * Merge latest ACK & CAF tags * GCC 9.3 Build, r2-tmp branch
not much changed, rebase over latest caf and aosp branches (my phone still dead)
New kernel upda- oh wait. nevermind. It's finally December and what better way to start the month off than having bricked phone :D This is now officially the second brick on oss. Had left it unattended to charge for about 20 minutes in the morning while away having breakfast only to return to a dead phone. I can no longer recommend this device and as such, retract all my previous recommendations. Get a better dev…
mainline binder cgroup, procfs changes genshin switch added back misc. changes for general improvements clang LTO build
cl: upstream, minor logspam removal, suspend fixes, lots of touch changes, full cl will be published later
CL same as prev. build with one more commit
CL Same as previous build with ghost touch fixes
tracing bonked fp irq cleanup charging optimizations wireguard, drivedroid minor sched changes
Channel photo updated
Showing the 12 most recent of 20 posts we hold for @mochi_vayu. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 29 August 2026 — this entry's latest reading, not the date you are reading this.
“mochi-vayu-releases” (@mochi_vayu), 603 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/mochi_vayu.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.