131–140 of 258 posts
Where I live, an sms app is not very important. It's almost exclusively used for two factor authentication messages. Everyone uses WhatsApp, signal, telegram etc, even businesses and services. So having a bare bones aosp messaging app was never an issue for me. Having said that, I find fossify messages pretty good. Will try out the new GOS app too.
Unfortunately I think that feature is shutting down.
https://www.verizon.com/support/vtext-vzwpix-shutdown/
I'm still waiting until RCS is supported before I actually use it.
Earlier quoted context omitted.
What's so difficult about implementing RCS from a technical perspective?
https://grapheneos.social/@GrapheneOS/117225561294973728
Earlier quoted context omitted.
The overwhelming majority of consumers just prefer larger screens (myself included). People seem to forget that Apple releasing the Mini was them listening to the minority and the sales numbers if it were poor versus the rest of the lineup. And why would Meta even do that?
Or maybe the majority of people buying a new damn phone every other week just prefer it'd be a tablet
Earlier quoted context omitted.
also I think RCS is way to insecure for Graphene OS - they have no way of making sure the communication is actually 100% secure. In my experience, Graphene OS doesn't make compromises.
Why would they support SMS then?
One feature I just found out about after trying it is that you can text email addresses. Unfortunately I think that feature is shutting down. https://www.verizon.com/support/vtext-vzwpix-shutdown/ I'm still waiting until RCS is supported before I actually use it.
It's not as funny in hindsight, given the unexpected results of that election, but at the time, it felt like top-tier humor.
I wish they prioritised the call app. It is beyond appalling. You can't even determine when a call happened, beyond the generic low fidelity "[time] ago". It also almost feels like tapping anything makes me accidentally call people. Abhorrent UI/UX to be completely honest.
This is completely false. Tap the call, tap "call details" and its there. Took be 2 second to disprove. This is lazy to the point of being seemingly malicious commentary.
Your comment is unnecessarily inflammatory.
With a seemingly insurmountable workload - maintain an actually secure OS fork - for a small team, I wonder how GrapheneOS prioritizes things like messaging apps? I'm not saying it's wrong at all; I am just interested in the thinking inside a project like that. I can imagine many reasons to devote resources to it: * A platform is only as good as its apps. If they want to grow GOS in the general public, it requires a…
GrapheneOS has made a big push to hire a bunch of experienced, talented app devs, and they have been slowly chipping away at Messaging for a few months. They now have the resources to take on the AOSP apps and resume with the GrapheneOS apps. The rest of the AOSP apps are also planned to be overhauled. They also plan to eventually support RCS in the Messaging app.
That's great. How can a FOSS project afford that? Where does GOS money come from? Did Daniel win the lottery?
Earlier quoted context omitted.
Simple. Fairphone doesn't want GOS. Forking GOS and porting it to a new device is a huge and unreasonable ask for an individual user. Even less so when you include the fact that you'll need to keep it up to date.
Why? Because of drivers? Don’t they already have Linux drivers for the fairphone? I wonder if fable or astra could wire everything up.