Comment on How is everyone dealing with Android 17's "Nearby Devices" change?
curbstickle@anarchist.nexus 8 hours agoThe solution is to avoid google going forward, for many reasons.
Comment on How is everyone dealing with Android 17's "Nearby Devices" change?
curbstickle@anarchist.nexus 8 hours agoThe solution is to avoid google going forward, for many reasons.
femtek@lemmy.blahaj.zone 7 hours ago
That’s why I use graphene but the permission is still there in base android.
pHr34kY@lemmy.world 2 hours ago
I’m actually using GrapheneOS.
curbstickle@anarchist.nexus 7 hours ago
The problem with graphene, unfortunately.
It doesn’t actually get away from google, at best its plugging holes in a (to me) sinking ship.
NarrativeBear@lemmy.world 6 hours ago
I wish there were some viable “fully cooked” alternatives. I won’t touch apple products with a 10 foot poll, and I owned the first and second iPhone.
As for Linux phone i have tinkered with it but its nowhere close to being a daily driver, yet.
Strangely sometimes I wish the Microsoft phone was not a total flop…
I guess the only thing left if a completely dumb phone, but that does not help if you use your phone more as a “pocket computer” then a phone at all.
curbstickle@anarchist.nexus 6 hours ago
Completely agree
My current decision is between a new Motorola signature 27 with graphene (running under the assumption Linux will be able to make the jump there, which isn’t an unreasonable conclusion to jump to), or getting a mostly basic flip phone that can hotspot and using a umpc with it.
Where Linux phones have failed for me is the limited options for phones and on the actual phone part, so I feel like separation that out with a nice umpc and letting a phone be a phone is a worthwhile option.
We’ll see how things play out though!