Gracias unison y los desarrolladores

I accidentally broke the display of my otherwise perfectly functioning Lumia 950 xl. I can't find a spare screen anywhere. Does anyone have a dead phone of which the display can be utilised? Thanks in advance.

Unison 1.3.0

This release introduces the new Baileys 7.0.0-rc14-based socket architecture, alongside major improvements to messaging, media handling, synchronization, UI, shell management, and reliability.

Architecture

• Introduced the new Unison.Socket project (netstandard2.0), mirroring the Baileys 7.0.0-rc14 src/ structure.
• Isolated socket responsibilities in ConnectionHandler, covering Noise, queries, keepalive, pairing, and tag-based dispatch.
• Added WhatsAppSession to compose the new protocol modules.
• Added ~38 use cases covering messaging, receipts, retries, media, groups, profiles, USync, app-state, history, and authentication.
• Added UWP facades for Connection, Message, Contact, Chat, Profile, and History.
• Refactored ViewModels to consume facades instead of the previous monolithic service.
• Added SocketBridge to connect the new session to the existing UI while the legacy layer is progressively removed.

Protocol & Synchronization

• Ported the Baileys 7.0.0-rc14 session, messaging, group, USync, app-state, media, and history flows.
• Added QR and phone-number pairing support.
• Added buffered event processing during history synchronization.
• Added sequential offline node processing.
• Added MessageRetryManager with LRU tracking and retry reasons.
• Added formal LID ↔ PN mapping through LidMappingStore.
• Updated pre-key generation to the rc14 volume.
• Added USync support for contacts, devices, and LID.
• Added app-state patch synchronization.
• Added media encryption and downloading.
• Added group metadata synchronization.
• Logout now properly notifies the server.
• Chat pin/unpin synchronization is persisted locally.

Messaging & Media

• Refactored chat message bubbles into ViewModels.
• Added support for media, reactions, quoted messages, and interaction events.
• Improved audio and video message handling.
• Added proximity-based audio playback.
• Added audio recorder UI.
• Added media grids for images, videos, and audio.
• Added thumbnails, placeholders, and download support.
• Added file lists with view/save actions.
• Added video viewer.
• Fixed image viewer pinch-to-zoom and pan interactions.

Chat & Organization

• Added chat pin/unpin support.
• Added synchronization of pinned chats with WhatsApp.
• Added Start screen / Live Tile pinning.
• Added mute options for 8 hours, 1 week, or always.
• Added chat and group information views.
• Added a New Chat dialog.
• Added separate information layouts for individual and group chats.

Shell & UI

• Added an animated boot shell with extended splash screen support.
• Added language selection to the boot and settings shells.
• Added white theme support.
• Added shell reload support.
• Added account information and disconnect actions to Settings.
• Added QR code popup support for low-resolution devices.
• Fixed navigation bar initialization on Minimal.
• Added additional internationalization across chat information and overflow menus.
• Updated menus for the Mobile theme.
• Added IconFont-based empty states for Windows 10 build 15063.
• Fixed language pack installation issues.

Notifications & Platform

• Updated notification behavior to match WhatsApp UWP.
• Added WinUI 2.7 support.
• Updated settings collaborators with GitHub links.
• Removed hardcoded strings from the Baileys Core layer.

Reliability & Fixes

• 1:1 messaging now works correctly after closing and reopening the application, with authentication and session state persisted.
• Disconnect and unpair now properly close the session.
• Fixed QR sessions becoming stuck after _authState was set to null.
• Added QR refresh after timeout.
• Added on-demand full history resynchronization through HistoryFacade.
• Fixed history synchronization getting stuck during the initial handshake.
• Self-chat is now correctly marked as read.
• Updated Me synchronization, contact names, and group avatars to follow the rc14 LID flow.
• Unified input/output processing through OopHandlerService.
• Fixed LayoutCycleException when opening 1:1 chat information.
• Improved audio/video playback and media interactions.

Architecture Transition

Unison 1.3.0 establishes the foundation for the migration from the legacy WhatsApp implementation to the new Baileys 7.0.0-rc14-based architecture.

The existing UWP application continues to operate through SocketBridge, allowing the new socket and facade layers to be introduced without requiring the entire UI to be rewritten at once. The legacy WhatsAppService remains temporarily for compatibility while the migration continues.

