Dans le cadre de mon partenariat avec Commown, j'ai eu en prêt 2 Fairphone, modèle 4 et 6, qui sont tous deux sous la dernière version de Murena /e/Os (et que je maintiens à jour en appliquant les dernières versions quand elles sont disponibles). Dans le présent article, je teste la connexion de Samsung Galaxy Buds 2. Car comme je le disais dans mon article Ubuntu et Samsung Galaxy Buds 2, je dispose de ces écouteurs sans fil, que j'utilise au quotidien pour l'écoute de mes podcasts. Ces écouteurs se connectent en Bluetooth.

Sur le Fairphone, sous Murena /e/OS, ils sont reconnus par défaut. Mais il me manque des fonctionnalités. Car par défaut, pour le niveau de batterie, j'ai une petite barre de niveau, à côté de l'icône Bluetooth dans la barre où on retrouve l'heure, le réseau, le niveau de batterie.

Pour le niveau de batterie, je n'ai pas le détail par écouteur (gauche /droite) comme je l'avais avant sur mon Samsung. Et j'ai besoin de savoir / d'avoir le suivi de la batterie des écouteurs et du boîtier (qui a sa propre batterie).

Je suis donc aller dans le AppLounge et j'ai installé l'application "Wearable de Samsung". Une fois lancé, elle cherche les écouteurs mais ne les trouvent pas... Car il faut également installer le "Galaxy Buds 2 manager" (où équivalent selon son modèle de Galaxy Buds).

En complément, je peux également mettre le Widget de Galaxy Buds pour activer la réduction sonore par exemple.

A noter que Commown propose aussi la location de casques filaires ou Bluetooth et enceintes Bluetooth, pour la visio conférence ou pour brancher à son Fairphone.

# Introduction

I recently wrote an article : Double authentification, ma gestion, and this one complements it. As mentioned in my article, for reasons of convenience and a bit of history, I have long used Authy (because there was a desktop client available for Linux, for the seamless key synchronization aspect across different devices).

# Migration to Fairphone with Murena /e/OS

As part of my migration to Fairphone with Murena /e/OS, I sought to transfer most of my applications and continue having the same uses. Being able to continue using two-factor authentication was an absolute necessity.

So, I naturally installed the Authy app. The app installs, but at the configuration (login) stage, I encountered the following error : "403 The device, app do not meet the minimum integrity requirements". This error seems to have multiple causes, which can be summarized as "Unlocked Bootloader / Custom ROM."

In other words : it is necessary to have an "official" Android, and alternative de-Googled Android versions are not compatible. And Murena /e/OS is therefore not compatible.

# Migration to Aegis Authenticator

I have known about the Aegis app for a long time, but out of habit, I never took the time to look into it. The necessity to change was therefore the opportunity/moment to explore it. For this, there are two places :

– The website : https://getaegis.app/
– Code source d'Aegis Authenticator sur Github

Note that Aegis is free software under the GPL-3.0 license.

# Why Aegis and not a digital vault ?

Why Aegis and not a digital vault (KeePassXC, Vaultwarden, or others) that offers two-factor authentication/OTP - One-Time Password features ? For separation reasons : not putting all your eggs in the same basket, and for convenience (having a dedicated and easy-to-use app on your smartphone).

# Migration Process

In my password manager, I have a "2FA" tag to immediately identify accounts where I have two-factor authentication enabled, and a second tag to specify the type. Filtering by "Authy" allowed me to see only the accounts with 2FA in Authy.

I had also tracked all these services in a spreadsheet, with a column indicating whether I had generated backup codes. I reused this file by adding a column to track the progress of switching to Aegis and ensure I didn't forget anything.

