643 karma · joined February 21, 2019
This is probably because /e/OS IS Android. It also contains microG, an open source framework that talks to Google Play Services.
Fun fact, their Android code [0] (haven't seen iOS) is unmaintainable mess and on the surface just looks like a complete disaster. I find it baffling how Telegram Android not only hasn't fallen to bits requiring a full rewrite, but has continued to deliver brilliant UX and features.
0. https://raw.githubusercontent.com/DrKLO/Telegram/master/TMes...
[0]: https://www.digitalhealth.net/2020/09/babylon-to-face-no-fur...
> Babylon Health will face “no further action” for a data breach that allowed a user of its GP app to access video recordings of other patients’ consultations.
This doesn't happen on Firefox and this [0] is probably why. I imagine this could be used for fingerprinting, am I missing something?
Anyway, back to driving trains.
[0]: https://hacks.mozilla.org/2020/07/securing-gamepad-api/
I'd like to hear of alternatives that apply the same e2e encryption model.
If you then navigate to the privacy policy on that site, it contains stuff like:
"For example, we may use remarketing with Google Analytics or other remarketing tools to advertise online. This enables third-party vendors, including Google, to show our ads on sites across the Internet...."
This really rings true to me. I almost cringe when I have to explain how to do some of the most basic things to non android developers.
Aside from the dozens of libraries you need to include, and need to know where to find and what version is compatible with what, the tooling itself is an insurmountable mess for new developers. It's also not getting any simpler.
I was fortunate enough to have developer mode & USB debugging enabled, which allowed me to install some code to clear the wallpaper using the WallpaperManager [0].
Sadly it wasn't as simple as pushing the code to the phone and running a command to execute it. When the device boots, it would crash _almost_ instantly and reboot into recovery mode after attempting to show the wallpaper a few times. This meant I couldn't put my passcode in, which meant Android refused to run the application I made to clear the wallpaper.
The ADB (Android Debug Bridge) tool [1] lets you replicate user input for the connected device, so you can basically swipe the screen / enter keys from the command line. I was able to use ADB to swipe up on the lock screen and enter my passcode. This was a start but wasn't enough, as the crash was happening before the wallpaper deleting app could be started.
I figured the unlock process was taking too much time, and found out after Android 8 (Oreo) you can actually use ADB to change or remove your passcode [2], provided you know your existing passcode. After I removed my passcode I was able to reboot the device, and run a single ADB command to swipe up on the screen and delete that cursed wallpaper.
And no it wasn't worth it, but I enjoyed the challenge
[0]. https://developer.android.com/reference/android/app/Wallpape...