Earlier quoted context omitted.
To clarify, its kinetic scrolling that is broken.
Interesting. Because with Firefox 59 for Android, both kinetic and inertial scrolling work as expected (just tested). Odd that it does not work for iOS Safari.
De-Googling my phone
61–70 of 192 posts
Re: De-Googling my phone
#62Your increased trust in these stores is motivated by .... what governance and audit structure? yes, its a devils-advocate position. You might (for instance) have high trust because you know them from hacker traeff you've been on, f2f. I can't have this a-priori knowledge. From here, this looks no better than "trust google" and in some dimensions looks significantly worse. Of course for the primary goal of "distrust g…
Something I haven't yet understood -- why hasn't a ~Debian of Android-compatible phones emerged? Are we lacking a UI? Kernel? Apps? Interest? Interface with existing closed-source apps? Is stock Android too good?
A lot of hardware support on these devices is proprietary in some way. Mostly proprietary firmware, some proprietary kernel drivers and some proprietary userland daemons or drivers.
Most hardware doesn't have support in the mainline Linux kernel, u-boot, mesa etc.
These are improving slowly as people do reverse engineering of proprietary components and the FLOSS enthusiast community does the work of getting hardware support mainlined. Some vendors also do mainlining work too and some employ folks to work on FLOSS drivers (Broadcom RPi VC4/VC5 for example).
Some related links are gathered on this page:
Re: De-Googling my phone
#63Earlier quoted context omitted.
What browser were you using. Scrolling works perfectly in Firefox 57 on Linux.
iOS Safari
Re: De-Googling my phone
#64I used k9mail for awhile until I realized it had sent every temporary draft of an email as I revised something and changed between apps. Was super embarrassing. Hard to trust it now even though the ui seemed great.
Re: De-Googling my phone
#65Re: De-Googling my phone
#66This is what I am using: https://lineage.microg.org/ (get rid of google play (and save 1/3 of battery)) apps have a dependancies to google framework and just not having it breaks lots of stuff (this is google true vendor lock-in). Microg is opensource reimplementation of it, but it needs patches into android to fake its file signatures. And lineage microg takes care about it)
First thing, get rid of your gmail/android account, register new account with 3rd party email provider. If you are buying phone, check xda-developers which has most support from ROM builders as you don't want, for instance, Samsung ROM. Only than go for hw specifications. Root phone (don't be afraid, it is nothing special, companies are scaremongering here), flash recovery TWRP (imagine it as "bootloader" for android), flash lineage microg.
From here, you start playing with OS.
- Replace dns server (root required) 8.8.8.8 with other (I use my own but there are plenty privacy oriented like ccc.de)
- Install yalp store (replaces play store, buy things using browser, if developer drm doesnt support verifying that you have bought its app, break it using lucky patcher or demand money back)
- Install xposed framework, install netguard, install xprivacylua (one of rare developers I trust for this, due to his privacy work), pay him donations to get pro versions (I have my own versions of those two built and a tad modified)
- use netguard logging to block all the fishy urls that system is calling (gps service, block complete network access,...)
- take special care about firefox, block all privacy details using xprivacylua, install webapi manager add-in, learn to use it.
- You have set up base os now start using it and block everything that is trying to be contacted using microg. Lineage is by no means clean but you can silence it. Dont trust system apps, broadcom drivers are, for instance, contacting their servers. Dont start installing apps until you have done it, later you will get huge noise from apps. Take a day or two and just use phone normal features blocking everything that seems faul (google ntp servers,...)
- For those who havent noticed it yet (or reversed a few of apps), most of android applications are demanding crazy lot of permissions. The reason is that in they have ~1/3 of developer code any 2/3 of spying code, from ad providers to trackinb and analytics and simply code that "just" needs to access your contacts =/. So... for every application you install, start it with everything blocked (netguard + xprivacylua) and work your way trough allowances. Don't give any app allow for internet if it doesn't need it, fake all the details to app that doesnt need them (South Pole is a nice place to be for gps coordinates)...
To really unhook yourself from google, you will need a server, I came to the point where all google domains are blocked (I mean ALL, not just google.*), all my comunication from all my computers/devices is passing server (i have two ways of doing it, either vpn or ssh tunnel) where communication is cleaned, http (+https mitm) over squid with huge blocklist, caching cdns forever,... and having squid in separate routing table (ok, its freebsd fib but close enough) with openvpn client, so also my ip is gone. I am completely self hosted (own "cloud" for webdav,webcal, files; mailserver; searx;...) and...
.. I am not missing anything that google has to offer, I am using android apps, but without google.
I would really recomend doing it, if you aren't familiar with networks, OS,... it will take a year, two, five, but you will learn a lot.
I have probably forgot about lots of details but please ask it, if you are interested.
Just for a taste, my google data export is 28kb (bought apps,...) after few years. What about yours? :)
Some links you might use:
Re: De-Googling my phone
#67Re: De-Googling my phone
#68Your increased trust in these stores is motivated by .... what governance and audit structure? yes, its a devils-advocate position. You might (for instance) have high trust because you know them from hacker traeff you've been on, f2f. I can't have this a-priori knowledge. From here, this looks no better than "trust google" and in some dimensions looks significantly worse. Of course for the primary goal of "distrust g…
Re: De-Googling my phone
#69Your increased trust in these stores is motivated by .... what governance and audit structure? yes, its a devils-advocate position. You might (for instance) have high trust because you know them from hacker traeff you've been on, f2f. I can't have this a-priori knowledge. From here, this looks no better than "trust google" and in some dimensions looks significantly worse. Of course for the primary goal of "distrust g…
Something I haven't yet understood -- why hasn't a ~Debian of Android-compatible phones emerged? Are we lacking a UI? Kernel? Apps? Interest? Interface with existing closed-source apps? Is stock Android too good?
really. we are back to being limited to one OS because of drivers.
this is also the reason lineageOS and other android roms can't just keep updating older phones to new releases. they need the oem to upgrade so they can extract drivers from the binaries.
Re: De-Googling my phone
#70Ubuntu phone is not dead, it's now developed by ubports http://ubuntu-touch.io/
It is dead. Someone forked it. I'm sorry but I can't trust some random team with almost zero funding to write my everyday os. Ubuntu phone died when Canonical dropped it. Same for Mozilla. It's a shame and kind of bizarre that Google can go on without any competition, but without the hardware manufacturers cooperating this isn't working out. We need open hardware for this to work.
I'm out of the loop, what happened with Mozilla?