One-to-one change
For each account where I use two-factor authentication with a code (I have other services where it's an SMS or email code that is sent...), when logging in again, I went into the settings, disabled 2FA, reset it, and re-scanned the QR code to add 2FA in Aegis. I requested new backup codes and saved them securely.

Verification
For security and to ensure it worked, I kept the tab open and, in a private browsing window, re-validated my two-factor authentication on the service by reconnecting using the second factor (code provided) via the Aegis app on the Fairphone.
If everything was good, I updated my tracking file, and deleted the entry from Authy (on the old phone). Aegis on the Fairphone then became my default app.

When is it done ?
Simply when my tracking file is complete and up-to-date, and I no longer have any codes generated by Authy. This took a few days because there were accounts I used every day and others I only used occasionally.

# Synchronization and Backup

To validate the synchronization and backup process, I installed Aegis on my old phone. I created a backup in a folder synchronized with the Nextcloud client on the Fairphone and restored the backup in Aegis on the old phone. This allowed me to validate the synchronization and backup process between different devices.

# Remaining Tasks

Customize a bit by manually adding icons (Authy did this by default) and tags to categorize the different factors. But nothing urgent—just cosmetics.

# Conclusion

The migration process allowed me to switch from a proprietary app to free software, to free myself from a third-party service, and to take another step toward my independence. I still have synchronization between different devices, and I can make backups.

# Introduction

J'ai récemment écrit un article Double authentification, ma gestion et celui-ci vient en complément. Comme dit dans mon article, pour des raisons de facilité et un peu historique, j'ai longtemps utilisé Authy (parce qu'il existait un client lourd disponible sous Linux, pour l'aspect synchronisation clefs en mains entre différents appareils).

# Migration vers Fairphone avec Murena /e/os

Dans le cadre de ma migration vers Fairphone avec Murena /e/os, j'ai cherché à reprendre la plupart de mes applications et continuer à avoir les mêmes usages et pouvoir continuer à faire de la double authentification était une nécessité absolue.

J'ai donc naturellement installé l'application Authy. L'application s'installe mais au moment de la configuration (connexion), j'ai l'erreur suivant qui s'affiche : "403 The device, app do not meet the minimum integrity requirements". Une erreur qui semble avoir plusieurs causes qui peut se résumer en "Unlocked Bootloader / Custom ROM"

Dit autrement : il est nécessaire d'avoir un Android "officiel" et les Android Degooglisés alternatifs ne sont pas compatibles. Et Murena /e/os n'est donc pas compatible.

# Migration vers Aegis Authenticator

Je connais le nom de l'application Aegis depuis longtemps, mais par habitude, je n'ai jamais pris le temps de me pencher dessus. L'obligation de changer est donc l'occasion / le moment de m'y intéresser. Pour ce, 2 endroits :
– Le site web https://getaegis.app/
– Code source d'Aegis Authenticator sur Github

A noter qu'Aegis est un logiciel libre sous licence GPL-3.0.

# Pourquoi Aegis et pas un coffre-fort numérique ?

Pourquoi Aegis et pas un coffre-fort numérique (KeepassXC, Vaultwarden ou autre) qui propose des fonctionnalités de double authentification /OTP - One time password ? Pour des raisons de séparation : ne pas mettre tous ses oeufs dans le même panier, de facilité (pouvoir avoir une application dédiée et facile à utiliser sur smartphone).

# Processus de migration

Dans mon gestionnaire de mot de passe, j'ai un tag "2FA" pour savoir de suite les comptes sur lesquels j'ai la double authentification d'activé, et un second tag pour préciser le type. Un filtre sur "Authy" a permis de n'avoir que les comptes ayant un 2FA dans Authy.

J'avais également tracé tous ces services dans un fichier tableur, avec une colonne indiquant si j'avais bien généré les codes de secours. J'ai réutilisé ce fichier en rajoutant une colonne pour suivre la progression de la bascule vers Aegis et être sûr de rien oublier.

Changement 1 à 1

Sur chacun des comptes pour lesquels j'utilise la double authentification avec un code (j'ai d'autres services pour lesquels c'est un code par SMS ou par mail qui est envoyé...), au moment de la nouvelle connexion, je suis allé dans le paramétrage et ai désactivé le 2FA, remis et rescanner le QRCode pour ajouter le 2FA dans Aegis, j'ai redemandé des codes secours que j'ai sauvegardé en lui sûr.

Vérification

Par sécurité et pour être sûr que ça marche, je garde l'onglet ouvert et dans une fenêtre en mode navigation privée, je revalide ma double authentification sur le service en me reconnectant en utilisant le 2ème facteur (code fourni) via l'application Aegis, sur le Fairphone.

