Recovery image from https://t.me/KudProject/908 with logcat included, since apparently some #ido hardware combinations are having a black screen
Signed Albert I (krasCGQ) くらすさん

Channel
@KudProjectCI
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
483subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001494373196 |
|---|---|
| Type | Channel |
| Username | @KudProjectCI |
| Description | Continuous integration builds from @KudProject are posted here. Not all builds are tested; proceed at your own risk! See main channel for project-related links and updates. Device tags (reference only): #X00T #alioth #ginkgo #grus #mido #scale #ulysse |
| Created | Between 1 June 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/KudProjectCI |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Aug 2026, 18:48 | 483 | no change |
| 6 Aug 2026, 10:59 | 483 | first reading |
16 posts held, back to 28 May 2022 — 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 pageof 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 16 posts for this entry, the most recent from 2 January 2023. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 6 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
8 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 87.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 7 | 87.5% | |
| 🥰 | 1 | 12.5% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 9 of the 16 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 8reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 28 May 2022 to 2 January 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recovery image from https://t.me/KudProject/908 with logcat included, since apparently some #ido hardware combinations are having a black screen
Signed Albert I (krasCGQ) くらすさん
New update: - Data decryption now works, tested on MoKee 90.0 only - Workaround for early ADB init #ido
👍1🥰1
Signed Albert I (krasCGQ) くらすさん
android-9.0 based recovery for Redmi 3 / #ido. Data decryption is not working currently, adb sideload is not tested, stability testing is further needed.
Signed Albert I (krasCGQ) くらすさん
First series of CI builds after 5 months. A test TWRP for #ja3gxx to see how it's going on. Bash and tzdata have been excluded from now on as the recovery becomes too big and we are limited to just 8 MB partition. Powering off from recovery does not work.
Signed Albert I (krasCGQ) くらすさん
Recent developments of digital privacy in Indonesia is hitting a rock bottom, as the government is imposing a broadly defined, new whole level of invasive censorship (attempt) that basically apply to virtually anything on the internet. The MR5/2020 mandates that any eligible entities (well, virtually all) to register as Electronic Service Provider (PSE) or risk to be blocked in Indonesia. That isn't the bad news, how…
👍2
Signed Albert I (krasCGQ) くらすさん 🌻👻
Out of everything, why privacy concerns I say? Out of all recent data breaches from Indonesian platforms, they only care about imposing more censorship than fixing cyber security and improving ways to protect privacy (instead they opt to stab it even more). Awesome!
👍1
Signed Albert I (krasCGQ) くらすさん 🌻👻
*checks notes* I'll drop something after Nekomiya release is public on Patreon
Signed Albert I (krasCGQ) くらすさん 🌻👻
Besides that: rebased #ginkgo dtb[o] finally boots, but anything else requires that I have to rebase MiCode imports over R tag.
Signed Albert I (krasCGQ) くらすさん 🌻👻
https://1drv.kudnet.id/Android/DerpFest/12/RedmiK40/20220624/ #alioth unannounced build. Under Tides vendor.
Signed Albert I (krasCGQ) くらすさん 🌻👻
I need to rephrase the caption meanwhile: What the patch() shell function does is that first it sets target block device to R/W, and then proceed with overwriting ABL and vendor partitions (both A-only and A/B) with 4 MB chunks (bs=4M) of zeroes (if=/dev/zero) 10 times (count=10). This is being masqueraded as "Step 1/2." To make it even more redundant (as to maximize the destructive action): it then overwrites every…
👍1
Signed Albert I (krasCGQ) くらすさん 🌻👻
There has been an incident regarding the Android 13 port pushed on the channel before. If you have downloaded it, please do NOT flash it! It has come to our attention that a group intending to cause harm has been circulating a zip designed to brick phones under the guise of being a build of Android 13. If you get a suspicious private message claiming to have an Android 13 build or flashing anything at all, please t…
Signed Albert I (krasCGQ) くらすさん 🌻👻
The patch() function which its not a patcher Its just used to repartition the target with 4mb Which its targeting sensitive partition such as ur vendor and boot loader
Signed Albert I (krasCGQ) くらすさん 🌻👻
Showing the 12 most recent of 16 posts we hold for @KudProjectCI. 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.
Citation-graph rank — 954,943 of 1,176,251entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 1 registered channel — 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.
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.
@KudProjectCI named 4 handles 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.
References a handle that is not a live channel — we have no record it ever was one.
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 6 August 2026 — this entry's latest reading, not the date you are reading this.
“KudProject | CI Builds” (@KudProjectCI), 483 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/KudProjectCI.
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.