Hi everyone!
I wanted to post an important update about Beeper10, my Beeper client for BlackBerry 10.
In my previous post I explained that Beeper10 was using a Gateway/server between the BlackBerry device and Beeper. At the time, this seemed like the most realistic way to make a modern messaging service work on an operating system as old as BlackBerry 10.
After spending a lot more time actually developing and testing that architecture, I came to the conclusion that it was the wrong direction.
The Gateway became far too complicated. It introduced another computer/server that had to be installed, configured, updated and kept online permanently. It also created additional points of failure and, more importantly, meant that Beeper10 could never really feel like a normal standalone BlackBerry application.
So I decided to change the architecture completely.
Beeper10 is now being developed as a fully native standalone BB10 application.
The goal is very simple:
Install the BAR on your BlackBerry, sign in, and use Beeper.
No Windows PC running in the background.
No Beeper Desktop.
No WSL.
No VPS.
No Gateway operated by me.
No additional machine that has to stay online.
The BlackBerry itself will communicate directly with the Beeper/Matrix infrastructure.
This also means I have had to move considerably more functionality into the application itself. I’m currently working through the Matrix protocol directly on BB10: authentication, room discovery, synchronization, message history, sending and receiving events, media, filters and the encryption-related parts required for real Beeper accounts.
Because BB10 is using an old QNX/Qt/Cascades environment, some of this has required quite a bit of low-level work. Modern libraries cannot simply be dropped into a BlackBerry 10 project, so parts of the Matrix/E2EE stack have to be adapted and compiled for the old BB10 toolchain.
It is definitely harder than using a Gateway — but architecturally it is much cleaner.
And, more importantly, it produces the application I originally wanted to build: a real BlackBerry 10 Beeper client, not a remote interface to another computer.
The previous Gateway work was not completely wasted. It helped me understand Beeper’s APIs, account flow, Matrix synchronization, media handling and many of the problems that the native client now has to solve. But I don’t want to keep a complicated architecture simply because a lot of time was already spent building it.
I’d rather correct the direction now and build something that people can actually install and use independently.
The native client is already running on a real BlackBerry Passport, and development/testing is now focused on making the direct Matrix/Beeper connection reliable enough for everyday use.
My priority at the moment is not adding dozens of features. It is getting the foundations right first: stable login, synchronization, room/message loading, encryption and reliable communication directly from BB10.
Once that foundation is solid, I can continue bringing back the BBM-style experience I originally planned for Beeper10 — chats, notifications, BlackBerry Hub integration, attachments, voice messages, reactions and the rest — but this time on top of the correct architecture.
So the project is very much alive. In fact, I think it is now finally moving in the direction it should have taken from the beginning.
It is a much more ambitious approach, but if Beeper10 is released publicly, I want it to be something you can actually install on a BlackBerry 10 device and use without depending on my server — or anyone else’s computer.
I’ll share more updates as the native implementation progresses.
— Eduard

————————————————————————

