Telegram RegisterThe public register of Telegram
Telegram profile photo for krenlol

Channel

krenlol

@krenlol

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

2,759subscribers

-14 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002071744973
TypeChannel
Username@krenlol
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/krenlol

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 15 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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

2,7592,7732,7667 August 2026 — 2,773 subscribers8 August 2026 — 2,772 subscribers13 August 2026 — 2,771 subscribers16 August 2026 — 2,768 subscribers19 August 2026 — 2,766 subscribers22 August 2026 — 2,769 subscribers25 August 2026 — 2,770 subscribers31 August 2026 — 2,771 subscribers2 September 2026 — 2,769 subscribers7 September 2026 — 2,765 subscribers11 September 2026 — 2,764 subscribers15 September 2026 — 2,759 subscribers7 August 202615 September 2026
12 measurements spanning 39 days, net -14. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 2,757–2,775 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 12:562,759-5
11 Sept 2026, 17:192,764-1
7 Sept 2026, 07:412,765-4
2 Sept 2026, 21:252,769-2
31 Aug 2026, 04:252,771+1
25 Aug 2026, 12:072,770+1
22 Aug 2026, 21:552,769+3
19 Aug 2026, 16:122,766-2
16 Aug 2026, 17:072,768-3
13 Aug 2026, 11:132,771-1
8 Aug 2026, 02:562,772-1
7 Aug 2026, 08:182,773first reading

Engagement

14 posts held, back to 27 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages 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 14 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

102 reactions across 12 posts, in 14 distinct kinds. The most used accounts for 28.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥2928.4%
🤡2827.5%
🤯1716.7%
👍87.84%
🍌54.90%
💩54.90%
😁21.96%
🤔21.96%
10.98%
👏10.98%
😐10.98%
😢10.98%
🥰10.98%
🥴10.98%

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 12 of the 14 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 102 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 14 most recent posts we hold, published 27 July 2026 to 5 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

5 Aug 2026, 01:12 UTC354 views11 reactionsread 7 August 2026
Photo

LineageOS 23.2 Unofficial, A16 QPR2 for Redmi Note 10, mojito/sunny changes from last build - Aug 2026 ASB - blur enabled, kawase2 - kernel: merged LOS sm8150 / sm6150 common https://github.com/ximi-mojito/mojito_manifests/releases/tag/20260805 #mojito #A16 #QPR2

🍌5👍4💩1🥴1

4 Aug 2026, 16:59 UTC593 views21 reactionsread 7 August 2026
Photo

Photo, posted without a caption

🔥11🤡6😁2👍1😐1

2 Aug 2026, 08:34 UTC547 views5 reactionsread 7 August 2026
Photo

theres also this small change on branch link instead of using function pointers, we can generate stub functions that are basically just naked traps we just patch those stubs at runtime to call the kernel function back, removing the need for function pointers and completely avoid blr overhead. -- on its early state, I had it unoptimized which takes like 6~10 instructions then I had it down to 1 insn on clang and 2

🤡3🔥2

2 Aug 2026, 08:24 UTC480 views4 reactionsread 7 August 2026
Photo

small change on the driver if youre building built-in and on AUDIT && ARM64 && KALLSYMS, the driver will now attempt to hijack slow_avc_audit via branch link. as for handling / choosing which fn prototype is apt for you kernel, this is done at buildtime by overloading fn typeof via C11's _Generic https://github.com/backslashxx/KernelSU/blob/master/kernel/downstream/slow_avc_audit_defs.h - this is actually my first

🤡3👍1

2 Aug 2026, 07:54 UTCviews —

krenlol pinned «I updated kernels on these - daisy / Mi A2 Lite https://github.com/ximi-daisy/daisy_manifests/releases - i9300 / Samsung Galaxy S3 https://github.com/samsung-i9300/i9300_manifests/releases - libra / Mi 4C https://github.com/ximi-libra/libra_manifests/releases…»

2 Aug 2026, 07:54 UTC457 views5 reactionsread 7 August 2026

I updated kernels on these - daisy / Mi A2 Lite https://github.com/ximi-daisy/daisy_manifests/releases - i9300 / Samsung Galaxy S3 https://github.com/samsung-i9300/i9300_manifests/releases - libra / Mi 4C https://github.com/ximi-libra/libra_manifests/releases - mojito / Redmi Note 10 https://github.com/ximi-mojito/mojito_manifests/releases Changes: - updated KSU 32567 - backported sys_faccessat2 on libra, daisy

🤡3👍2

1 Aug 2026, 01:21 UTC645 views7 reactionsread 7 August 2026
File

so I guess no issues in the foreseeable future. hooking will not be a problem for a while.

🤡3🤯31

29 Jul 2026, 23:31 UTC868 views21 reactionsread 7 August 2026
Photo

kek, its so fast now I'm proud from 18s dropping to 4s andthen further drropping to 0.25s yeah I guess it is viable, I might as well forego kallsyms_on_each_symbol lookup is good too, unordered array on flat realloc its just so fast since we get sequential memory access

🔥16🤡2👏1🥰1😢1

28 Jul 2026, 22:09 UTC895 views2 reactionsread 7 August 2026

https://ir.latticesemi.com/news-releases/news-release-details/lattice-semiconductor-completes-acquisition-ami

🤡2

27 Jul 2026, 08:17 UTC973 views2 reactionsread 7 August 2026
Photo

and yeah, as I said, this is an attempt. if it fails, it will keep sct hook for the symbol. especially for < 4.17, there is no "do_faccessat" so if its not backported, youll only see newfstat + execve on branch link at best. and theres also that isra problem on gcc, however, this is also handled, no attempts will be made to patch isra gcc calls for more info https://www.google.com/search?q=gcc+isra lto_priv.0 on g

🤡2

Showing the 12 most recent of 14 posts we hold for @krenlol. 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Mentions

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

APatch Updates
@APatchChannel · 25,141
Telegram ranks this channel #8 of 37 here — alongside 36 others — read 14 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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 15 September 2026 — this entry's latest reading, not the date you are reading this.

“krenlol” (@krenlol), 2,759 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/krenlol.

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.