Channel
@jamesdsp_releases
On this record: Topic · Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry
1,531subscribers
+19 since we began measuring on 30 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001942937364 |
|---|---|
| Type | Channel |
| Username | @jamesdsp_releases |
| Created | Between 1 April 2023 and 22 July 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 30 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/jamesdsp_releases |
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 17 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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 |
|---|---|---|
| 15 Sept 2026, 21:39 | 1,531 | +5 |
| 12 Sept 2026, 10:37 | 1,526 | +2 |
| 8 Sept 2026, 12:35 | 1,524 | +4 |
| 3 Sept 2026, 05:53 | 1,520 | +7 |
| 30 Aug 2026, 19:54 | 1,513 | +1 |
| 30 Aug 2026, 02:15 | 1,512 | first reading |
19 posts held, back to 22 July 2023 — 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 19 posts for this entry, the most recent from 18 May 2026. An engagement rate over an empty window would be a number about nothing.
237 reactions across 15 posts, in 9 distinct kinds. The most used accounts for 40.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 95 | 40.1% | |
| 👍 | 89 | 37.6% | |
| 🔥 | 28 | 11.8% | |
| 🤯 | 12 | 5.06% | |
| 👏 | 6 | 2.53% | |
| ❤🔥 | 2 | 0.844% | |
| 🏆 | 2 | 0.844% | |
| 🥰 | 2 | 0.844% | |
| 😱 | 1 | 0.422% |
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 15 of the 19 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 237 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 22 July 2023 to 18 May 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.
⦁ Created post-fs-data.sh with apex mounting support if needed ⦁ Service.sh will now seek inside jdsp AIDL lib dependency, and modify it to match files in system (not need to add additional dependency files which might break functions of phone). This became useful for (example) newest oneplus firmwares, which have too new dependency files ⦁ JDSP during flash, if volume key will not be detected, will choose pbone U…
❤27🔥4🏆2👏2
* updated AIDL lib * updated PBone APK * updated patching script * AML compatibility for non-pixel AIDL devices (not needed for now, but still)
❤35🤯12🔥9😱1
v6.0 installer by @Zackptg5 Changelog: * mmtex v3.6 update (support for apatch and kitsune) (cr. @Zackptg5 and @ShadoV90) * Update pbone apk * Update jdsp app/libs
👍27❤9❤🔥2🥰2
File, posted without a caption
👍19👏3❤2
File, posted without a caption
🔥11❤4👍3👏1
Beta update for JamesDSP changelog from 5.8: bugfix update with some new refactoring for efficiency and easier tracing of any remaining bugs. Should be more stable than 5.8, but we're introducing it as beta first to catch any unexpected bugs. Will be renamed 5.9 official if everything's ok
👍13🔥3❤2
Sticker, posted without a caption
👍3
Changelog: * Update thepbone app to 9/10/23 version * Update jdsp libs/apk * mmtex v3.5 update - fix for magisk removing/renaming variables for no reason whatsoever 😡
👍7❤4🔥1
Newest libs and app from James, also new app from ThePBone (1.6.6-43 version). I made workaround in installation script. App should appear correctly (Jeez, code is more and more complex)
👍4
Changelog: Automatic lib arch detection (thx @Shadov90) MMTEx update Overall minor update - no changes to jdsp itself
👍2❤1
Test build - now has automatic 32/64bit lib detection. Thanks @ShadoV90
👍2
this would be the latest recommended version, however, there seem to have been some bugs with thepbone's version of the UI since some time ago. Haven't heard from @James34602 or @thepbone how we're going to deal with it. Affected modules seem to include convolver and DDC. If you are affected you may want to revert to the standard GUI for now
👍3❤2
Showing the 12 most recent of 19 posts we hold for @jamesdsp_releases. 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.
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.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“JamesDSP Releases” (@jamesdsp_releases), 1,531 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/jamesdsp_releases.
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.