Photo, posted without a caption
Signed H 1

Channel
@gcam_releases
On this record: Topic · Growth · Engagement · Reactions · Posts · Polls · Citations · Cite this entry
7,416subscribers
-106 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001225968982 |
|---|---|
| Type | Channel |
| Username | @gcam_releases |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/gcam_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 12 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 |
|---|---|---|
| 18 Sept 2026, 22:20 | 7,416 | -12 |
| 14 Sept 2026, 14:39 | 7,428 | -6 |
| 11 Sept 2026, 06:21 | 7,434 | -8 |
| 6 Sept 2026, 09:38 | 7,442 | -15 |
| 2 Sept 2026, 01:25 | 7,457 | -7 |
| 30 Aug 2026, 05:53 | 7,464 | -2 |
| 26 Aug 2026, 22:56 | 7,466 | -10 |
| 23 Aug 2026, 14:45 | 7,476 | -11 |
| 19 Aug 2026, 15:03 | 7,487 | -10 |
| 16 Aug 2026, 14:39 | 7,497 | -6 |
| 13 Aug 2026, 03:15 | 7,503 | -11 |
| 10 Aug 2026, 10:31 | 7,514 | -6 |
| 7 Aug 2026, 02:05 | 7,520 | -2 |
| 6 Aug 2026, 15:00 | 7,522 | no change |
| 6 Aug 2026, 14:57 | 7,522 | first reading |
18 posts held, back to 18 October 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 17 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 18 posts for this entry, the most recent from 13 March 2026. An engagement rate over an empty window would be a number about nothing.
19 reactions across 10 posts, in 3 distinct kinds. The most used accounts for 42.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 8 | 42.1% | |
| 🥰 | 6 | 31.6% | |
| 🔥 | 5 | 26.3% |
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 18 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 19 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 18 October 2022 to 13 March 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.
Photo, posted without a caption
Signed H 1
File, posted without a caption
👍1🔥1
Signed H 1
Indoor sample. Now imagine how good the outdoor ones will be! (Problem is, Marco has limited access to his begonia and the cam does not work on android 11. Try and send feedback (good one or I will ban you 😜)
🔥1🥰1
Signed H 1
#begonia #XML #AGC #BigKaka Xml for Redmi Note 8 Pro (probably won't work on other phones) by: @gasssgg This is made for AGC9.2.14_v14.0 , don't use on other versions (won't be compatible) Get the cam from here (tap the underlined "here" word, then download the first link) -The viewfinder will have a bit of lag (unfortunately), but it's the best GCam for this phone (in the creator's opinion) and he guarantees res…
🔥3
Signed H 1
Config for LMC 8.4 release 18. Used for sharp, slightly saturated pictures ideal for nature. Shoots in 64 mp by default. To get LMC, head to celsoazevedo.com and go to Hasli mods (yes, this requires the use of your eyes to read and fingers to tap blue text thingies) Samples > https://t.me/googlecameraglobal/636125?single Join @googlecameraglobal for discussion
🥰5
Signed H 1
Are you interested in seeing a comparison between Redmi Note 8 pro (stock/gcam) and iPhone 12 pro?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
👍1
Signed H 1
#rn8p #begonia #burial10 #7.x This is not the greatest config in the world, no! This is a tribute :) See this for reference: https://www.youtube.com/watch?v=_lK4cX5xGiQ (not a rickroll video, I promise) Anyways. This is the config I'm currently using on Burial 10 Works fine, colors seem good to me and the noise is quite good in my eyes (more noise than your average config). Modified small values here and there a…
👍2
Signed H 1
Which one do you think is better?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
👍1
Signed H 1
Here are two images taken with two different configs. Distance, lighting, and focus are the same on both, the different is in Luma denoising... I know most people prefer noise-free photos, but this always comes at the cost of details (you can read the text better on the noisy one, plus the wall is actually textured but you can't see that well on the config with noise reduction enabled. And now comes a poll, just fo…
👍1
Signed H 1
Enable Auxiliary lenses on OpenCam (possibly other apps): #tutorial #root #opencam #begonia #redmi_note_8_pro OpenCam does not detect auxiliary lenses properly on stock MIUI on RN8P, so to force enable them, try the following. - Using any root explorer, go to Root/etc/device features - Make a backup of "begonia.xml" - Open "begonia.xml" - Look for the line that says "Camera_aux_package_list" - Add this line to the…
Signed H 1
ℹ️ GCam 9.0 and older Android versions: While the original GCam 9.0 requires Android 14, GCam 9.0 mods should work on Android 12 and above. Those stuck on older Android versions have to use older GCam bases (v8, v7, v6).
Signed H 1
#rn8p #begonia #BigKaka #AGC #8.x A config for BigKaka's AGC8.8.224_V4.0 Has three additional modes tuned on main cam: - Light and saturated - Black and white - Blue and red (less green) filter You can access the modes from the top right button. Other lenses are not tuned properly (and probably will never do it as I'm happy with burial 10) This config is made for my personal use, using the values I am comfortabl…
👍1
Signed H 1
Showing the 12 most recent of 18 posts we hold for @gcam_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 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
Are you interested in seeing a comparison between Redmi Note 8 pro (stock/gcam) and iPhone 12 pro?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Which one do you think is better?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 18 most recent posts we hold, published 18 October 2022 to 13 March 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“GCAM Releases and devblog” (@gcam_releases), 7,416 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/gcam_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.