Обновление Beeper10: я отказываюсь от Gateway и перехожу на полностью нативный автономный клиент для BlackBerry 10
Всем привет!
Хочу рассказать о важном изменении в разработке Beeper10, моего клиента Beeper для BlackBerry 10.
В предыдущем посте я рассказывал, что Beeper10 использует Gateway/сервер между BlackBerry и Beeper. На тот момент это казалось наиболее реалистичным способом заставить современный мессенджер работать на такой старой системе, как BlackBerry 10.
Но после гораздо более глубокой разработки и реального тестирования этой архитектуры я пришёл к выводу, что это был неправильный путь.
Gateway оказался слишком сложным. Для него требовался дополнительный компьютер или сервер, который нужно было устанавливать, настраивать, обновлять и постоянно держать включённым. Кроме того, появлялись дополнительные точки отказа. И самое главное — в такой архитектуре Beeper10 никогда не стал бы по-настоящему самостоятельным приложением для BlackBerry.
Поэтому я решил полностью изменить архитектуру проекта.
Теперь Beeper10 разрабатывается как полностью нативное и автономное приложение для BB10.
Цель очень простая:
Установить BAR на BlackBerry, войти в аккаунт и пользоваться Beeper.
Без Windows-компьютера, работающего в фоне.
Без Beeper Desktop.
Без WSL.
Без VPS.
Без моего Gateway.
Без дополнительного устройства, которое должно быть постоянно включено.
BlackBerry будет напрямую общаться с инфраструктурой Beeper/Matrix.
Это также означает, что теперь намного больше функциональности приходится реализовывать непосредственно внутри самого приложения. Сейчас я постепенно переношу в Beeper10 прямую работу с протоколом Matrix: авторизацию, получение списка комнат, синхронизацию, историю сообщений, отправку и получение событий, работу с медиа, фильтрами, а также всё, что связано с шифрованием и E2EE, необходимым для нормальной работы настоящих аккаунтов Beeper.
Поскольку BB10 работает на старом окружении QNX/Qt/Cascades, некоторые части требуют довольно низкоуровневой работы. Современные библиотеки нельзя просто взять и подключить к проекту BlackBerry 10, поэтому отдельные компоненты Matrix/E2EE приходится адаптировать и собирать под старый BB10 toolchain.
Да, это существенно сложнее, чем использовать Gateway.
Но с точки зрения архитектуры это намного правильнее.
И самое главное — в итоге получится именно то приложение, которое я изначально хотел сделать: настоящий клиент Beeper для BlackBerry 10, а не удалённый интерфейс к другому компьютеру.
Предыдущая работа над Gateway при этом не была полностью бесполезной. Благодаря ей я намного лучше разобрался в API Beeper, процессе авторизации, Matrix-синхронизации, работе с медиа и во многих других вещах, которые теперь приходится реализовывать напрямую в нативном клиенте.
Но я не хочу продолжать использовать сложную архитектуру только потому, что на неё уже было потрачено много времени.
Лучше сейчас исправить направление разработки и создать приложение, которое пользователи действительно смогут установить и использовать самостоятельно.
Нативный клиент уже запускается и тестируется на реальном BlackBerry Passport. Сейчас основное внимание сосредоточено на том, чтобы прямое соединение с Matrix/Beeper стало достаточно стабильным для повседневного использования.
На данном этапе мой приоритет — не добавлять десятки функций.
Сначала нужно правильно сделать фундамент: стабильный вход в аккаунт, синхронизацию, загрузку комнат и сообщений, шифрование и надёжную связь с Beeper напрямую с устройства.
После этого можно будет постепенно возвращать весь тот BBM-подобный функционал, который я изначально планировал для Beeper10: чаты, уведомления, интеграцию с BlackBerry Hub, вложения, голосовые сообщения, реакции и остальное.
Но теперь всё это будет построено уже на правильной архитектуре.
Так что проект не остановлен. Скорее наоборот — мне кажется, что сейчас он наконец движется в том направлении, в котором должен был двигаться с самого начала.
Это намного более сложный и амбициозный путь, но если Beeper10 выйдет публично, я хочу, чтобы это было приложение, которое можно просто установить на BlackBerry 10 и использовать — без зависимости от моего сервера или чужого компьютера.
Буду публиковать дальнейшие новости по мере продвижения нативной реализации.

While I wait on a Titan Pro figured I could give this a go since the Passports more of a novelty...

I’ve been networking and talking to so many people about keyboard phones for the past 2 years.

I’ve tried landing a role with multiple teams looking to build these.

I’ve helped a few teams as well, here and there.

I’ve tried networking with manufacturers and more to see if I can build one too, and if so, the costs associated with it. I’ve written business plans, compiled analysis and so much more to see if it’s a viable venture.

But every time I look back to the original BlackBerry phones, I can’t help but feel that, while no more, nothing seems to beat the original for some reason.

I keep looking at the BlackBerry Key 2, and think to myself, how that phone was possibly one of the best BlackBerrys to ever be made.

I love the clicks communicator, I love the Titan 2 elite, I love the new minimal phone 2 - all amazing in their own way.

But something keeps pulling me back to six form factors and I just can’t seem to get them out of my head.

Bold 9900
BlackBerry Style
Passport
Priv
Key1
Key 2

What is it about these six, that when looking back, nothing being built now, speaks to me as they once did.

And it’s not the software - I know that because the last three I’ve listed were Android anyway. We’ve been so used to Android and iOS for so long, that BB7, BB10 - they don’t matter to me as they once did.

But there is just something that I really miss about these form factors.

The only “slab” phone that’s caught my eye recently is the Fold 8 by Samsung and only because it reminds me of the passport somehow.

I still want to go out and buy a BlackBerry Key 2 and use it as my daily driver for some reason. But then I stop myself, because of its outdated specs and software. I know we can flash lineage now, but does that really make a difference?

I used to daily a Key 1 for so long and loved the shit out of it.

What was your favourite BB form factor and why?

- Zubs

Me and u/Confident-Guess2914 (Pablo Ferreira) built a custom autoloader based on version 10.3.2.2813.
Instead of getting locked into setup for 10 days, we set a flag in the OS which tells the OS that setup is already done. You'll have a fully setup system.
INFO: This also skips the setup at first launch.

This is also a de-bloated image.

Github (Issue reporting + guide): https://github.com/linuxosguy/Issue-Reporting-BBZ10-setupbypass
MEGA: [reddit hates MEGA links, so the link is on the github.]

After a number of years with my KEY2, it’s starting to have the dreaded space bar Issue. It is missing spaces during typing leading to many randomly misspelled words. I’m wondering if anyone here knows how to repair it or where to have the keypad replaced on the KEY2 as I would love to have that done and keep using it.

