Migration of main phone (Pixel 4a) to #lineageos complete. Everything works except for the wallet. Banking (FINECO) works perfect. IO app (for italians) doesn't add driving license nor Tessera Sanitaria.
Battery lasts incredibly more: nighttime went from 85% to 84% with active wifi and network.
Also set up photo/video backup to my NAS with SyncThing.
I'll post some more updates in the next days.

https://lineageos.org/

@OrionKidder @baroqbard Same new tech these days is like burning money. Pixel 6 -> 7 about 3 months ago because the screen cracked on the 6. It was still usable and i was going to try GrapheneOS on the 6 but it just stopped working one day and i tried everything. i have a #degoogled to5 yr old Lenovo FHD 10" with #LineageOS & #Fdroid app repo which is just fine for everything loungeroom tablety i need it for.

@thomas_klopf @hobbs that will work fine. You might end up putting #LineageOS on them so it's a version of Android that's reasonably current. And if it's not something current enough, block it from the Internet at the edge.

I'm assuming with the above you have an edge router that runs #OpenWRT (or something of similar power). Given the tone of your toot, if you don't have something like that at the edge you would probably benefit from doing so.

Can any #Android #LineageOS or #e_OS Users help me choose a Gargoyle-free phone, please?

I don't need games. Music, GPS satnav, WWW, Tusky for Mastodon, various utility apps such as DNS, SSH, 2TB MicroSDXC (a lot of CDs copied as .flac and a few movies, about to pass the 1TB line).

I prefer 3.5mm headphone socket for accurate lip synch, but...
I found a Fairphone 4 with /e/OS already installed, which suggests custom ROMs are OK.

No 3.5mm socket, though. If I buy a USB-C adaptor, or buy USB-C headphones, will I get sound synch'd with video?

Any hints, please?

(I'm guessing that I'll need a 2nd phone for banking apps, if it has a custom ROM)

RE: https://fedi.nemo.earth/@bartonemo/statuses/01KFH5RWW6WRPV52Q8QM61W82V

No i #ubuntutouch poszedł pa pa z mojego #fairphone4. Koszmar obsługi stał się większy niż ekscytacja z korzystania. Jako że #calyxos nadal pracuje nad wznowieniem wydań, skorzystałom z #lineageos i jest zajebiście.

I have a working phone again. Did you know that phones sold through #Verizon have their bootloaders factory locked? That means that you have to use the operating system Verizon provides on the phone. You can't root it or install #LineageOS or do anything besides use it as Verizon intends until Verizon no longer supports the phone. I chose to buy a refurbished Pixel from somewhere besides Verizon this time around so I could install #GrapheneOS. It's working great!

my doov r77 pro has arrived. all going well i will finally replace my nokia 3310 from 2017.
#nokia3110 #doov #r77 #lineageos #dumbdroid

@sebsauvage @noopss je suis passé à #LineageOS sur mon xiaomi il y a quelques années et j'en suis content. Je ne sais pas si c'est toujours le cas mais le truc relou avait été de devoir s'enregistrer pour pouvoir débloquer le tel et installer le nouveau bootloader. Une adresse poubelle avait fait le taf.... Par contre si quelqu'un sait comment mettre à jour la version d'Android je suis preneur. Je suis bloqué sur la 12 donc bloqué sur Lineage v19.

Leaving The Apple Ecosystem – Doogee Blade10 Pro

https://medi-nerd.com/2026/01/22/leaving-the-apple-ecosystem-doogee-blade10-pro/

Adding Two Factor Authentication to Android (LineageOS)

I really like the idea of using biometrics to add extra security, but have always hated the idea that simply touching the fingerprint sensor would unlock your entire phone, so in my version of LineageOS the touch to unlock feature is disabled but I still use second factor biometrics for the security of various apps. Effectively the android unlock policy is Fingerprint OR PIN/Pattern/Password and I simply want that OR to become an AND.

The problem

