New derpfest build https://drive.google.com/file/d/1OUMd0ZW9-yXc_iv-Mxc985KXKJJnGhq3/view?usp=drivesdk Changelog: - Synced sources - Tried to fix high battery drain reported by someone, need reports in that regard After someone will check about battery drain I will publish on derpfest updates

Channel
Adi's builds
@adi200x1
On this record: Topic · Growth · Engagement · Posts · Handles named that no longer answer · Cite this entry
99subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001351124128 |
|---|---|
| Type | Channel |
| Username | @adi200x1 |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 2 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 2 October 2026 |
| On Telegram | t.me/adi200x1 |
Topic
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 27 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 16:00 | 99 | +5 |
| 9 Sept 2026, 14:17 | 94 | -4 |
| 9 Aug 2026, 11:32 | 98 | no change |
| 7 Aug 2026, 17:34 | 98 | first reading |
Engagement
20 posts held, back to 4 May 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 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
New DerpFest build https://drive.google.com/file/d/1RA55AL0OvVYcMK7aDqWsBf6BsJffiwMg/view?usp=sharing Changelog: - Synced derpfest sources
New DerpFest build https://drive.google.com/file/d/1nNSz5-VVRE6DhT937CPaVJJyLB_qmAyC/view?usp=sharing - Merged febuary security patch - Synced derp sources screen off fod is broken idk why, i will try debug it out before i will release on derpfest updates
New DerpFest build https://drive.google.com/file/d/1Erh5uJDnstniV-ktyejpASn3gJU3A9Io/view?usp=sharing Changelog: - Update kernel bpf backport into 5.10 - Update from 1.0.33 sweet_k6a release - Update dolby blobs - Sync sources
https://drive.google.com/file/d/19Di5DNYbVdVnuEMTFBmnk84Awfoa7uoQ/view?usp=sharing New DerpFest build - Updated dolby atmos implemention - Synced derp sources (fixed hotspot settings page, App volume, lmofreeform added and more)
https://drive.google.com/file/d/1BHVZMUw0ckM4_vWng43laHXjFSNO1gM4/view?usp=sharing New DerpFest build - Synced sources - Fixed some crashes in systemUI and in launcher
DerpFest new build https://drive.google.com/file/d/1UsXfEBpnrCzI26J-rz6CHt7FEvCDp4a2/view?usp=sharing - Fixed QCOM Wireless Display - Synced sources
https://drive.google.com/file/d/1iFmvIm6LSc0_pfjowO4r4UF1yhPffFri/view?usp=sharing new build - Include missing postprocesing blobs - Adapt motor camera menu into expressive design - Update some props - Sync sources
DerpFest QPR2 for davinci https://drive.google.com/drive/folders/1JclkNRsqeJ-GZW3WcGkvxphNsbqsmJ6z?usp=sharing Changelog: * Remove useless BPF patches which i picked on previous build * Improvments for launcher * Switched for now into AOSP WFD for fix Miracast * Disable blurs since it was lagging with them
DerpFest QPR2 for davinci https://drive.google.com/drive/folders/1JclkNRsqeJ-GZW3WcGkvxphNsbqsmJ6z?usp=sharing Bugs: - Wireless Display (will workaround in next build with switching into AOSP until there is any shim found to QCOM one) - Minor bugs in source like launcher stuck sometime(not often and not always happens)
Derp QPR1 build https://drive.google.com/drive/folders/195DrcOnditey0AuZW0VeJrTqMMxTQrmN?usp=sharing Not all customizations are added back yet, ksu next 1.1.1 included with susfs 1.5.9, passes integrity by default
DerpFest 16 test build rom: https://drive.google.com/file/d/1EyUsG_aTSiUJrIUmc9OxJVZ9SwbZ6lx5/view?usp=sharing recovery: https://drive.google.com/file/d/1jH7Xoku2k8hfmyieObN6Mq3GyCe6K5SY/view?usp=sharing Synced derpfest source and includes changes only for maintainers Rebased device and kernel trees over lineage official but with many changes(dolby included, updated blobs, anti_flicker enabled, device as webcam is …
Showing the 12 most recent of 20 posts we hold for @adi200x1. 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@adi200x1 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 10 August 2026 – 10 August 2026
Cite this entry
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“Adi's builds” (@adi200x1), 99 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/adi200x1.
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.