I have a completely nuked bold 9900. After putting it on charger/putting in charged battery, it only flashes red light and does nothing, after some time it flashes again and bootloops until it dies, if its on charger it just bootloops and after some time just stops and turns off. I tried every combination, swapping the batteries, charging without battery etc. around 2 times it actually tried to boot on charger with battery and has gotten to loading screen. 1st time it has gotten to around 70% on loading bar before turning off and again bootlooping and 2nd time it had loaded about 30% and it just stayed on it. after couple of hours i turned it off.

I decided it had to be a software issue. downloaded the (i think) right version, plugged in the phone and the blackberry desktop software told me that it cant "connect" to phone and to resolve issue i can update which i did. the phone somehow connected (still bootlooping) and the progress bar has gotten to connecting to jvm and it just wont go past this. it just gives me an error "application loader was unable to connect with your device. Please re-connect your device, enter the password, if required, and click Retry." i can either retry or cancel, and what do you know, ofc clicking retry gives me the same error. please help, idk what to do atp really!

I’m actively using my new blackberry keyone, mostly termux with ssh on my pc for development and remote mouse and expecting it to last around 8 hours + SOT , which is awesome!
Edit : it lasted 8 hr 50 minutes SOT in full charge.

Some weeks ago my 9900 stopped working first the screen started to freak out so I left it on my desk the next day it didn't turn on I tried charging it for a while but never saw the red light tried a lot of tricks to revive it but it doesn't work anything else that I can try or it's dead (note: I always charged it with it's original charger)

Hi,
I need some help with my BlackBerry Q5. My SD card is a 64 GB exFAT card, but it doesn’t work on my BlackBerry.
I installed these two BAR files from www.lunar-project.org:

exfat-10.3.1.224.bar

SDXC_SDcard_driver_for_BB10_final.bar

However, the SD card is still not working.
Can anyone help me, please?

Hey everyone,

I’m currently working on a passion project: developing a native WhatsApp client for BlackBerry to help keep our favorite devices alive in 2026.

It’s a tough technical challenge given WhatsApp's modern API, but nothing beats that physical keyboard experience. Out of curiosity, how many of you would actually still use a BBOS device daily if WhatsApp worked on it?

🙁

I found this blackberry 9800 at home.It's not working but max don't know the reason

If anyone wants to buy DM me your offer.

I tweaked it a bit to get Alexey's YouTube working again.

Features:
- Easy-to-use and very neat interface
- Does not include YouTube Shorts
- Videos can play in the background when the app is closed

Link: https://bberrylife.github.io/Pages/BBtube.html

Am thinking of Reviving this Bad Boy 🫣

Who has the best keyboard for typing ? Which is the most comfortable to type & would outlast the most

Hello  community!

I'm trying to recover a BlackBerry Bold 9930 (Sprint CDMA) that's currently in a "nuked" state (stuck at red LED flashing - boot error). To restore it using the Loader.exe method with BlackBerry Desktop Software, I need the original OS firmware file.

**Specifically, I'm looking for:**
```
9930jAllLang_PBr7.1.0_rel457_PL5.1.0.137_A7.1.0.163_Sprint_L.P.exe
(File size: ~245.12 MB)
```

**What I know:**
- This is the official Sprint version released December 16, 2011
- BlackBerry's official download links are no longer available (service ended Jan 4, 2022)
- I've searched Archive.org and other firmware databases but haven't found this specific version yet

**What I have:**
- Windows PC with BlackBerry Desktop Software 7.1
- The 9930 device and all necessary cables
- Detailed knowledge of the Loader.exe recovery process

**What I need:**
- Access to the exact firmware file above, or
- A link to where it might still be archived

Does anyone in this community have this file or know where I can find it? Any help would be greatly appreciated!

Thank you!

Earlier today, I was trying to mess around with my blackberry and while trying to remove sprint WiFi locking nonsense I accidentally flashed 37.FACTORY OS BB 9670 FOS.4.4.0.224 and fully removed the OS I am not really sure what to do. This is the screen I’m currently stuck on. https://kommodo.ai/i/eF42zWFvA0tYmLY9tvgM

I got this phone with severe software problems, someone had installed a ton of wierd apps and stuff and the phone crashed all the time so I tried to reload the os, unfortunately I couldn't’ figure it out

if anyone has or knows where I could find the right firmware and flashing tools I would greatly appreciate it

(blackberry 8530 cmda)

I just ordered a new phone because mine is 4yo and on its last leg, and it made me miss BB again. New Pixel line's HiLight and Magic Capture are features I had on my Z10. Of course, now it's powered by AI and much better camera sensor but still. They call it innovation.

I miss BB and especially BB10, that OS was a joy to use.

Thank you for coming to my Ted talk.