Welcome back to this series on fixing a broken screen on a google pixel phone, and then installing and configuring GrapheneOS on it.
My main goal, is to create a more privacy oriented phone, that at the same time only has the bare minimum of apps I need in order to get through the day, thereby reducing my screen time. A few years ago I bought a dumb phone, but tbh. it lacked too much of what I need in order to be a feasable replacement. Just the simple fact that no proper camera is available is more or less a no-go when you have 3 kids.
Thus I hope to create something like a halfway-house; A phone that has all I need, but does not invite me to use it more than needed.
Installing GrapheneOS #
Decpite my initial expectations, the actual installation part of GrapheneOS on the phone was one of the easier parts of the whole process.
Two installers are available; a traditional command line installer and a web-usb based installer.
I chose the latter, so all I had to do was to plug the phone into the usb of my computer and head over to GrapheneOS web installer and follow the steps there.
No rocket science involved.
Getting up and Running with a Clean OS #
This is where all the difficult descisions are placed;
Do I want that app or this one?
Is this app privacy conserned or that one?
Does this app work on GrapheneOS or not?
If I do not install from google store, how do I ensure it remains up to date?
Goole Play Store & Services #
The first choice to make when starting on the path to using GrapheneOS is to decide whether or not to install Google Play and Services. This is entirely optional, but certain apps will not work without Services, or can only be installed through the google Play store (because the publisher does not publish an offical APK in other channels).
I am no expert in how google services work on normal android phones, but as I understand it, they run as system apps that has root access, meaning that they can essentially access any piece of data it may choose to do.
On GrapheneOS, the developers have sandboxed Google Play and Google services to run as a app in the normal user land, without any special permissions. You can head over to the Documentation to read more details.
Due to the need for banking apps and a few other requiring google services to work, I decided to go the route and install the sandboxed google play, which can be found in the GrapheneOS App store.
I do however want to avoid installing apps through the google play store as far as possible, so whenever possible, I will install the APK directly from the developer if it is available, and only use google play store when strictly necessary. Which takes me to the next challenge:
Keeping apps up to date #
When you install the app directly from an APK distributed by the developer, there is no automatic check if newer versions are available, unless the app itself is built with mechanisms to check for newer versions of itself. From my reading on the matter, it appears that is seldom the case, and there is a need for some solution for regularly checking for updates.
The simple solution that seemed to be mentioned all over the place when looking online is Obtainium, which lets you install apps “from source”, where you configure where the source is found as an input to the app, and it will then download and install the APK for you. Because you configured how to find the release, it can then keep using that config to check if any newer releases are available. The app supports releases from a dozen different source websites, such as e.g Github or Gilab.
Web Browser #
In the old days I used to use Opera as a web browser, but the last few (actually quite a few) I have been using ore or less Firefox or Chrome/Chromium.
I do not remember why I stopped using Opera, but I it might have been because Vivaldi was released. Vivalidi was created by the same guy who originally created Opera, and I remember playing around with it in the early days. I did at that time grow tired of the rapid release cycle of the early version (which is only natural), so I went with something more stable. Not too long ago I remembered about Vivaldi, and decided that now is the time to make the switch back, so for this phone I am going with Vivaldi.
Messaging #
Along with a good Camera, the ability to message with my friends on the platforms they actually use are the biggest reasons why I could not use a normal “dumb-phone” when I tried to make the switch earlier. While I acknowledge that messaging can easily be something one spend more time on than needed, and can also be used to fuel the dopamine addiction, I have decided to go all-in on messaging platforms, meaning:
- Signal
- Messenger
- SMS
I regularly use all these platforms for differnt people and purposes, so I might as well embrace it and install all. That way I do not need to keep another phone ready in order to be able to reach person X or person Y.
UI #
I want to have a clean look, which also minimises the want to use the phone, so I went with Unlauncher, which presents you with a list of 6 apps, and then a swipe to see a list of the rest. When the UI is in plain text and black and white, I do not really see any other way of minimizing the urge to use the phone, other than to literally further restrict the apps that are installed.
Conclusion #
I think I will call it a post, and end this brief description of the config I have used on the phone. I have installed a few other convenience apps, such as a podcast app, bus ticket app and banking apps but I do not think there is much value in discussing these at great length.
It probably has become more of a smart-phone than I intended. In the end it remains to be seen wheter this will reduce my screen time, but there should atleast not be any excuses that the dumbed down phone lacks any must have features.