Unfortunate, but somewhat of a formality. AOSP Messages and Dialer were essentially deprecated as it was already, and we have many projects ready to take their place.
It seems to me that that might seriously deter third-party Android distributors—AFAIK most do not ship stock Google apps for all the basic utilities, they only ship the auxiliary ones like Gmail or Docs.
Yeah, I've been watching the mobile Linux space with interest but it's definitely not in a place yet where I would consider using it as anything more than a novelty. The PinePhone is a neat little piece of hardware but no way it can replace my LineageOS phone right now.
I was vaguely wondering how hard it would be to use a GNU/Linux laptop as a phone. If you always carry a laptop, that's more-reasonable than it might seem, and that opens things up hardware-wise a lot. There are at least three obstacles:
The touch-oriented app infrastructure is stronger on smartphone OSes.
Laptops aren't as good at idling power-wise as phones. You want to be able to listen for calls without consuming a lot of power.
Apparently, while you can get 5G modems for laptops, getting one for a computer that can do voice service is not an option today. You can do VoIP or something, but I suspect that you're looking at a latency hit then.
Can they at least handle texting? A lot of services require SMS-based 2FA (insecure as it is) these days, so a phone that can't receive texts is a complete non-starter.
I don't know that off-the-top-of-my-head, but I would guess that with normal voice service the modem may well also handle texts, as at least historically, I believe the SMSes went over space in some sort of command channel separate from the per-active-phone timeslice reserved for voice.
However, you could hypothetically get SMS service and relay that to a your laptop-phone over IP from some service that provides VoIP service. With SMSes, unlike with voice, the latency shouldn't really matter.
Big tech conglomerates thrive on their user base. They lure you in, get you hooked into their ecosystem, and then try to convince you to become dependent upon their services.
This tactic is just gas-lighting. There are other options out there but they don’t want you to be aware of them or seek them out.
This is a shitty tactic for sure, but it's not gaslighting. Gaslighting would be if they acted like everyone who mentioned the AOSP dialler was crazy for thinking it ever existed. This is standard drug-slinger bullshit.
I got sick of vendors being a year behind on updates which would prompt me to use a custom ROM. Decided to finally just get a pixel and live with the fact I will never be able to de-google myself unless I totally leave the eco-system
Aren’t there alternative dialer and messaging apps out there? The existing dialer and messaging apps on AOSP are already old & massively out-of-line with the rest of the OS.
I'm guessing it's not a big deal to replace it with a third party text messaging open source app; I'm not sure about the Dialer, though.
It would be an interesting solution, to port a few mobile Linux apps to Android (some of them are already there) - I'm a bit worried about potential maintenance burden for platform support; but it could benefit KDE/GNOME apps by getting feedback from a bigger bunch of users.
undefined> Because Android users notoriously complain about their OS not being completely locked down with zero freedom whatsoever!
Yes so Android is so locked down because Google deprecated 2 apps that 2/3 of my Android phones did not use out of the box instead having oem alternatives plus 3rd party ones.
Google is fucking up Android trying to close it down and put themselves in absolute control but this is actually meaningless. Now playintegrity and locking down payments behind it is a much more annoying and effective strategy.
But...but.... Isn't AOSP open source? Did someone lie to me? Just restore the functions! Right? Am I right?
Or was Google just exploiting people believing that they were participating to an open source project?
This news serves as perhaps further evidence of AOSP’s reduced significance, as Google seeks to tie more and more previously open-source features behind its own proprietary frameworks and services.
OK Google, you win. I capitulate. Next phone is going to be Apple. If it's locked down, low customization walled garden either way I'd rather something with trade in value and a bit of snob appeal.
Wish I could, and I'm completely with you on both manufacturing and mining needed to enable our phone addictions. But I need it to function in modern society, much like my car or industrially farmed food. Being reachable and being able to reach out 24x7 is now an expectation. I don't have the practiced skills to be useful as an agrarian, and not being into religion I'm pretty sure the Amish wouldn't take me in.
Once the not-user-serviceable battery dies or hardware start to glitch at around 2 years of age a replacement is mandatory for me. Apple's phones seem to be designed for a service life of 3-4 years rather than 1-2, so that may be a way to help.
Add comment