Database Info

Multiple Suggestions

First of all I want to applaud the integrity of the team working on OmniRom and for standing for software freedom. As the only GPL ROM on the phone, I believe it will reach a certain prominence once critical mass of functionality is achieved. I have some suggestions that I was hoping to get feedback for from the Devs here.
1- What is the possibility for devising an in-place upgrade system that works across future OS version upgrades for major changes in AOSP? (something akin the upgrade systems of current GNU/Linux systems)
2- Incorporating apps from the guardianproject (.info) a privacy and security oriented group that make secure messaging apps and TOR for Android. That will be our anwser to the so called secure chat of CM.
3- Cooperation with the largest FOSS software repo F-Droid and perhaps including it as a default app repo option for OmniRom.
4- Now this is a big one, but as a distro that prizes Software Freedom and the GPL above all else you are in a unique position to be a demo showcase for incorporating the major app frameworks being ported to Android like Qt and Gnome. Arranging with the devs from KDE and Gnome to make this a reality would be a major milestone for the FOSS movement's efforts to bring free software in an environment that is being increasingly closed off like what Google is doing with their absorption of features in proprietary apps and the treachery of the CM turncloaks.

Casual observer here. I don't think it's accurate to call it a GPL ROM given how many non-free drivers are required to get working WiFi and so on. OmniROM encourages GPL as a way of keeping the community honest but I don't think it's set in stone.
1. upgrades on Android don't happen in same way as GNu/Linux: it's always a fresh install. CM already does this, or you can use recovery mode.
2. good idea! more generally, system wide proxy settings which would allow all traffic to go through Tor. Tor is one part of remaining anonymous, the browser needs to be locked down for example. Guardian Project say that their companion browser, Or web, doesn't work on Android 4.4, and they might stop developing it. There are other Android techniques for anonymity e.g. xprivacy.
3. F-Droid builds and signs apps, it's hard to see room for cooperation. It will soon have ability to install apps silently if part of a ROM. They dropped their Android.mk; looks like time to bring it back, maybe with package name change option.
4. Qt was announced on day one at the BBQ!

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.

Ways to offer secondary verification of authenticity of an Android app

I know a lot of FOSS projects publish to f-droid and that has a great system of using PGP signatures to verify the APK files. What I'm curious about is how to verify apps deployed from the google playstore. Now obviously PlayStore verifies the apps submitted but on more than one occasion, phishing apps that share a similar name have remained up for days. Here are a few ways to verify the apps, that made sense to me.
Publish in your github repo, the full and proper playstore ID of your app
Publish in your github repo, the public key cert used to sign your app in playstore
Publish in your github repo, the full APK of your app via releases mechanism
#1 is the simplest but isn't really cryptographically hardended. Just makes sure the users type in the same URL you tell them to and hope there is no DNS hijack other exploits at play.
#2 is nice since it is trivial to extract the signing cert from an installed APK and the cert fingerprint can be verified against the one in the source repo. The signing cert never (or should never) changes so there is little maintenance this creates. And finally, most any JDK / ADK install will be able to verify an APK against a given cert.
#3 is probably the most complete since the user can checksum their installed APK against the one in the source repo, or simply install the one listed in the source repo. This does put extra work on the developer since they need to remember to publish a release via github whenever they push a release to Google.
I know it's paranoid, but there are some bitcoin Android apps that might warrant a heightened sense of paranoia.
Thoughts?

[GUIDE] GrapheneOS's Sandboxed Play services in your ROM

I loved to hear about GrapheneOS's Sandboxed Play services that allow running Google Play services as regular sandboxed apps. I don't own a google phone and am using LOS18.1. Unfortunately it seems LineageOS won't integrate the feature (see reddit).
That's why I looked for the corresponding commits in GrapheneOS, adopted them for LineageOS 18.1 (almost everything could be auto-merged) and used LOS4mG's docker CI/CD to build LOS18.1 with GrapheneOS's compatibility layer.
I don't want to release ROMs myself, but am just leaving the project here: https://github.com/sn-00-x/lineage-gmscompat
The docker image is on docker hub so you could build LOS18.1 by simply running the image sn00x/docker-lineage-cicd (set env vars and volumes as explained here). Or grab the patches here and apply yourself.

I'm very very sorry.. I have troubles building.. in fact I never got a build to succeed and didn't need much custom work anyway. But this one from your docker, I tried for two days, and there are always errors as I'm not experienced... You'd be VERY generous to build a 18.1 from your docker with the sandboxed gms patches for Pixel 4 (flame). That would be very kind of yours !! Thanks in advance

