Database Info

Project Articul8

Hi everyone,
I am a privacy guy and I just started a new project called Articul8 with the aim of building a new lightweight Android ROM that is both secure and has privacy built in to the core. I recently wrote about the project on LinkedIn (but I am not allowed to post links yet on this forum) and there has been quite a lot of interest from the privacy arena.
The plan is to develop apps which host all their data off the device on private remote servers - but more than that, the project will seek to develop popular apps which are hosted serverside, to prevent tracking and profiling.
I have already written a serverside Twitter app which does exactly this (I just need to write the client interface for Android) some time ago as explained in the linked article and I have also recently written a contacts app for Android using Ionic Framework. The purpose of this post is to try and gather some feedback and support in developing the project further. I expect this project to be a long term project which grows significantly over time and I am already planning server hosted apps for LinkedIn, Facebook, G+ as well as looking into SIPjs to create a VOIP client as well. What I haven't managed to plan out yet is how to build the ROM with most of the native apps stripped out and replaced with these new remote services.
I would like to make the entire project open source and publicly available - none of the apps will include any advertising or third party APIs - the whole point of the project is to firewall the device from all third parties as well as firewalling all the data from the device (in the event the device is compromised). All services should require passwords to open to prevent data being compromised should a device be stolen or taken from the owner. In essence the hardware will become dumb.
All feedback appreciated and if you are interested in contributing, please get in touch.

What is git-hub?

What is github please tell me in easy language i already Google it but its hard to understand a new comer like .

a famous website

It's a website.
The site provides social networking-like functions such as feeds, followers, wikis (using wiki software called gollum) and a social network graph to display how developers work on their versions ("forks") of a repository and which fork (and branch within that fork) is newest.
A user must create an account in order to contribute content to the site, but public repositories can be browsed and downloaded by anyone. With a registered user account, users are able to discuss, manage, create repositories, submit contributions to others' repositories, and review changes to code.

NativeBase: The Missing Piece of React Native​

React Native is something I call a breakthrough in mobile app development; bringing the best of web development, making native app development how it’s supposed to be i.e. completely native.
However, React Native has too low level APIs and small components where we end up rewriting many basic components ourselves for each project, which is where NativeBase fills in.
NativeBase is an open source framework that lets you write high-quality React Native apps with ease by providing generic re-usable components (header, footer, buttons, lists, cards etc.) and in this tutorial, we’re going to do a demo of the same. The source code is available in this Github repo.
Let’s build a “Github Repository Finder App” using React Native & NativeBase

Thread closed.
1. This forum is for apps and games, not news posts.
2. Please do not copy and paste content from articles into XDA threads: https://scotch.io/tutorials/nativebase-the-missing-piece-of-react-native​
The Flash
Forum Moderator

[Dev][LIB][MULTI-PLATFORM] JDroidLibv2! Java Android Communications Platform

Welcome!​
Introduction
After three years of inactivity, of me (the developer) simply enjoying life and riding bikes, I'm proud to announce that JDroidLib is being resurrected!
Originally inspired by AndroidLib by @regaw_leinad, JDroidLib is a Java class library aimed to ease the development of Java applications designed to communicate with Android-powered devices.
The end goal was to make the library as easy and efficient to use as possible, and while the original library was easy to use, some fairly bad design choices were made on my part to make that happen.
After a turn of recent events, I've found myself to have somewhat more free time on my hands and decided to re-visit the project.
After looking through the (well-documented) source code of the original library, I decided that in order for an update to make sense, I'd have to completely re-write the library.
After a couple of hours of development and building the base, I had come up with a structure and code design that I was happy with and continued from there.
A few days after development began, I created a new repository on GitHub and thus, JDroidLibv2 was born!
The original version of JDroidLib was featured multiple times on the XDA platform and on other networks, as well.
Ok, great! But why should we care?
There are two very simple answers to this question!
If you're not a Java developer, or you have no interest in building Java applications that communicate with Android devices, such as flashing, rooting, or diagnostic tools, then you absolutely don't have to care! That's the beauty of it.
If, however, you are either of those, then you should give JDroidLib a closer look!
JDroidLib is designed to be efficient and easy to use.
Getting the library integrated in to your project is as easy as clicking a couple of times and calling it a day!
Now, I hear you ask: What's the upside to using your library?
Also a question that is very easy to answer.
Using JDroidLib, your application has next to no boilerplate code, meaning the footprint of your actual application is minimal and thanks to fast initialisation routines, your application will suffer minimal latency.
Thanks to both synchronous and asynchronous operations, your UI application will feel responsive to your users and your application less bloated.
JDroidLib includes shortcuts to commands that are often used and helper classes that cleanly sort and store data, so your application doesn't have to!
What design choices have you made?
JDroidLib is designed to be as easy to use as possible, while being efficient at what it does.
To implement these ideas and this design, JDroidLib uses a variety of designs that all work together to create an efficient library:
Factories to easily define the things you need
Singletons to prevent resource hogging and minimise the risks of memory leaks
Both synchronous and asynchronous methods so you can choose what's best for you!
Strongly typed
Provides features that otherwise prove useful in applications, such as tuples
Genericism
Ok, that's cool and all, but when will it be ready?
As it is, JDroidLibv2 is currently in an early beta. Its features are not yet fully implemented and a lot of things are missing.
All I can say for now, is it'll be ready when it's ready.
It could take weeks, or even months - depending on how much time I have.
I'm hoping the repository will be updated regularly!
End notes
If you're interested in the project, the link to the source code repository can be found below.
In later posts I will add current features, todos, and more relevant information!
Happy coding!
XDA:DevDB Information
JDroidLibv2, Tool/Utility for all devices (see above for details)
Contributors
Beatsleigher, Beatsleigher
Source Code: https://github.com/Beatsleigher/JDroidLibv2
Version Information
Status: Beta
Created 2017-10-06
Last Updated 2017-10-07

