Telegram RegisterThe public register of Telegram
Telegram profile photo for Mixilver's porting stuff

Channel

Mixilver's porting stuff

@mixilvers_stuff

On this record: Growth · Engagement · Posts · Citations · Cite this entry

128subscribers

+56 since we began measuring on 9 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004063806353
TypeChannel
Username@mixilvers_stuff
Created24 July 2026measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live19 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/mixilvers_stuff

Growth

721281009 August 2026 — 72 subscribers9 August 2026 — 72 subscribers17 August 2026 — 86 subscribers25 August 2026 — 101 subscribers31 August 2026 — 110 subscribers10 September 2026 — 124 subscribers19 September 2026 — 128 subscribers9 August 202619 September 2026
7 measurements spanning 41 days, net +56. 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 64–136 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 16:36128+4
10 Sept 2026, 06:20124+14
31 Aug 2026, 18:13110+9
25 Aug 2026, 16:34101+15
17 Aug 2026, 15:4686+14
9 Aug 2026, 23:0172no change
9 Aug 2026, 15:4872first reading

Engagement

6 posts held, back to 24 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 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 6 posts for this entry, the most recent from 24 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

24 Jul 2026, 13:42 UTC451 viewsread 9 August 2026

An OneUI 8.5 porting guide 1. Merge my props from archive 2. Add your com.android.vndk*.apex to system_ext/apex 3. Remove everything in product/etc/selinux/mapping and system_ext/selinux/mapping 4. Replace keystore2 in system/bin and add libkeyutils.so to system/lib64 5. Replace etc/group and passwd from oneui vendor to your 6. Force permissive in system/bin/init replace (1F0400710001005420008052 with 1F0400710

24 Jul 2026, 13:42 UTC410 viewsread 9 August 2026

8. For signal bars (they are empty on non-samsung devices) java -jar apktool.jar d framework.jar -o framework-src in smali_classes4/android/telephony/SignalStrength.smali find getVendorLevel method and replace it with .method public blacklist getVendorLevel()I .locals 3 iget v1, p0, Landroid/telephony/SignalStrength;->mPrimaryRadioTechnology:I if-nez v1, :cond_0 invoke-direct {p0}, Landroid/telepho

24 Jul 2026, 13:42 UTC469 viewsread 9 August 2026

9. For bluetooth python3 ./deapexer.py extract com.android.bt.apex replace libbluetooth_jni.so from archive java -jar apktool d javalib/service-bluetooth.jar -o service-bluetooth-src in service-bluetooth-src/smali/com/android/server/bluetooth/BluetoothManagerService.smali find getSecBTAIDLServiceMockable method and replace invoke-static {v2}, Landroid/os/ServiceManager;->waitForService(Ljava/lang/String;)Landroid/os/

Showing the 6 most recent of 6 posts we hold for @mixilvers_stuff. 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.

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.

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.

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

“Mixilver's porting stuff” (@mixilvers_stuff), 128 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/mixilvers_stuff.

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.