aibos said:
I'm very very sorry.. I have troubles building.. in fact I never got a build to succeed and didn't need much custom work anyway. But this one from your docker, I tried for two days, and there are always errors as I'm not experienced... You'd be VERY generous to build a 18.1 from your docker with the sandboxed gms patches for Pixel 4 (flame). That would be very kind of yours !! Thanks in advance
Click to expand...
Click to collapse
You can install GrapheneOS on Pixel 4, why would you want to use LOS 18.1?

To use VPN Tethering.

I'm pretty sure there are issues with some indexes with some of the following patch files, related to "strings.xml".
0005-gmscompat-Keep-GMS-services-alive-by-converting-to-f.patch
0015-gmscompat-Make-notification-channel-more-user-friend.patch
0016-gmscompat-Improve-foreground-service-notification-UX.patch
I get this error:
Code:
"error: invalid file path 'frameworks/base/core/res/res/values/strings.xml.orig'."
I dont know how to troubleshoot this. Any suggestion/fix?

Hello. Trying to do this same thing to lineage 19 for pixel 5....I can just merge this code into my repo and build?

Must you have signature spoofing for SPS?

It's sad when a talented dev disappears.. :'(

I am trying to take up where he left off. I will be attempting to patch this into Lineage 19 when I get off of work tonight.

That's why it's sad when a talented dev disappear...

Because then, nothing happens

Linking previous about GMS_Comapt by @sn00x here: https://forum.xda-developers.com/t/sandboxed-play-services.4341085/
I'd talks with GrapheneOS dev on twitter and reproducing them here for more insights:
> Can gms_compat be made available to use by everyone? I really want that to be implemented on LineageOS but that's not possible as they straight away rejected the request.
Is gms_compat device specific? If not, can it developed as a Magisk moduleso that installing that allows users to install GApps without actually flashing them in the first place?
Thank you.
> it's not device specific at all
> it could be easily ported elsewhere at least once the changes are squashed
> Can you elaborate a bit about these in case of the time permits? Squashing changes? You mean merging of commits?
> https://github.com/GrapheneOS/platform_libcore/commit/8d4383d15f9baed7665dbb459b29567e729b166d
> here's the simplified libcore changes, for example
> will be doing frameworks/base next
> Sandboxed Google Play compatibility layer (gmscompat):
Add support for loading DEX files from "/proc/self/fd" APK paths · GrapheneOS/[email protected]
Needed to load code from the Google Play services' Dynamite APK modules, which are available only by the file descriptor reference.
github.com
gmscompat: linker: Add support for opening zip files by fd paths · GrapheneOS/[email protected]
In some cases, it can be useful to load libraries from zip files that are only available by fd reference. For example, file descriptors of APKs containing native libraries may be sent via Binder IP...
github.com
add GmsCompat app · GrapheneOS/[email protected]
Make Build System (being phased out upstream). Contribute to GrapheneOS/platform_build development by creating an account on GitHub.
github.com
gmscompat: add compatibility layer for unprivileged GMS · GrapheneOS/[email protected]
Originally authored by Danny Lin <[email protected]> for inclusion in GrapheneOS. It has since been substantially extended and rewritten by Dmitry Muhomor <[email protected]> (pr...
github.com
gmscompat: support for Dynamite modules · GrapheneOS/[email protected]
Authored by Danny Lin <[email protected]> and Dmitry Muhomor <[email protected]> for inclusion in GrapheneOS. Commit history: Before June 2022: https://github.com/GrapheneOS/pl...
github.com
https://github.com/GrapheneOS/platform_packages_apps_GmsCompat
https://github.com/GrapheneOS/platf...mmit/550842c62ac693234b38fcaa0ed30692fae1873b
do not allow disabling GmsCompat app · GrapheneOS/[email protected]
Apps will break if it's disabled, handling this case in code increases complexity unnecessarily.
github.com
gmscompat: Add ConnectivityManager hook for baseline compatibility · GrapheneOS/[email protected]
This is part of GmsCompat's baseline compatibility for unprivileged Google Play Services. Change-Id: I3e87706f1f3b87c0af9d00f6ce92144469596f8c
github.com
gmscompat: restart GMS processes when permission gets granted · GrapheneOS/[email protected]
Contribute to GrapheneOS/platform_packages_modules_Permission development by creating an account on GitHub.
github.com
gmscompat: Add WifiManager hooks for baseline compatibility · GrapheneOS/[email protected]
This is part of GmsCompat's baseline compatibility for unprivileged Google Play Services. Change-Id: I2f56a47a6a732d6a73531c7f80aca69065a88c38
github.com
gmscompat: allow harmless COLUMN_NOTIFICATION_CLASS · GrapheneOS/[email protected]
Contribute to GrapheneOS/platform_packages_providers_DownloadProvider development by creating an account on GitHub.
github.com
Pixel eSIM management app integration:
https://github.com/GrapheneOS/platf...mmit/be60cb05013a1fb61675f21c705ddbef296f221a
https://github.com/GrapheneOS/platf...mmit/4c4a2f0df9c53eaf22b7add0305f0bfaac46695c
> this is the list of commits now
> after it has been squashed / cleaned up
> Thank you very much for more detailed info. I'll try my level best analyse and learn from these.
Based on this, I believe that, instead of making GMS_Compat just available for LineageOS, we can make it a module that can be flashed wither with Magisk or Recovery making it available for everyone as it is **NOT** device specific..

@sn00x This is awesome!
Has anyone tried this with lineage 19 ?
Also do OTA updates work?

Hi, I am trying to build a rom and wanted to include the graphene os sandboxed google play. I have never built a rom before, do I need to sync your repo into one of the folders where I have my rom files?
Not sure if this is relevant, but I am trying to build for AOSP for Sony Xperia

GMScompat is a big joke and just a fig leaf: Making Googleapps third party apps does not do much, except for giving user a false sense of security. As long as you install GMS framework and apps, they use intents to interact with AOSP, as well as system processes to do what they were designed to do - to spy on users.. The only way to remove such intents is to modify those application's sources, which is NOT possible, because they are closed source.

optimumpro said:
GMScompat is a big joke and just a fig leaf: Making Googleapps third party apps does not do much, except for giving user a false sense of security. As long as you install GMS framework and apps, they use intents to interact with AOSP, as well as system processes to do what they were designed to do - to spy on users.. The only way to remove such intents is to modify those application's sources, which is NOT possible, because they are closed source.
Click to expand...
Click to collapse
Why is this a joke? You are completely missing the point of what gmscompat is trying to achieve: to make using gms more private and secure. The best example is that with gmscompat google cannot access device identifiers auch as imei for example. Plus, as the name suggests, google cannot escape the app sandbox anymore. it doesn't have any special permissions anymore. speaking of permissions, you can revoke any permission of the google apps thanks to gmscompat.

as i am totally intersted into this subject using and following every rom that implement this feature ( sparkos voltageos yaap os etc)
recently the gmscompat fail to start and from my search thegraphene os team make it more difficult to launch needs frequent update of gmscompat.apk and config which is nesserory to make it work
from the bigining the grahene os team doesnt want to make it to other than thier os and pixel devices

drsanusi said:
as i am totally intersted into this subject using and following every rom that implement this feature ( sparkos voltageos yaap os etc)
recently the gmscompat fail to start and from my search thegraphene os team make it more difficult to launch needs frequent update of gmscompat.apk and config which is nesserory to make it work
from the bigining the grahene os team doesnt want to make it to other than thier os and pixel devices
Click to expand...
Click to collapse
When I was using Poco F3 I had SparkOS installed as a "warmup" for Pixel and GrapheneOS. The ROM is a good replacement for anyone who wants this experience of sandboxed play services, but it lacks a lot of stuff from the GrapheneOS. And also it lacks polished default apps. Thankfully you can disable them and install your own though...

hellcat50 said:
Why is this a joke? You are completely missing the point of what gmscompat is trying to achieve: to make using gms more private and secure. The best example is that with gmscompat google cannot access device identifiers auch as imei for example. Plus, as the name suggests, google cannot escape the app sandbox anymore. it doesn't have any special permissions anymore. speaking of permissions, you can revoke any permission of the google apps thanks to gmscompat.
Click to expand...
Click to collapse
Permissions and intents are contained in app's Manifest, as well as in app's code. Google certificates, which recognize Gapps as native are in AOSP code. So, regardless of where the app is installed, it can go around 'compatibility' layers and do their thing, i.e. collect user data.
The only proper way to get rid of higher level permissions is to modify Gapps' code, which is impossible.

optimumpro said:
Permissions and intents are contained in app's Manifest, as well as in app's code. Google certificates, which recognize Gapps as native are in AOSP code. So, regardless of where the app is installed, it can go around 'compatibility' layers and do their thing, i.e. collect user data.
The only proper way to get rid of higher level permissions is to modify Gapps' code, which is impossible.
Click to expand...
Click to collapse
Sorry but i call bs on that. Do you have any sources to claim that?

[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