Si tout est bon, je trace /mets à jour mon fichier de suivi, je supprime dans Authy (sur l'ancien téléphone). Et Aegis sur Fairphone devient alors mon application par défaut.

Quand est-ce que c'est bon ?

Tout simplement quand mon fichier de suivi est complet et à jour et que je n'ai plus de code généré par Authy. Cela a pris quelques jours car il y a des comptes que j'utilisais tous les jours et d'autres que je n'utilise que ponctuellement.

# Synchronisation et sauvegarde

Pour valider le processus de Synchronisation et sauvegarde, j'ai installé Aegis sur mon ancien téléphone. J'ai fait une sauvegarde dans un dossier synchronisé avec le client Nextcloud sur le Fairphone et restaurer la sauvegarde dans Aegis de l'ancien téléphone. J'ai ainsi pu valider le processus de synchronisation et de sauvegarde entre différents appareils.

# Reste à faire

Personnaliser un peu avec l'ajout d'icône manuellement (Authy le faisait par défaut), de tags pour classer les différents facteurs. Mais rien d'urgent, juste de la cosmétique.

# Conclusion

Le processus de migration m'a permis de basculer d'une application privatrice à un logiciel libre, de me libérer d'un service Tiers et de faire un pas de plus vers mon indépendance. J'ai toujours une synchronisation entre différents appareils, je peux faire des sauvegardes.

As part of my partnership with Commown, I'm experimenting with and documenting my transition to a Fairphone running Murena's /e/OS. In this article, I'd like to share some of the thoughts and reflections I've had while preparing for this switch.

# Introduction

I'll keep this much shorter than my friend Souverain, who recounted his entire smartphone journey in his article, ending with the announcement of his switch to a Fairphone with Murena's /e/OS.

I've had a mobile phone since 1998 (I've used various models, including the Nokia 3310). My first real smartphone was in 2013 : the ZTE Open C with Firefox OS, which I got the year after Free Mobile launched (before that, I didn't have a data plan, so no smartphone). Then came the Sony Z3C with Firefox OS, followed by a return to Android 4.x when Firefox OS was discontinued. I used second-hand phones until I got my first Samsung in 2017 (a work phone), then a second one (A15), and finally my current phone, an S21 (released in 2021, purchased in June 2022). I've had the same phone for a little over four years. It still works perfectly well, even if it no longer receives security updates.

# Why /e/OS and Not Another Solution ?

In the various articles I'm preparing about Murena's /e/OS, I'll explain—directly or indirectly—why I chose this option. But in short, it's a personal choice : I need a phone with the apps I already use, and I want to test the feasibility of migrating to a phone I could recommend to my family. I don't want a "geeky" phone, but a reliable alternative that's compatible with basic, non-tech-savvy users, like my parents.

I'm aware of the other solutions out there. My friend Walid NOUH and his podcast do an excellent job covering them—check out the dedicated episodes of the *Projets Libres* podcast to learn more.

My choice of Murena's /e/OS is also because it's still Android-based, so I won't feel out of place. I've long used free apps from F-Droid, but also proprietary ones.

One of my goals is—and will remain—sharing my experience so that everyone can form their own opinion and benefit from my feedback.

# My Usage

In my feedback and transition to a Fairphone with Murena's /e/OS, I'll test and document my most basic daily uses : phone calls, text messages, photography, and podcast listening. I'll also cover specialized uses that depend on free or proprietary apps.

I'll likely have to make some choices or compromises. We'll see how it goes.

I'm sticking with a smartphone, even though I'm aware of dumbphones (basic phones). Going back to that kind of device would be very difficult for me (though not impossible—I lived the first 20 years of my life without a mobile phone ; however, my lifestyle has changed...).

I'm disciplined enough to avoid having tons of apps and constant notifications, and to manage my screen time. This will probably come through in my articles.

# How to Force the Migration ?

For every app that works and is set up on my Fairphone, I force myself to stop using it on my primary smartphone. But I don't delete it. This requires some discipline, but if I run into issues with my Fairphone, I'll always have a "backup phone" ready to use (one I won't need to reconfigure—just update and reinstall the apps).

Using my Fairphone for all my usual smartphone tasks (calendar, emails, social media) helps me get used to its handling and feel, so that this device—which can sometimes feel like an extension of myself—becomes "natural."

Until the big day when I move the SIM card into the Fairphone, making it my primary phone.

# Keeping Two Phones Just in Case

I've already managed two phones before—one personal and one for work. It's annoying but doable. My current phone then becomes a backup (with the Fairphone's Wi-Fi hotspot allowing me to access data on my old phone if needed). At worst, I can always switch the SIM card back.

# The Big Day – Moving the SIM Card to the New Phone

The day has arrived. I move the SIM card into the Fairphone and start using it as my primary phone.

# Introduction

As part of my partnership with Commown, I'm experimenting with and documenting my transition to a Fairphone running Murena's /e/OS. In this article, I'd like to share my (simple) methodology for handling the apps I'll need to migrate.

# Using Proprietary Solutions

Just as I use Windows in a professional context for client assignments (and have for a long time), even though I support de-Googling and oppose GAFAM, I'm not an absolutist. I have a Google account (though I don't use Gmail) for professional needs (e.g., joining Google Meet when invited) or personal use (for apps from the Play Store). I occasionally use WhatsApp because my aging family and parents use it as one of their social connections. So, I make compromises.

With proprietary apps, this highlights how much we're also dependent on interactions with others and the choices they make and impose on us. However, this migration is an opportunity for me to reassess these apps and, if possible or necessary, switch to a more open alternative... or not.

An Opportunity to Clean Up My Apps

This migration is also a chance to avoid reinstalling *all* my apps at once. Instead, I can install and configure them gradually, track any issues, update passwords if needed, etc. This also ties into the broader process of digital legacy planning, including account and app management.

# Analyzing My Apps

In a spreadsheet, I've listed and categorized all the apps I currently use on my smartphone—about fifty in total.

This is an opportunity for me to challenge each one : How relevant are they ? How necessary ? Are they open-source or not ? How can I recover my data ? And so on.

This analysis is entirely subjective and based on my personal needs.

# Categories

– Essential : I truly can't do without these. If they don't work, I'll need to find an alternative but still retain the functionality tied to the app.
– Non-essential : I'll reflect on whether the app is truly necessary. I might simply abandon it or reinstall it later if the need arises.

## Possible Alternatives

For all the open-source apps I use and which are available by default on F-Droid, I'll have no trouble finding them on /e/OS—there's no issue there.

For non-open-source apps, I plan to detail their migration in a future article : whether they can be installed (spoiler : I've had to switch to another app) and, if so, what the potential consequences might be.