Channel
@PixelLineage
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
541subscribers
+26 since we began measuring on 22 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002203488898 |
|---|---|
| Type | Channel |
| Username | @PixelLineage |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 22 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/PixelLineage |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 21 September 2026 and assigned it the closest of 31 fixed categories, at 93% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Oct 2026, 08:20 | 541 | -1 |
| 1 Oct 2026, 06:16 | 542 | +4 |
| 17 Sept 2026, 13:01 | 538 | +7 |
| 9 Sept 2026, 05:21 | 531 | +7 |
| 31 Aug 2026, 00:42 | 524 | +5 |
| 23 Aug 2026, 21:34 | 519 | +4 |
| 22 Aug 2026, 11:00 | 515 | first reading |
20 posts held, back to 1 November 2025 — 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 22 August 2026. An engagement rate over an empty window would be a number about nothing.
lineage-23.2-20260822-quick-alioth OneDrive | SourceForge lineage-23.2-20260822-quick-munch OneDrive | SourceForge Changelog: * august security patch * new los updater * keep updater checks daily for integrity * internal bluetooth permission fixes * updated revanced prebuilts * source upstream and minor patches Check pinned message 📌 Smoking and Drinking is injurious to health.
If you enjoy this project and want to support its development, consider sponsoring it! Your contributions help keep the updates coming. Every bit counts—thank you!
lineage-23.2-20260607-quick-alioth OneDrive | SourceForge lineage-23.2-20260607-quick-munch OneDrive | SourceForge Changelog: * june security patch * added auto-updater for integrity * source upstream Check pinned message 📌 Smoking and Drinking is injurious to health.
lineage-23.2-20260525-quick-alioth OneDrive | SourceForge lineage-23.2-20260525-quick-munch OneDrive | SourceForge Changelog: * update keybox * buttons settings crash fix * fixed bugs with revanced implementation Check pinned message 📌 Smoking and Drinking is injurious to health.
lineage-23.2-20260515-quick-alioth OneDrive | SourceForge lineage-23.2-20260515-quick-munch OneDrive | SourceForge Changelog: * may security patch * update keybox and fp * update ksu legacy * upstream lineage sources * drop irrelevant thermal configs * added back pixel bootanimation * bring back old calibration for auto brightness on munch * make home search use google search page (same behaviour as pixel phone) * …
lineage-23.2-20260501-quick-alioth OneDrive | SourceForge lineage-23.2-20260430-quick-munch OneDrive | SourceForge Changelog: * update keybox and fp * improved audio latency on bluetooth devices * use high perf task profiles for UI rendering * fixed usb tethering on windows * misc. optimizations & upstream Notes: * Android 16 has blur enabled by default. If you want to save battery and have a smoother UI, disable …
If you enjoy this project and want to support its development, consider sponsoring it! Your contributions help keep the updates coming. Every bit counts—thank you!
lineage-23.2-20260417-quick-alioth OneDrive | SourceForge lineage-23.2-20260417-quick-munch OneDrive | SourceForge Changelog: * match signal bars as aosp/pixel * improve UI and blur rendering * update ksu 0.9.5 to ksu legacy 3.2.2 (get apk from notes) * directly open inner page on battery app info settings (took from GrapheneOS) * fixed ignore window secure flags * fixed nfc on munch * misc. fixes and improvements …
HOTFIX PUSHED - April 11 Switched from Cortex A76 to A55, enhancing overall efficiency and ensuring smoother, faster performance. Thanks @peternoz for recommendation! Please head to Settings -> System -> System updates links updated on previous post.
lineage-23.2-20260411-quick-alioth OneDrive | SourceForge lineage-23.2-20260411-quick-munch OneDrive | SourceForge Changelog: * Android 16 QPR2 April security patch. * 32-bit apps will no longer work. If you have any, delete them before updating. * KernelSU-Next removed due to regressions. Revert to KernelSU 0.9.5 (get APK from notes). * Dropped Leica Micam. * Updated Revanced prebuilts. * Updated Twemoji prebuilt …
lineage-22.2-20260224-quick-alioth OneDrive | SourceForge lineage-22.2-20260224-quick-munch OneDrive | SourceForge Changelog: - Update keybox for integrity - 95 audio bugs fixed - Minor RAM management fixes Known Bugs: 1] "ok google" voice trigger doesn't work. Play Integrity Note: This ROM currently uses a prebuilt keybox to pass integrity checks. It works for many apps, but some banking apps may not function pr…
lineage-22.2-20260129-quick-alioth OneDrive | SourceForge lineage-22.2-20260129-quick-munch OneDrive | SourceForge Changelog: - Update keybox for integrity - Update kernel Known Bugs: 1] "ok google" voice trigger doesn't work. Play Integrity Note: This ROM currently uses a prebuilt keybox to pass integrity checks. It works for many apps, but some banking apps may not function properly. A fix is not guaranteed, bu…
Showing the 12 most recent of 20 posts we hold for @PixelLineage. 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.
Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“PixelLineage by Quick” (@PixelLineage), 541 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/PixelLineage.
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.