13 ms·
Google is about to make life more difficult for custom ROM fans
- agufal 3y agoNot related to the article, but I heavily despise this site's cookie management options. How many third party vendors can a site have?? And all of them have "legitimate interest" checked...
- ocdtrekkie 3y agoTitle could just be "Google deprecates open source Dialer and Messages apps". But yeah, this is hardly a surprise, almost every app Google had on Android used to be open source and nearly all of them have been replaced with proprietary variants over time.
- behringer 3y agoJust another step towards Ubuntu or another proper linux distro to take over the phone space.
- jraph 3y agoUbuntu actually pioneered the domain with Ubuntu Phone, and then abandoned it. It's been taken over by UBPorts, a community effort, with Lomiri for it's graphical environment. I don't know these much, as I think they don't let you run regular Linux apps. There are many linux mobile distributions, I think the most mature / widespread ones are Mobian, PostmarketOS and Manjaro. And UBPorts of course. Mobian has been upstreaming most of its work to Debian proper, which is cool. I'm using Mobian but there's not much Mobian-specific stuff remaining. I think they nailed the development model.
- glodalitazic 3y agoSailfishOS is totally usable. It is not as open as some others, but they get more stuff to work
- fifteen1506 3y agoHow are they, as a company, with all the Russia shenanigans (trade bans, etc.?)
- unnah 3y agoFrom what I have been able to determine as a user, the sanctions have been a big blow to the company, but they are still able to operate in Western countries and are also seeking partnerships in China. We'll have to see if they can pull through and keep some part of their business profitable.
- jraph 3y agoYes, I always forget about it (because I'm not interested personally. The way I see it is that if I want a mostly open source mobile OS but with some proprietary blobs, Android is just fine. I just can't justify using SailfishOS).
- palata 3y agoI strongly disagree. It's just another step towards other open source apps taking over those two use-cases on alternative Android systems. AOSP is still open source, and maintained by Google. So this doesn't seem like a big deal to me, like at all. I feel like people tend to really under-estimate the difference between "proper linux distros" (why "proper", btw?) and Android. Android was designed for smartphones, good luck catching up with "proper" distros.
- jraph 3y agoThis is the kind of shit I thought could theoretically happen and it was one of the reason I got rid of Android a few years ago and got a PinePhone when my smartphone died. I've been counting on the Linux mobile ecosystem to develop so we have an good alternative to Android and iOS. It's not there yet. I need my phone to be reliable and IMHO, it would need to reliably let me place an emergency call if I ever needed it. It's not yet the case. For now, I'm using my first phone, which is not a smartphone, and the PinePhone serves the smartphone-specific needs I have on the go like look something up on the internet or display a map. Which is already something. The Linux mobile ecosystem has greatly improved though, I still have hope that it'll be usable in a few years.
- charcircuit 3y agoThe Pinephone can suffer from the same issue where people maintaining the software included may decide they no longer want to maintain their software anymore. It's no different for this. Either someone needs to step up to mountain it or you replace it with something else. Wanting to get rid of the rest of Android just because dialer and messenger are no longer maintained is throwing the baby out with the bath water.
- gostsamo 3y agoPinephone has multiple compatible os-s, while most android phones don't have alternatives and become unusable if android drops support for them. Also, Google and the big OEM-s have the incentive to break compatibility to provide you with the newest gadget, which is not true for the pines. yet.
- charcircuit 3y agoPlenty of android phones have alternatives. It's what custom roms in the title of this article is referring to.
- jraph 3y agoBut these custom ROMs are hard to maintain especially as soon as when the phone manufacturer drops support. There's no way to get the latest AOSP on these devices forever. Hard work is required to port any new version and that's not always possible because AOSP comes to rely on newer kernel versions but you are stuck with the heavily customized one (+ the blobs) the manufacturer provided.
- jeroenhd 3y agoMost custom ROMs don't seem to use the AOSP dialer anyway. I've mostly seen forks with some nice features Google's dialer still lacks (call recording, for one). AOSP hasn't been a useful Android distribution for years. Luckily, you can make it useful through third party apps like the Simple apps: https://www.simplemobiletools.com/ https://www.simplemobiletools.com/
- jraph 3y agoif QKSMS still exists, it seems like a good replacement for the messaging app. That's what I used when I used Android a few years ago.
- hans_castorp 3y agoIt still exists. F-Droid also has alternative dialers, so I don't see how this is a big issue.
- magnat 3y agoQKSMS has not been updated for two years and has broken MMS support.
- Ruthalas 3y agoDo you have a suggestion for an alternative?
- magnat 3y agoI use custom fork of AOSP Messaging (on local LineageOS/microG build) with some minor UI tweaks and bugfixes. I have tried all other messaging apps on F-Droid, but every single one of them was broken in some way (mostly regarding MMS support or notifications while in deep sleep) or was missing a key feature (like delivery notifications). The problem with MMS is that there is no built in system-level support for the protocol on Android, and due to legacy of 3G network/WAP, the protocol is quite odd when compared to modern alternatives.
- 3y ago
- tripdout 3y agoVery interesting article that talks about the progression of Google's closed source app alternatives: https://arstechnica.com/gadgets/2018/07/googles-iron-grip-on-android-controlling-open-source-by-any-means-necessary/ https://arstechnica.com/gadgets/2018/07/googles-iron-grip-on... I always thought that sure, they're deprecating old apps for the closed source Google version, which sucks, but at least AOSP still comes with barebones versions. But now AOSP, a mobile phone operating system, will come without calling and texting ability? How can Google even do that? These apps, old as they may be, can also still serve as useful reference points for making your own OEM-branded app.
- jeroenhd 3y agoThey're just saying they've stopped maintaining it, I'm pretty sure that puts these apps in the same situation as the Android 2 style music player that's still part of AOSP.
- luca020400 3y agoTheir plan is to remove them altogether. Still those apps have not been maintained in years, that's the normal course of action for apps in AOSP.
- hedora 3y agoI think the big question is whether they “improve” the APIs these apps require at the same time. That would break the alternative implementations.
- luca020400 3y agoAndroid APIs are stable and an app will keep working until Google decides to bump the min SDK version in Android itself. The APIs a Google app uses are the same as any other app. Unless the app is privileged ( = can use system APIs ) there's no difference in capabilities.
- albertopv 3y agoHow can you call Android an open source mobile OS anymore given even these basic functions will be dropped?
- hans_castorp 3y agoThere are open source alternatives available (e.g. on F-Droid). So I don't see why this is such a big issue.
- crote 3y agoWould you call Windows "open source" just because you run a few open source apps on it? Google is slowly but surely turning more and more components of Android into closed source code. This is a targeted effort to kill AOSP and lock consumers into their ecosystem. The end result will probably look a lot like macOS: a few open source parts, but primarily a proprietary stack.
- ars 3y agoThe OS and the default apps it comes with are really not the same thing.
- CrampusDestrus 3y agoWindows is not open source, AOSP is
- luca020400 3y agoA lot of people still don't see how the operating system as a whole is open source, not having properly supported open source apps is not the best, but while we can make apps and/or update the aosp versions, we can't make an operating system...
- palata 3y ago> A lot of people still don't see how the operating system as a whole is open source What? Just checkout the sources and go through them, maybe? > not having properly supported open source apps is not the best If your definition of "properly supported" means "supported by Google", I guess...
- notorandit 3y agoI would like to hear from the LineageOS developers. Closed source blobs and closer-and-closer source os are calling for the disaster.
- luca020400 3y agoYou'll hear that it's been happening since years, and while a lot of us tried to upstream some of our enhancements/changes hardly any of them got accepted ( or anyone is actively working on those apps to review them properly ). This changes nothing, we'll keep using our forks that didn't see a single change from Google in years at this point :)
- ftxbro 3y agotime to get some used electron microscopes and start carving my own transistor arrays into rocks
- alexhaber 3y agoDidn't Sam Zeloof do this exact thing?
- uneekname 3y agoPerhaps custom ROMs will only ever exist among a relatively small group of "hackers" or whatever you want to call us, but I do really hope we can grow this community in the coming years. You know that xkcd with n standards, let's add another, now it's n+1? That's kinda how I feel about Android ROMs these days. I'm hopeful we can join forces to a greater extent, and make these platforms easier for less-technical folks to access.
- gobdovan 3y agojoin forces to create the n+2nd standard.
- palata 3y agoI feel like custom ROMS have become really good these days. I have been using /e/ OS for 2 years, just like a normal stock Android. I got the phone with it (no need to install it myself), and never had to fiddle with it. I don't have the Google Services, but that's my choice. LineageOS, GrapheneOS, CalyxOS, I think all those are becoming really good.
- wesapien 3y agoI've been using custom ROMs since the Galaxy Note 1 came out (my first smartphone). My LG V20 is still working and getting mobile service while on LineageOS. GPS has been finicky on it but I have a Galaxy A70 for driving around for now.
- BLKNSLVR 3y agoI wonder what the overlap is between people who put custom ROMs on their phones and those who use their phones to make actual phone calls more than once a week. I think I made my weekly phone call a couple of days ago, only because my ISP doesn't allow cancellations via email.
- fifteen1506 3y agoAndroid ROMs allow telephony well. Personally, I'm on GrapheneOS. Your comment does make more sense if you're talking about non-Android ROMs. None of the existing ones convince me. See also: https://drewdevault.com/2023/06/16/Mobile-linux-retrospective.html https://drewdevault.com/2023/06/16/Mobile-linux-retrospectiv...
- 0xedd 3y agoGreat opportunity to take the plunge into a Linux phone, like Pinephone. Still in beta quality but with more people, more can be done. Personally, I daily drive it with compromise. Had I been a secretary, it wouldn't cut it.
- yMEyUyNE1 3y agoI am waiting for PostmarketOS to go mainstream.
- fsflover 3y agoIt doesn't need to go mainstream for you to use it.
- palata 3y agoI guess anything is an opportunity to mention one's favourite project. Don't get me wrong: I like mobile Linux distros (played with PostmarketOS), but I think it is completely off topic. All this article says is that Google will stop supporting 2 apps. Open source apps maintained by others will replace them, for sure.
- fsflover 3y agoThis is not completely off-topic. Google is moving away from open-source making Android more and more proprietary. If you care about it, there should be a moment after which you abandon Google and look elsewhere. For me, it already happened.
- palata 3y agoYes, I abandoned Google, but I am still running an AOSP-based system :-). AOSP is still open source, they just stopped maintaining two apps.
- deng 3y agoHas the author of this article ever used a custom ROM? There are so many free alternatives for these apps out there. If I remember correctly, LineageOS ships with their own version of Dialer/Messages anyway. I usually replace them with the versions of SimpleMobileTools, which work just fine. The main difficulty for custom ROMs are not these standard apps. The real issues are bootloaders which cannot be unlocked, undocumented binary&buggy firmware blobs, SafetyNet, Google Play Services, and so on. Just look how Google effectively broke the AuroraStore App recently. It's getting more and more difficult to use Android without a Google Account.
- quaintdev 3y ago> It's getting more and more difficult to use Android without a Google Account. Good that is how they shoot themselves in the foot. The more they do this, the more people will realise they need alternative and ditch Android.
- nickelpro 3y ago99.9% of consumers do not care about this and are totally willing (and expect) to connect their phone to their Google/Apple account Not saying the grievance isn't valid, but don't fool yourself
- thunderbong 3y agoWell, it's not like they have a choice, isn't it?
- palata 3y agoHmm I think it's getting pretty easy today to get a de-Googled Android phone that "just works". You can buy Murena phones that come with /e/OS pre-installed (I did that). Probably the same with GrapheneOS/CalyxOS/etc. Users are lazy and don't want to take such a risk, but they do have a choice.
- 3y ago
- tpush 3y agoThis is a total nothing burger with a terrible headline. Google is just deprecating AOSP Apps that neither them nor anyone else is using. There are plenty of better FOSS alternatives than what's in AOSP.
- Dwedit 3y agoThe much bigger thing making life difficult for Custom ROM fans is the "device fingerprint" nonsense making your device condemned to fail SafetyNet. Hope you never want to run a banking app.
- mcny 3y agoI got a locked iPhone SE 2020 from a prepaid carrier and never inserted the SIM card. It cost me under USD 200 including the one month of service but I just wanted to use this device on WiFi. I can now leave all banking apps out of my xiaomi phone running lineage.
- palata 3y agoRunning banking apps on my /e/ OS, no problem there.
- neurostimulant 3y agoInterestingly, Netflix was the one that give me problem (refused to run with unlocked bootloader). I can run all banking apps I need (5 of them) on my phone with unlocked bootloader just fine.
- NoGravitas 3y agoHmm. My phone runs LineageOS for microG, and both Netflix and my banking apps work fine. The bootloader remains unlocked. microG settings say that Google SafetyNet is on.
- fifteen1506 3y agoThat is probably the unlocked bootloader. On GrapheneOS (bootloader is locked at the end of installation) I get no problem nor warning. Google Wallet does does not allow to add a card, though, due to that failure of the "CTS Profile Match", which I assume is what you mean by "device fingerprint".
- palata 3y agoI disagree with this title. I use /e/ OS, and I couldn't care less about that news. I already use a custom SMS app, and I am not even sure if my system comes with the default dialer. There are many things Google can do to make like more difficult for custom ROMs, but I don't think this is one.
- ntp85 3y agoAh, a fellow /e/ user. While I completely agree with you concerning dialer and SMS apps, the mentioned SafetyNet restrictions from the article could be causing problems in the future as many apps, especially banking apps, potentially rely on those.
- palata 3y agoYes, I am a bit worried about SafetyNet as well.
- KingMachiavelli 3y agoThe real concern is not the loss of the AOSP apps but the lack of new but mandatory features in AOSP and even more undocumented APIs. For example, RCS only works with Google messenger and there's no sign of that expanding (unless your Samsung). Even Visual Voicemail which should/is an open standard has a lot of carrier specific code (I think it can still be extracted from the Google Phone app but I'm not sure on the license). NFC payments (tap2pay) seem to be impossible outside the few blessed implementations and even running those is a cat & mouse game with SafetyNet (now called Play Integrity). Android is still the most open source mobile OS (that's functional and has real security; mobile Linux doesn't count). But IMO it better remember why people pick it over iOS. I'm still optimistic, if open standards for the basic functionality is going to survive; it will be on Android. - Sent from my Google Fold running GrapheneOS.
- Catholic_Tree 3y agoI am curious, how is the experience of running GrapheneOS on the Google Fold? On my Pixel 6 it runs quite well, but I would imagine that the Folding aspect brings in quite a bit of additional complexity.
- KingMachiavelli 3y agoSo far it's been good, it's a lot faster than my Pixel 5 on GOS. I didn't play with the stock OS much but basic UI for the fold works the same. It's individual apps that need fold and/or tablet support like I have the use Gboard to get a decent tablet mode keyboard and the Pixel Camera to support the different camera modes. Overall it's quite obvious that it's really a phone + tablet which means a lot of things work OK but won't handle the 90 degree fold mode (table top) well. Also the tablet UI of many apps (especially FOSS) are unpolished.
- hbn 3y ago> RCS only works with Google messenger I don't get how Google can continue to call RCS an "industry standard" and do their campaigns publicly shaming Apple for not implementing it when this is the case. Not to mention RCS messages are mostly being routed through Google's own servers anyway because no carriers have implemented it. No wonder they want Apple to get on board with this "standard," it replaces SMS with a Google service.
- PufPufPuf 3y agoThis has absolutely zero consequences for custom ROM fans. Google hasn't been maintaining these open source apps for years. All custom ROMs use forks, alternatives, or even the proprietary Google ones.
- grishka 3y agoBack when I used custom ROMs, that was already a non-issue. Cyanogen already came with its own dialer and messaging apps, iirc.
- qwerty456127 3y ago> Google's decision to deprecate two key open-source apps What are "two key open-source apps"? > Google has quietly deprecated support for the Dialer and Messaging apps in AOSP. This means brands need to use their own apps or Google’s latest phone and messaging apps. Don't custom ROMs use either their own dialer apps or Google's apps already? What are the options other than Goole and your own? > Custom ROM developers might need to develop their own phone and texting apps How is this a problem? Developing a basic dialer or a messaging app seems a trivial task (perhaps I'm wrong, I can only judge on the UI/functionality and don't know the internals).
- sanitycheck 3y agoI got a new Android phone two weeks ago, Google's default messaging app has turned into such a mess that I've replaced it with one from F-Droid already - and I'm liable to do the same with Photos. I think this will have precisely zero impact on "custom ROM fans".
- oars 3y agoWhat app do you recommend from F-Droid? I've been looking for an alternative as well but none of the ones in the Play Store look appealing to me.
- genpfault 3y agoCheck out Simple SMS Messenger[1], been using it since Signal dropped SMS support. [1]: https://f-droid.org/en/packages/com.simplemobiletools.smsmessenger/ https://f-droid.org/en/packages/com.simplemobiletools.smsmes... [2]: https://f-droid.org/en/packages/com.simplemobiletools.thankyou/ https://f-droid.org/en/packages/com.simplemobiletools.thanky... [3]: https://github.com/SimpleMobileTools/Simple-SMS-Messenger https://github.com/SimpleMobileTools/Simple-SMS-Messenger
- sanitycheck 3y agoSlow response, sorry - too soon to say I recommend it but I'm currently using Simple SMS Messenger as mentioned in a sibling comment. Not at all fancy, works fine so far.
- ranting-moth 3y agoGoogle could have pretty much owned the entire messaging ecosystem today had they just done it properly to start with. When Android was new, you had to wait for eventually Skype to do an Android release. Then there was Hangout, Talk, Duo, Meet, ... and of course the built in SMS app.
- jbverschoor 3y agoNot really a “fan”, but after about 2 years you’re forced to install some custom ROM to upgrade to a more current version because nobody supports them anymore..
- public_defender 3y agoI agree with the many siblings that say this news is pretty irrelevant to people who use custom ROMs, but I don't think it's realistic to say that FOSS alternatives exist, at least for SMS. There are multiple references in this thread to Simple SMS, but that app is not at all ready for prime time. If your carrier/ROM didn't bundle an SMS app you can live with, I think you are out of luck. I'm glad to be proved wrong though, if anyone knows of a good SMS app.
- logicprog 3y agoQKSMS is great!
- public_defender 3y agoI admit I passed over trying this for whatever reason. I'll try it now and report back.
- NoGravitas 3y agoQKSMS has a better interface than Simple SMS Messenger, but it's unmaintained, and for me, it had the same or worse problems with MMS than Simple SMS has.
- public_defender 3y agoIt sure looks unmaintained! Here are my problems with Simple SMS that are fixed in QKSMS: 1) Long delay updating conversation after receiving a message (>5s). 2) Date sorting broken (old messages appearing at top of queue for no reason). 3) "Failed to send" sms users experience is bad (still testing on qk). 4) MMS sender ID almost always wrong (all messages in group MMS appear to be from the same person until you examine details). 5) Sending MMS with attachment/image always fails without verbose error (still testing qk) This is pretty abysmal. Do I use the unmaintained app that fixes 3-5 of these issues, or the apparently actively developed one with all the warts? I guess this is the state of basic phone functionality in vendor-free, google-free android.
- DeathArrow 3y agoHow are Google and Apple not monopolies? Just because we have two vendors instead of one?
- elforce002 3y agoYou can make a case for Google tbh. Apple has what, 30% of the market at best, while every phone manufacturer uses Google by default. Heck, I don't know where to begin to brake Google's grip without seriously fragment everything. You can't escape google even if you want to, whereas with Apple you only need to switch phones.
- izacus 3y agoApple has more than half of US market share.
- modshatereality 3y agoFor google, it's an open and shut case. Look up how they force numerous other companies to collude with them using their open handset aliance contract. They explicitly prohibit "forking android" which they consider creating a non-android OS with an android app loader as an "android fork".
- maksimur 3y agoI used to flash custom ROMs regularly until 2021, when I bricked a second smartphone. It was a rare mishap (went smoothly the other times), but it made me too scared to try again. This is to say it's already an anxiety inducing operation without Google interfering.
- codethief 3y agoI'm not particularly worried; GrapheneOS is already replacing/improving plenty of AOSP apps, so Messaging & Caller will likely just be added to that list.
- activiation 3y agoyou should be worried is you are using GrapheneOS though... why do you trust it?
- kevin_thibedeau 3y agoPretty ironic that a smart phone OS won't ship with a standard phone dialer. I guess it's time to get rid of the standard keyboard that's holding back innovation too.
- devit 3y agoLineageOS, GrapheneOS and others will mantain those apps or a replacement, so this is a non-issue.
- nologic01 3y agoOk, naive question but I would dearly love to have an informed answer as another phone of mine is dying, it is still TINA and I can't for the life of me project how this will play out: The first iphone was released in 2007. That's like 15 years ago. People were probably toying with "smart" phones already few years before that. Its not that the world doesn't know how to manufacture smartphones and/or write software for them. How come in 2023 there isn't an open source mobile phone that is reliable as a daily driver phone? With a financially healthy entity behind it. NB: It doesn't matter if its android or linux or firefox os or anything else. Surely there is a market for such a device. 1% of a billion is a big number. Is it because (pick all that apply or please add the true reason): * Are manufacturers a cartel and won't allow breaking the duopoly? (Doesn't seem plausible, Samsung toyed with Tizen) * Are governments happy to strike deals with the duopoly? (Doesn't seem plausible, at least in the EU) * Is it the telecoms that somehow don't want this to happen? Why would that be? * Is it the FOSS community that can't get its act together? (Doesn't seem plausible, both F-Droid and e.g., KDE mobile communities seem more than on top of supporting this) So where is the bottleneck? A free mobile device is maybe the most important piece of technology one could have at this moment. I can imagine various actors that would not want it to happen but at the same time all sorts of other actors that would very much want it to happen.
- sourcecodeplz 3y agoBecause just like with the iPhone mini, a small but vocal minority is not worth serving if development costs are too high. Most people don't care about hacking their phone. They just want one that works.
- LegitShady 3y agoBecause manufacturing mobile phones is hard and expensive. Companies have large teams of hardware and software people will incentivized to develop phones and lots of them fail. The best we’ve got so far are exactly custom android builds like grapheneOS or lineage that replace software on phones other companies build. Apparently google doesn’t like that, though, so they’re going to continue to make AOSP worse and worse to protect their spyware. The best case currently probably varies between something like grapheneOS on a pixel phone or lineageOS which is less privacy focused but has a much wider range of supported devices.
- motohagiography 3y agoArguably, the main thing standing in the way of a global digital identity scheme is Android fragmentation. From a strategy perspective, Google is probably getting pressure to solve that problem from it's "stakeholders." The case for the Pine phone and other divergent devices is incredibly urgent.