Channel
@LumiaWOA_Announcements
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
2,039subscribers
+10 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001228781569 |
|---|---|
| Type | Channel |
| Username | @LumiaWOA_Announcements |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/LumiaWOA_Announcements |
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 16 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 |
|---|---|---|
| 15 Sept 2026, 23:22 | 2,039 | +1 |
| 12 Sept 2026, 11:16 | 2,038 | +3 |
| 8 Sept 2026, 19:00 | 2,035 | +2 |
| 30 Aug 2026, 19:26 | 2,033 | +2 |
| 27 Aug 2026, 19:14 | 2,031 | -1 |
| 21 Aug 2026, 07:22 | 2,032 | +2 |
| 11 Aug 2026, 10:06 | 2,030 | +1 |
| 7 Aug 2026, 22:00 | 2,029 | no change |
| 7 Aug 2026, 21:55 | 2,029 | first reading |
20 posts held, back to 13 October 2024 — 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 20 posts for this entry, the most recent from 24 December 2025. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
742 reactions across 20 posts, in 7 distinct kinds. The most used accounts for 58.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 435 | 58.6% | |
| 🔥 | 99 | 13.3% | |
| 🎉 | 73 | 9.84% | |
| 👍 | 61 | 8.22% | |
| 😢 | 30 | 4.04% | |
| 😁 | 23 | 3.10% | |
| 😱 | 21 | 2.83% |
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 20 of the 20 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 742 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 13 October 2024 to 24 December 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Merry Christmas and happy end of the year holidays on behalf of the LumiaWOA team. Sorry not much this year but this project and the phones are quite old by now. Quite impressive there are still people holding on to these devices and the news of this project. Wishing you the best.
❤53👍13🎉5
Here is the latest codebase build of the UEFI for Hapanero devices if you need it (built today)
🔥12❤3
a new dedicated "lumia" branch was created in the firmwaregen repository to host the last known good codebase that works for lumias and building ffu files with woa in them https://github.com/WOA-Project/FirmwareGen/tree/lumia the latest tree of firmwaregen is more suited for building images for newer snapdragon devices (such as surface duo devices) and is incompatible with lumias, so this was needed
❤7
Note for developers: we also made the Lumia950XLPkg repository buildable out of the box again today by pinning the specific EDKII commit that is last known to work fine (i am sure theres newer but this will do for now) on top of which, I added back files for hapanero too so for folks with those devices, you can rebuild an image today. https://github.com/WOA-Project/Lumia950XLPkg
❤11
Photo, posted without a caption
🔥32
Updated FFU files with latest NI_RELEASE Windows 11 Build (last compatible) and latest drivers Hello everyone we made available brand new ffu files containing the latest CU for NI_RELEASE available as of this month (the last compatible windows version for the Lumia 950 series of devices) and with the latest driver versions (so you can run your dolphin x86 gpu app friends) More info and downloads, 👉 https://fullflas…
🔥15❤2🎉1👍1
Updated version of the kit to build FFUs yourself (ie. without us, without us having to answer questions too ;) ) Works with the latest driver pack and is optimized for vintage Intel64 and modern amd64 machines only. Q&A: Q: wildcard? A: Read the readme file inside the ZIP
❤18👍3
Hello everyone just a small status update to let you know that we updated the ffu download web page to be, well lets not write 5000 words and be quite direct here, miles better hope thats more useful/easy to use and navigate into https://fullflash.pvabel.net/LumiaWOA/FFUs/ if i find the time i could also maybe make more up to date ffu images but for now this should be a good thing, happy holidays
❤34👍5🎉4🔥3
Hoot hoot Hoo hoooo BOO Happy Halloween!
😁21😱15🔥9👍2
letting that thing rest for good is probably the soundest thing now
❤45😢30👍7
Happy 10th anniversary Cityman (950 XL) and Talkman (950) Final build series (Fx) Time flies, but calls stopped counting too soon
❤51🔥6👍4🎉3
Dolphin Universal Sample application compiled for x86 if you ever want to try that app
❤20👍1
Showing the 12 most recent of 20 posts we hold for @LumiaWOA_Announcements. 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.
Named by 2 registered channels — 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.
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.
“LumiaWOA Announcements” (@LumiaWOA_Announcements), 2,039 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/LumiaWOA_Announcements.
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.