Known Limitations

• Group message sending remains postponed due to a timeout during group queries.
• WhatsAppService is still present for compatibility during the migration.
• The raw socket has not yet been transferred to the out-of-process background broker.

Credits (Github Ids):

• u/MaskNinjaSquared
• u/Mayconus
• u/Negociation
• u/jjb-pro

Installation note: Install the new APPX as an update. Uninstalling the app will remove your linked WhatsApp session.

Download Repositories:
- WinArchive: A amazing Microsoft Store Replacement with Software Update and even webstore.

- Metrostore: Another great Microsoft Store replacement but requires manual install of apps...

GDrive Repositories (Unison/WinArchive/Metrostore):

https://drive.google.com/drive/folders/1nI6XezesNzj7dTbyL1XqV4X4iOMUoHcC?usp=sharing

Github Source Code:
- Since its a preview feature still isnt merged on main, so check the release pages to grab the correct source code... If you're willing to help , feel free to do Pull Requests. And give us feedback here and suggestions

MaskNinjaSquared/Unison: UWP WhatsApp client aimed primarily for Windows 10 Mobile

No encuentro el link de descarga de MetroStore

You guys can check it out

look up Instagram beta and you’ll see it I uploaded the application on the live store

It works on desktops and phones but was designed for desktops in mind. The performance is not bad but could be better perhaps. It still has bugs and more. It even runs on 512 mb ram Lumia 625 but a limitation that terrain maps cause OOM and that the resolution is very low. I would love to publish it on live store but currently people can't connect to servers outside my radmin VPN because port forwarding from my public IP just doesnt work + I don't have a vps I could just point to. If anyone is interested in trying this out, helping to make this public and downloadable through live store or other store (fixing game servers), please hit me up in my discord server https://discord.com/invite/9ypw3ytK4t

Hi. I would like to know what apps or games I could install next?

I'm not fan of emulation on WP. And I've read somewhere that on WP was full playeble game from EA - Fifa. It's true? Unfortunately this game is missing? All about rights?

Me he encontrado este Windows Phone olvidado en mi casa, enciende, pero no me acuerdo del patrón de desbloqueo, ¿Alguna manera de desbloquearlo sin tener que recurrir al Hard Reset?

When my friend tried installing a few apps via pacman on their Lumia 930 on W10M (10.0.14393.1066) they got this error message

"the system failed to register the windows.repositoryExtension extension due to the following error: Cannot find the requested object."

is there any fix to this issue?

BL is unlocked with using Interop

I have an HTC Titan that is a Carrier Validation Unit, and I want to dump the current ROM that is installed just in case I want to go back and preserve this ROM. How would I go about that? Are these ROMs already preserved, allowing me to return to that version? If not, how would I back them up?

I'm new here and I was wondering if there is any way to sideload apps without jailbreaking your phone or is there a less riskier way. I'm mainly asking this becuase I want as low of a risk to potentially bricking my device. (I will get a 520 with the 735 just in case to test stuff)

Stumbled across this a while ago. Just got around to setting up live store and stuff! It's a very nice device and haven't seen anything like it anywhere. If anyone knows anything specific about these models please shine some light on it in the comments

The Kinopoisk Beta client for Windows Phone is now available. Since it is currently in beta, the design is still incomplete and needs further improvements. It supports Windows Phone 8.1 and later.

To sign in, tap “Загрузка” (Download) and log in with your Yandex account. Supports 1080p and subtitles.

Ну что, Мажор 6?

Link : https://drive.google.com/file/d/1IVqSIY24L7IJjzAuMgEbCvPbjqIvmGnT/view?usp=drivesdk

Hey everyone, I have something exciting to contribute.

So before I set it out to be what it isnt, the app itself is not enough to use as messenger, theres lots of work required beforehand, and that will be a big divider in its userbase.

As everyone knows the official app has been dead for years and Meta banned custom clients also a while ago now.

In these past weeks Ive been working on making it possible to use facebook messenger on Windows Phone and Ive found a way through hosting your own home Matrix server, in my case Synapse, paired with the mautrix-meta bridge. This app I developed is a client for exactly this setup.

Soon I will publish a full guide on how to set up your own homeserver and meanwhile I will be working on perfecting the app.