The idea of using two factor authentication (2FA) was pioneered by GrapheneOS but since I like the smallness of the Pixel 3 that’s not available to me (plus it only seems to work with pin and fingerprint and my preferred unlock is pattern). However, since I build my own LineageOS anyway (so I can sign and secure boot it) I thought I’d look into adding the feature … porting from GrapheneOS should be easy, right? In fact, when looking in the GrapheneOS code for frameworks/base, there are about nine commits adding the feature:

a7a19bf8fb98 add second factor to fingerprint unlock
5dd0e04f82cd add second factor UI
9cc17fd97296 add second factor to FingerprintService
c92a23473f3f add second factor to LockPattern classes
c504b05c933a add second factor to TrustManagerService
0aa7b9ec8408 add second factor to AdaptiveAuthService
62bbdf359687 add second factor to LockSettingsStateListener
7429cc13f971 add second factor to LockSettingsService
6e2d499a37a2 add second factor to DevicePolicyManagerService

And a diffstat of over 3,000 lines … which seems a bit much for changing an OR to an AND. Of course, the reason it’s so huge is because they didn’t change the OR, they implemented an entirely new bouncer (bouncer being the android term in the code for authorisation gateway) that did pin and fingerprint in addition to the other three bouncers doing pattern, pin and password. So not only would I have to port 3,000 lines of code, but if I want a bouncer doing fingerprint and pattern, I’d have to write it. I mean colour me lazy but that seems way too much work for such an apparently simple change.

Creating a new 2FA unlock

So is it actually easy? The rest of this post documents my quest to find out. Android code itself isn’t always easy to read: being Java it’s object oriented, but the curse of object orientation is that immediately after you’ve written the code, you realise you got the object model wrong and it needs to be refactored … then you realise the same thing after the first refactor and so on until you either go insane or give up. Even worse when many people write the code they all end up with slightly different views of what the object model should be. The result is what you see in Android today: model inconsistency and redundancy which get in the way when you try to understand the code flow simply by reading it. One stroke of luck was that there is actually only a single method all of the unlock types other than fingerprint go through KeyguardSecurityContainerController.showNextSecurityScreenOrFinish() with fingerprint unlocking going via a listener to the KeyguardUpdateMonitorCallback.onBiometricAuthenticated(). And, thanks to already disabling fingerprint only unlock, I know that if I simply stop triggering the latter event, it’s enough to disable fingerprint only unlock and all remaining authentication goes through the former callback. So to implement the required AND function, I just have to do this and check that a fingerprint authentication is also present in showNext.. (handily signalled by KeyguardUpdateMonitor.userUnlockedWithBiometric()). The latter being set fairly late in the sequence that does the onBiometricAuthenticated() callback (so I have to cut it off after this to prevent fingerprint only unlock). As part of the Android redundancy, there’s already a check for fingerprint unlock as its own segment of a big if/else statement in the showNext.. code; it’s probably a vestige from a different fingerprint unlock mechanism but I disabled it when the user enables 2FA just in case. There’s also an insanely complex set of listeners for updating the messages on the lockscreen to guide the user through unlocking, which I decided not to change (if you enable 2FA, you need to know how to use it). Finally, I diverted the code that would call the onBiometricAuthenticated() and instead routed it to onBiometricDetected() which triggers the LockScreen bouncer to pop up, so now you wake your phone, touch the fingerprint to the back, when authenticated, it pops up the bouncer and you enter your pin/pattern/password … neat (and simple)!

Well, not so fast. While the code above works perfectly if the lockscreen is listening for fingerprints, there are two cases where it doesn’t: if the phone is in lockdown or on first boot (because the Android way of not allowing fingerprint only authentication for those cases is not to listen for it). At this stage, my test phone is actually unusable because I can never supply the required fingerprint for 2FA unlocking. Fortunately a rooted adb can update the 2FA in the secure settings service: simply run sqlite3 on /data/system/locksettings.db and flip user_2fa from 1 to 0.

The fingerprint listener is started in KeyguardUpdateMonitor, but it has a fairly huge set of conditions in updateFingerprintListeningState() which is also overloaded by doing detection as well as authentication. In the end it’s not as difficult as it looks: shouldListenForFingerprint needs to be true and runDetect needs to be false. However, even then it doesn’t actually work (although debugging confirms it’s trying to start the fingerprint listening service); after a lot more debugging it turns out that the biometric server process, which runs fingerprint detection and authentication, also has a redundant check for whether the phone is encrypted or in lockdown and refuses to start if it is, which also now needs to return false for 2FA and bingo, it works in all circumstances.