Reserved
Current Features
Automatic initialisation
Installation/downloading of platform-specific platform-tools packages
Start/stop ADB server
Get list of devices
Execute custom commands (sync and async!)
Connect to and disconnect from devices via TCP/IP
Manage device filesystems
Get root and busybox information
Get device battery information
Current Todos
Complete Device class
Build file manager
Get battery information
Get SU/busybox information
Get CPU/RAM information
Build buildprop manager
Add reboot methods
Finish JavaDocing everything
Add (complete) wiki to GitHub
Add homepage to GitHub (I've no more website)
Add feature requests from potential users?
Continue updating
Elements that are stroked are completed/ideas that have been scrapped.

Reserved
Useful Links
Source Code
https://github.com/Beatsleigher/JDroidLibv2
Issue Tracker
https://github.com/Beatsleigher/JDroidLibv2/issues
Wiki and Guides
https://github.com/Beatsleigher/JDroidLibv2/wiki
Release Downloads
https://github.com/Beatsleigher/JDroidLibv2/releases
Todo: Upload to Maven Central
Social Media (Updates)
Google+
Twitter (not as regular, though)

JDroidLibv2 has been released in an open beta!
https://github.com/Beatsleigher/JDroidLibv2/releases

[APP][4.4+][v.9.33.31] Telegraher, a Telegram fork with blackjack and hookers

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi folks it has been 9+ months that i consistently developing my telegram fork, "Telegraher with blackjack and hookers!"
The main idea is that vanilla TG client pretty annoying:
remote deletions
impossible to screenshot in greenchats
content restrictions
have too much privileges & tracking
So slowly i started to mod that client to make my own. I use Telegram official source as a base. I don't use Tg-FOSS cause author is pretty slow in updates. Also i don't use popular "cat-forks" cause i have "real life" and i hate x2 screen size tap menus.
I started from version 8.3.0 and 1st release was made for 8.3.1. While i'm writing this post we're on 8.8.5, so our internal version is look actual stuff section.
We're not in Izzy's repo (cause fork >30Mb), we're not on fdroid either because I don't want to depend on their CI/CD and their repo. We're on github and apps made by CI/CD and posted by github too. Then releases are picked up by the bot and send to our TG chat, from where i move them into the channel. Also i send a copy to Matrix (which i made as a backup since Telegram send us a strike in march'22, to loveletter to "Telegraher team"). And i move them also on my CDN with TOR access enabled, so folks can download files w/o JS and hide their IP as they want.
Why i did it for telegram and not for Matrix or XMPP, it's because i have lot of contacts on telegram. When my friends will leave TG i will leave it too. Also i love to piss-off telegram fanboys.
Main features are:
we're in bundle, 4 architectures and we work from android 4.4+ (early versions 4.1+)
no remote deletions at all (green chats & timed medias also)
no gapps, the app is FOSS (notifications are same like in Tg-FOSS, via notification badge cause since A8 OS can kill the app)
we have shadowban to shadowban people or channels you don't want to see
no content restrictions, also in greenchats (save all you want, but don't forward, 'cause forward if fully API function)
emulator detection is disabled
we have device spoofing (actually TG doesn't change devices pretty fast for active sessions, but you can change it globally and add an account)
the phone you type is "always active" and you have that simcard
we have session manager & unlimited multiacc (while you have memory, we're tested 80 accs easily).
wal is disabled for db, so no journal grow
we're on vanilla API keys & keep vanilla behaviour to avoid any client bans (we keep low profile, sending vanilla keys, package, vendor, codeversion & fingerprint also)
..and many other features what i added or picked somewhere (or community is asked me).
Application links:
Github repo, CI/CD releases (all is made here, the origin)
Gitlab repo, just synced from Github.
CDN releases and cloned repo also (manual copy here, front is Cloudflare, backed by AWS, if you care about your IP, use VPN or TOR)
Telegram resources: channel, chat, FAQ EN/RU & FAQ Persian.
Matrix resource: the space, chat & apks (after last incident with free oracle cloud we're lost local files, but i launched anotherone with same keys, server is in swiss)
"Press":
Techtracker.in (08/2022)
FAQ:
Can i be banned?
Officially - no. Telegram have 2 TOS: one for the users, another is for the devs. User TOS is the TOS you need to follow when you use the app. User TOS forbid `spam, scam, violence & porn`. This is an open-source fork which don't have hidden features to `spam, scam, violence & porn`. Dev TOS is the TOS which devs must follow when they develop the apps and use generated API keys. Telegraher as an app break the DEV TOS only & Telegraher use vanilla API keys. User TOS it's up to you!
Actual stuff:
Actual release is 9.33.31
.
.
if you face the issue "update your app it's too old" go here
About me:
I'm not an Android dev, but i code on Java, thats why i do what i do. I'm a russian and i live already 10y in France. My life & work c'est ici.
P.S. Telegraher there are no "p", it's not a "Telegrapher" and have nothing to do with.

Thank you for the fork !

Rush-er said:
Thank you for the fork !
Click to expand...
Click to collapse
my pleasure!

nikitasius said:
Hi folks it has been 9+ months that i consistently developing my telegram fork, "Telegraher with blackjack and hookers!"
The main idea is that vanilla TG client pretty annoying:
remote deletions
impossible to screenshot in greenchats
content restrictions
have too much privileges & tracking
So slowly i started to mod that client to make my own. I use Telegram official source as a base. I don't use Tg-FOSS cause author is pretty slow in updates. Also i don't use popular "cat-forks" cause i have "real life" and i hate x2 screen size tap menus.
I started from version 8.3.0 and 1st release was made for 8.3.1. While i'm writing this post we're on 8.8.5, so our internal version is 8.85.47 .
We're not in Izzy's repo (cause fork >30Mb), we're not on fdroid either because I don't want to depend on their CI/CD and their repo. We're on github and apps made by CI/CD and posted by github too. Then releases are picked up by the bot and send to our TG chat, from where i move them into the channel. Also i send a copy to Matrix (which i made as a backup since Telegram send us a strike in march'22, to loveletter to "Telegraher team"). And i move them also on my CDN with TOR access enabled, so folks can download files w/o JS and hide their IP as they want.
Why i did it for telegram and not for Matrix or XMPP, it's because i have lot of contacts on telegram. When my friends will leave TG i will leave it too. Also i love to piss-off telegram fanboys.
Main features are:
we're in bundle, 4 architectures and we work from android 4.1+
no remote deletions at all (green chats & timed medias also)
no gapps, the app is FOSS (notifications are same like in Tg-FOSS, via notification badge cause since A8 OS can kill the app)
we have shadowban to shadowban people or channels you don't want to see
no content restrictions, also in greenchats (save all you want, but don't forward, 'cause forward if fully API function)
emulator detection is disabled
we have device spoofing (actually TG doesn't change devices pretty fast for active sessions, but you can change it globally and add an account)
the phone you type is "always active" and you have that simcard
we have session manager & unlimited multiacc (while you have memory, we're tested 80 accs easily).
wal is disabled for db, so no journal grow
we're on vanilla API keys & keep vanilla behaviour to avoid any client bans (we keep low profile)
..and many other features what i added or picked somewhere (or community is asked me).
Application links:
Github repo, CI/CD releases (all is made here, the origin)
Gitlab repo, just synced from Github.
CDN releases and cloned repo also (manual copy here, front is Cloudflare, backed by AWS, if you care about your IP, use VPN or TOR)
Telegram resources: channel, chat, FAQ EN/RU & FAQ Persian.
Matrix resource: the space, chat & apks (after last incident with free oracle cloud we're lost local files, but i launched anotherone with same keys, server is in swiss)
"Press":
Techtracker.in (08/2022)
About me:
I'm not an Android dev, but i code on Java, thats why i do what i do. I'm a russian and i live already 10y in France. My life & work c'est ici.
P.S. Telegraher there are no "p", it's not a "Telegrapher" and have nothing to do with.
Click to expand...
Click to collapse
Thanks sir keep up the good work

AmirulAndalib said:
Thanks sir keep up the good work
Click to expand...
Click to collapse
thaaaanks

nikitasius said:
Hi folks it has been 9+ months that i consistently developing my telegram fork, "Telegraher with blackjack and hookers!"
The main idea is that vanilla TG client pretty annoying:
remote deletions
impossible to screenshot in greenchats
content restrictions
have too much privileges & tracking
So slowly i started to mod that client to make my own. I use Telegram official source as a base. I don't use Tg-FOSS cause author is pretty slow in updates. Also i don't use popular "cat-forks" cause i have "real life" and i hate x2 screen size tap menus.
I started from version 8.3.0 and 1st release was made for 8.3.1. While i'm writing this post we're on 8.8.5, so our internal version is 8.85.47 .
We're not in Izzy's repo (cause fork >30Mb), we're not on fdroid either because I don't want to depend on their CI/CD and their repo. We're on github and apps made by CI/CD and posted by github too. Then releases are picked up by the bot and send to our TG chat, from where i move them into the channel. Also i send a copy to Matrix (which i made as a backup since Telegram send us a strike in march'22, to loveletter to "Telegraher team"). And i move them also on my CDN with TOR access enabled, so folks can download files w/o JS and hide their IP as they want.
Why i did it for telegram and not for Matrix or XMPP, it's because i have lot of contacts on telegram. When my friends will leave TG i will leave it too. Also i love to piss-off telegram fanboys.
Main features are:
we're in bundle, 4 architectures and we work from android 4.1+
no remote deletions at all (green chats & timed medias also)
no gapps, the app is FOSS (notifications are same like in Tg-FOSS, via notification badge cause since A8 OS can kill the app)
we have shadowban to shadowban people or channels you don't want to see
no content restrictions, also in greenchats (save all you want, but don't forward, 'cause forward if fully API function)
emulator detection is disabled
we have device spoofing (actually TG doesn't change devices pretty fast for active sessions, but you can change it globally and add an account)
the phone you type is "always active" and you have that simcard
we have session manager & unlimited multiacc (while you have memory, we're tested 80 accs easily).
wal is disabled for db, so no journal grow
we're on vanilla API keys & keep vanilla behaviour to avoid any client bans (we keep low profile, sending vanilla keys, package, vendor, codeversion & fingerprint also)
..and many other features what i added or picked somewhere (or community is asked me).
Application links:
Github repo, CI/CD releases (all is made here, the origin)
Gitlab repo, just synced from Github.
CDN releases and cloned repo also (manual copy here, front is Cloudflare, backed by AWS, if you care about your IP, use VPN or TOR)
Telegram resources: channel, chat, FAQ EN/RU & FAQ Persian.
Matrix resource: the space, chat & apks (after last incident with free oracle cloud we're lost local files, but i launched anotherone with same keys, server is in swiss)
"Press":
Techtracker.in (08/2022)
FAQ:
Can i be banned?
Officially - no. Telegram have 2 TOS: one for the users, another is for the devs. User TOS is the TOS you need to follow when you use the app. User TOS forbid `spam, scam, violence & porn`. This is an open-source fork which don't have hidden features to `spam, scam, violence & porn`. Dev TOS is the TOS which devs must follow when they develop the apps and use generated API keys. Telegraher as an app break the DEV TOS only & Telegraher use vanilla API keys. User TOS it's up to you!
About me:
I'm not an Android dev, but i code on Java, thats why i do what i do. I'm a russian and i live already 10y in France. My life & work c'est ici.
P.S. Telegraher there are no "p", it's not a "Telegrapher" and have nothing to do with.
Click to expand...
Click to collapse
Niki u are everywhere.

Niki u are everywhere.

tyler19820201 said:
Niki you are everywhere.
Click to expand...
Click to collapse
Salut Tyler
yep, i was surprised that i did not had account here. I was visiting XDA for my nexus4 in 2013, but probably w/o making an account.
Also in more places i am - harder for TG to ban the project

nikitasius said:
Salut Tyler
yep, i was surprised that i did not had account here. I was visiting XDA for my nexus4 in 2013, but probably w/o making an account.
Also in more places i am - harder for TG to ban the project
Click to expand...
Click to collapse
Welcome on the board.

Brilliant , congrats for posting on xda.

Walden0 said:
Brilliant , congrats for posting on xda.
Click to expand...
Click to collapse
thanks !

nikitasius said:
Hi folks it has been 9+ months that i consistently developing my telegram fork, "Telegraher with blackjack and hookers!"
The main idea is that vanilla TG client pretty annoying:
remote deletions
impossible to screenshot in greenchats
content restrictions
have too much privileges & tracking
So slowly i started to mod that client to make my own. I use Telegram official source as a base. I don't use Tg-FOSS cause author is pretty slow in updates. Also i don't use popular "cat-forks" cause i have "real life" and i hate x2 screen size tap menus.
I started from version 8.3.0 and 1st release was made for 8.3.1. While i'm writing this post we're on 8.8.5, so our internal version is 8.85.47 .
We're not in Izzy's repo (cause fork >30Mb), we're not on fdroid either because I don't want to depend on their CI/CD and their repo. We're on github and apps made by CI/CD and posted by github too. Then releases are picked up by the bot and send to our TG chat, from where i move them into the channel. Also i send a copy to Matrix (which i made as a backup since Telegram send us a strike in march'22, to loveletter to "Telegraher team"). And i move them also on my CDN with TOR access enabled, so folks can download files w/o JS and hide their IP as they want.
Why i did it for telegram and not for Matrix or XMPP, it's because i have lot of contacts on telegram. When my friends will leave TG i will leave it too. Also i love to piss-off telegram fanboys.
Main features are:
we're in bundle, 4 architectures and we work from android 4.1+
no remote deletions at all (green chats & timed medias also)
no gapps, the app is FOSS (notifications are same like in Tg-FOSS, via notification badge cause since A8 OS can kill the app)
we have shadowban to shadowban people or channels you don't want to see
no content restrictions, also in greenchats (save all you want, but don't forward, 'cause forward if fully API function)
emulator detection is disabled
we have device spoofing (actually TG doesn't change devices pretty fast for active sessions, but you can change it globally and add an account)
the phone you type is "always active" and you have that simcard
we have session manager & unlimited multiacc (while you have memory, we're tested 80 accs easily).
wal is disabled for db, so no journal grow
we're on vanilla API keys & keep vanilla behaviour to avoid any client bans (we keep low profile, sending vanilla keys, package, vendor, codeversion & fingerprint also)
..and many other features what i added or picked somewhere (or community is asked me).
Application links:
Github repo, CI/CD releases (all is made here, the origin)
Gitlab repo, just synced from Github.
CDN releases and cloned repo also (manual copy here, front is Cloudflare, backed by AWS, if you care about your IP, use VPN or TOR)
Telegram resources: channel, chat, FAQ EN/RU & FAQ Persian.
Matrix resource: the space, chat & apks (after last incident with free oracle cloud we're lost local files, but i launched anotherone with same keys, server is in swiss)
"Press":
Techtracker.in (08/2022)
FAQ:
Can i be banned?
Officially - no. Telegram have 2 TOS: one for the users, another is for the devs. User TOS is the TOS you need to follow when you use the app. User TOS forbid `spam, scam, violence & porn`. This is an open-source fork which don't have hidden features to `spam, scam, violence & porn`. Dev TOS is the TOS which devs must follow when they develop the apps and use generated API keys. Telegraher as an app break the DEV TOS only & Telegraher use vanilla API keys. User TOS it's up to you!
About me:
I'm not an Android dev, but i code on Java, thats why i do what i do. I'm a russian and i live already 10y in France. My life & work c'est ici.
P.S. Telegraher there are no "p", it's not a "Telegrapher" and have nothing to do with.
Click to expand...
Click to collapse
Welcome to XDA and thanks for sharing!

orb3000 said:
Welcome to XDA and thanks for sharing!
Click to expand...
Click to collapse
Thaaanks!

Some folks facing the issue "update your app" on actual release.
If you read it and face it also, please share information about via reply to this message:
- phone model
- ROM
- how many telegram clients are running on that device already on same time while you're adding the acc to the graher.

nikitasius said:
Some folks facing the issue "update your app" on actual release.
If you read it and face it also, please share information about via reply to this message:
- phone model
- ROM
- how many telegram clients are running on that device already on same time while you're adding the acc to the graher.
Click to expand...
Click to collapse
Here is a video i did on old Nexus 4 running LOS with Android8 and no gapps.
I also have no issues on fresh install on Mi Mix 2 running LOS with Android11 also w/o gapps.
P.S. video made on linux using Kazaam, play it via VLC.

Interessing moments folks
This is github update 9.0.0 -> 9.0.1 https://github.com/DrKLO/Telegram/commit/11edd5ee0d924b8db0bd9b2460c7abdf664ad716
There are the part: code version changed from 2799 to 2800 and version also 9.0.0 to 9.0.1 (screenshot from github).
While on market 9.0.0 version had code 2800 and not a 2799 (screenshot from jadx).
Why could build 9.0.1 with vanilla keys on github with codeversion 2800 and 9.0.0 with same vanilla keys and codeversion on gplay?
I see only 2 reasons:
dev is ****edup the build on google
easypeasy way to detect ALL FORKS on vanilla keys, cause they will have codeversion 2800 for appversion 9.0.1
Just filter requests and ban all "bad forks":
vanilla keys
code 2800
app 9.0.1 and NOT 9.0.0

Release 8.85.48
ㅤbit changed login part
ㅤ.gitignore fix
ㅤyou can enable WAL mode for DB (using debug menu in the client)
this is the last update fro 8.8.x. All next will for beta 9.0.x now.
Github, the origin, CI/CD
CDN, copied from github manually
P.S. IDK if i should to share an APK here, it's about 64Mb.

1-st of all i wanna thank the great community, cause together we're debugged the issue #update_app_to_login .
The facts:
- users on chinese ROMs like MIUI (xiaomi) or EMUI (huawei, most of cases)
- users on chinese phones but w/o chinese ROM does not face the issue (like me on Xiaomi Mi Mix 2 under LOS w/ android 11).
- users face this issue NOT only with graher, but also with with official bundles https://www.apkmirror.com/apk/telegram-fz-llc/telegram/telegram-8-8-5-release/ & https://www.apkmirror.com/apk/telegram-fz-llc/telegram/telegram-8-8-6-release/ (we're on "8.8.6" codeversion).
From my side i re-debugged login flow and made it maximum correct and legit as it looks.
But folks on huawei still faced the issue.
So, we're simply did this: we're changed the device.
Users on the Huawei swapped their devices via device spoofing to `Xiaomi`/`MI MIX 2`/`30` (30 for the OS).
And magically it worked fine.
So, if you just installed graher 8.85.x and you have this issue:
- find a NON-Huawei device, like this http://deviceinfohw.ru/devices/item.php?item=565947 (search on this website)
- clean the app using Kaboom or any APP MANAGER or simply reinstall it (cause it's reshly installed you risk nothing)
- go to app properties (android system menu)
- go to storage manage and you will see "cache cleaning UI" from the app
- go to graher menu at the bottom
- change BRAND, MODEL & OS
- kill the app (red button)
- REPEAT it till "go to graher menu" to check that the device is spoofed well
- START the APP and ADD your account!
If you did it all and you still face the error, please write on forum or in chat we'll debug it. Or just wait new release on 9.0.x telegram.
I pretty sure, as it work with a spoofing that it's server side issues.

Release 8.85.49 bundle
ㅤapp use data from BuildVars everywhere
ㅤlogin flow looks now pretty legit for me
this is the really last update fro 8.8.x. All next will for beta 9.0.x from now.
Github, the origin, CI/CD
CDN, copied from github manually
attached to this post also

Today i got multiple messages that ****ty avast mark us as `Evo-Gen`. Well, as you see 23/09 was nothing, today - we're the "virus".
For Avast team i have 2 recomendations:
check our source code and CI/CD on github
mark as `Evo-Gen` official Telegram client also if you ignore 1.
Spoiler: Screenshots