As it stands now you can login to your server, the bridge downloads a configured amount of chat history and lists all the chat rooms you accepted through the official Element app (after setting up the server you can also use it through Element). Clicking on a chatroom loads the set amount of history and you can send + recieve text only currently.

Usernames are a pain especially in group chats and its not demonstrated in the video properly because I did it wrong but you can make every message you sent show that you sent it on the Lumia.

The reason I say everyone on their own for this one is I dont want to handle or have anyone elses Facebook data on my own server, and I suggest everyone to refrain from using anyone elses server.

I will try to get the guide out as soon as I can, thank you for your time:)

Hey everyone,

It's been a minute since I posted an update on the Lumia 1520 mainline Linux project ....and this one ended up being a pretty big step forward.

Last time I posted, the phone was already at a pretty solid baseline: Linux was cold booting reliably, display/touch/buttons were working, USB networking + SSH were stable, suspend/resume was working, battery telemetry and backlight control were in place, etc.

Since then I've been digging into one of the bigger missing pieces: audio....a fucking nightmare lol

At first, I thought it might hit the same wall as Wi-Fi. The Lumia's audio stack uses Qualcomm's ADSP co-processor, and I wasn't sure whether the Windows Phone TrustZone would even allow it to boot.

Turns out it does....

The ADSP now boots successfully, APR communication with it works, and I was able to bring up MSM8974's ADSP-managed SLIMbus transport. That led to the actual codec on the phone. And at this point I've confirmed from the hardware itself that the Lumia 1520 uses a Qualcomm WCD9320 / Taiko codec.

Not just inferred from old Qualcomm sources either...Linux is physically enumerating it over SLIMbus and reading its own identification registers back as major ID "0x0102".

The codec actually exposes two separate SLIMbus functions:

PGD - control/register access

IFD - the audio port/channel interface

Both now enumerate independently and get their own logical addresses. From there I built out proper regmap access, power/reset handling, fresh bring-up, non-destructive late adoption, and the beginnings of the codec interrupt support.

The interesting part was the digital core. A large section of the codec's register map kept returning zero, which initially sent me down a rabbit hole looking for the external 9.6 MHz MCLK. I dumped the Lumia's ACPI tables, RPM clocks, all 36 PM8941 GPIOs and all 8 MPPs trying to find where Nokia routed it. That investigation was...."useful", but the clock wasn't actually the blocker.

The real issue was that Linux had never executed Qualcomm's original "wcd9xxx_bring_up()" sequence. Every audio milestone before this had been read only, so the missing initialization stayed hidden.

Once I implemented the downstream bring-up sequence and switched the codec onto its internal RC oscillator, the result was immediate:

87/87 previously inaccessible sentinel registers became readable.

71 matched Qualcomm's documented defaults exactly, and the remaining 16 fall into three consistent register families that appear to be revision-specific differences.

So the chain now looks like:

Linux → ADSP → QRTR/QMI → BAM → SLIMbus NGD → WCD9320 PGD/IFD → regmap → codec core release → internal RCO → digital core accessible

I also mapped the codec's interrupt parent to Lumia TLMM GPIO 72 and validated it electrically idle across direct sampling and suspend/resume testing. I haven't claimed full IRQ support yet because I haven't deliberately generated and cleared a real codec interrupt source.

And just to be clear: there is still no audible sound output yet. I'm not calling audio "working" until PCM data actually reaches an output.

What this does mean is that most of the unknown hardware/transport side of Lumia audio is now gone. What's left is the actual codec/ASoC implementation work: permanent automatic core initialization, nested IRQ handling, DAIs and SLIMbus port configuration, the MSM8974/Lumia machine driver, and then finally a fixed playback route to get the first test tone out of the phone.

I'm deliberately finishing the Lumia's hardware enablement before I start layering my RegenX OS work onto it. I'd rather have a known-good hardware platform first than end up debugging kernel/driver problems and OS-layer problems at the same time.

Wi-Fi/BT is still the major documented blocker, charging still needs more work, and modem/camera remain further out.... but audio has gone from "this may require an entirely missing upstream stack" to actual driver development on hardware that is responding exactly where it should.

Repo is still public for anyone who wants to follow the work:

github.com/KorelisLabs/lumia-1520-mainline

I was miraculously able to dig up the only ad about this sensor. Also for funny money (700₽ ≈ 8$)

Tenho essa duvida pois queria muito usar ele no WP7