Conclusion

The final diffstat for all of this is

5 files changed, 55 insertions(+), 3 deletions(-)

So I’d say that is way simpler than the GrapheneOS one. All that remains is to add a switch for the setting (under the fingerprint settings) in packages/apps/Settings and it’s done. If you’re brave enough to try this for yourself you can go to my github account and get both the frameworks and settings commits (if you don’t want fingerprint unlock disable when 2FA isn’t selected, you’ll have to remove the head commit in frameworks). I suppose I should also add I’ve up-ported all of my other security stuff and am now on Android-15 (LineageOS-22.2).

@Brotmann
Oh, #GrapheneOS... Respekt!
(Ich habe früher meine alten Smartphones mit #LineageOS bespielt. War aber mehr so eine Spielerei.)

Ich habe Windows und Linux als DualBoot.
Mal sehen wie lange noch.

Wer Linux zumindest mal "gesehen" hat, kennt schon mal ein paar freie Alternativen. Es geht um Empowerment.

Mein alarmistischer Post 🚨 ist eigentlich nur ein Aufruf, wertvolle "Backups" auch bei sich offline Zuhause zu haben. Es muss ja nicht zum "äußersten" kommen.

i właśnie dlatego wszystkie startery z T-Mobile po użyciu utylizuję...

#tmobile #LineageOS

Ich darf euch freudig mitteilen: Android #LineageOS und #eOS Custom ROM installieren ist immer noch ein riesen Gefrickel. Ich hab keine Ahnung warum das so schlecht verbreitet ist.

Ich habe nicht damit gerechnet sowas direkt oben im deutschen Wikipedia Artikel von Android zu lesen, sehr nice.

#Android #Google #e_os #GrapheneOS #CalyxOs #LineageOS

Des rennais utilisateur de la #star (réseau bus/métro de l'agglo) par ici ?
J'ai envoyé un message pour savoir pourquoi leur appli avait besoin des #googleServices pour fonctionner et je n'ai pas eu de réponse. Sachant que j'ai #lineageos sans #microG je ne peux pas m'en servir. D'autres dans ce cas ?
Même si vous n'êtes pas dans ce cas écrivez-leur ici : https://www.star.fr/points-de-contact/bus-metro et sélectionner "Une suggestion"
#Rennes #noGafam #noGoogleService #bus

Und jetzt schreibe ich von einem Motorola G7 mit #LineageOS. Wieder eine Erfahrung mehr.
Einen Schritt näher an der digitalen Souveränität.

The Key2 family up to date. January 2026 security patch, Android 15.

Well, almost. There's still some polishing up to do but overall the port is in good shape. The regular Key2 has more issues than LE currently (and that is so sad - much nicer device). Apart from some modem firmware issues (Damn you BlackBerry for not releasing Pie!!!) the rest of the issues are very simple and should be fixed really soon. Feels good.

#lineageos #android #blackberry

Sony Xperia 1 IV und 5 IV: LineageOS 23 bringt Android 16 auf die Klassiker
https://www.schmidtisblog.de/sony-xperia-1-iv-und-5-iv-lineageos-23-bringt-android-16-auf-die-klassiker-1791646/

#Android16 #LineageOS #LineageOS23 #Sony #SonyXperia1IV #SonyXperia5IV

Am Wochenende war wieder viel los bei uns. Die Anzahl der Reparaturen pendelt sich gerade bei 50 ! ein.

Besonders hervorheben möchte ich diesmal die Damen an den Nähmaschinen. 4 Maschinen waren kontinuierlich am Surren.

Auch im Computerraum herrschte reger Andrang, um Altgeräte mit passender Software weiter nutzen zu können.

#WerkstattCafe #RepairCafe #reparieren #reparierenStattWegwerfen #Wiesloch #BürgerstiftungWiesloch #EndOf10 #Linux #LinuxMint #LineageOS #DUTgemacht