Phones are developed to store as much in RAM as possible. Storage is slow, and users are expected to switch between apps constantly. It’s not uncommon for hundreds of apps to be loaded, including their state, at the same time. Apps that don’t fit into memory are saved to storage, but the most common apps and services are kept around.
Common files are also cached in memory for performance reasons. If you don’t have any RAM available, browsing files or photos would be terribly slow.
The GPU shares RAM on many devices, and that’ll take a significant chunk out of your system memory. Rendering 60 frames per second on a 1440p screen isn’t cheap, especially if you have ten different apps ready to render full screen at all times.
My phone has about 4½GB assigned to applications, the rest is cache. I’d say phones with less than 6GB of RAM would work, but not very smoothly.
The more RAM, the easier switching between apps becomes. Websites and apps have become huge, not only because of inefficiencies but also because of how huge the graphics they need to render have become, and the expectation that everything works with a smooth 60-90-120Hz all the time. Do you need 12GB? Hard for me to tell. I can tell that my phone’s 6GB struggles when Firefox is open while Youtube is playing and I need to switch to my password manager. It’ll hold out, but only just, one more app and Firefox gets unloaded. Then again, my password manager seems to be suffering from some kind of memory leak, because there’s no reason it would need this much RAM.
I don’t know what Macbook you have, but if someone is buying a laptop these days, I wouldn’t recommend getting anything with less than 16GB of RAM or an upgrade slot. Web browsers have become operating systems of their own and buying 8GB laptops now will make your device last less than five years, at least comfortably. I would personally advocate for 32GB or more if you’re planning on using your laptop for ten years, based on current trends.
Even still, many people can and do use phones the wag they did desktops ten years ago. It’s not surprise to me that phones have grown to have desktop class RAM specs. Many people don’t know about it, but you van hook up a Samsung phone to a monitor and have a fully featured desktop right there waiting for you in DeX, you just need a Bluetooth keyboard+mouse to control it. I bet my parents could use a phone as a desktop without ever running into any trouble, partially because of how much RAM those phones sport.
If all you need is basic browsing and social media, you can go with 6GB of RAM, or even less. As time goes on, your phone will start to struggle with the ever growing websites and apps, but it’ll keep doing what it always did, you just see a few more loading screens when switching between apps. Any €350 phone will do fine for most people these days, I don’t get why people spend three or four times that on a phone if all they do on it is browse social media.
Settling for RCS means no E2EE. It’s also handing control over messaging back to carriers (or most likely, Google, because not many carriers have RCS servers) which is a step backwards.
For all of Apple’s many many faults, iMessage is a pretty good service once you pay the Apple tax to get in.
No, E2EE is not part of any RCS spec yet. Based on news articles, Apple is implementing RCS but will supposedly ask the governing standards bodies to add E2EE to the spec so they can implement it according to the official specifications.
Google has implemented their own E2EE on top of RCS (based on Signal’s messaging for one to one conversations, based on MLS for group chats), but they haven’t published any specifications for that. It shouldn’t be too hard to reverse engineer, but that shouldn’t be necessary for any open protocol.
If you mean this link: that’s a high level description of the protocol, but it leaves out important details.
For example, Google uses MLS for group chats, but the document only mentions the Signal protocol. In other words, E2EE for group chats is broken even if you manage to implement the protocol exactly as they describe.
For example, they say the client “registers with the key server” and “uploads the public key parts”. What server is that? What protocol do we use? HTTPS POST? Do we use form/multipart? Do we encode the key in PEM or do we submit they bytes directly?
Another example: “Key material, digest, and some metadata are encrypted using the Signal session”. Whay do you mean “some”? What algorithm is used to generate the digest?
The document is a nice high level overview, but worthless if you want to implement their protocol. It basically says “we put signal, and send the signal messages over RCS, with out own key servers. Here’s how the Signal protocol works”. If, for example, Ubuntu Touch would like to implement this into their messenger, they’ll need to reverse engineer Google’s Messages app, guided by the description in their whitepaper.
Carriers wanted RCS because WhatsApp and iMessage were taking away their ability to charge by the text more than anything. I think they all dropped their subscription model by now, but no doubt they’ll start charging you when you use the more advanced features of RCS (i.e. uploading 500MB files).
Google did come up with an alternative: Google Talk, then Hangouts, then Allo, then Google Chat, and I think I missed one or two. Unfortunately, Google employees only get promoted by launching new products, so every chat team wants to launch something new, and that’s why every year Google launches a new messenger.
Nobody I know uses SMS because carriers here still charged by the SMS five years ago. MMS has been turned off entirely by the largest carriers around. Why would I pay 5 cents per message, or €3 extra for unlimited text, when I could just use the data plan I already have for free? Messages cost kilobytes of data, fractions of a cent.
As for the evolution of SMS: SMS was free at first, then relatively cheap, because it used empty space in the GSM standards allocated for basic message passing. Someone noticed that there was some leftover capacity and thought they may as well use it for a small feature. Then once people started using it, this stuff stayed in.
MMS (the part where you send anything more than 140 characters to a single phone number) is using your data connection. Well, it’s actually using a separate data connection, but it’s all packeted, like RCS is. That’s why SMS works when you have a single bar of reception, but MMS struggles.
As of LTE/4G, everything is packeted networking. Phone calls (over VoLTE) are no longer directly routed audio links, they’re voice (or video, but nobody seems to implement that part) streams over a network connection. VoWiFi (WiFi calling) is basically a VPN tunnel with two audio streams inside it. A true 4G successor of SMS would he RCS, except you’d need a separate APN that normal applications couldn’t use to reach an internal IP address that’s not accessible over the internet.
Like how MMS is entirely optional for carriers to provide, so is RCS. That’s why Google runs their own servers. For the majority of people, they need Google’s servers because their carrier doesn’t offer RCS services. They basically took a component intended to be run by carriers only and said “fuck it, we’re a carrier now”.
There can be advantages to RCS if your carrier has a server you can use, but if you’re using Google Jibe, there’s not much, really. In theory Google could expose an RCS API that would automatically enable E2EE (if available) to other apps, like how you can access RCS received messages through the same API you can use to read MMS messages on Android phones with Google’s messages app, but Google hasn’t implemented that in core Android yet. Knowing them, they probably don’t want to be locked down in their encryption system or protocol by making it part of the standard distributed to every phone manufacturer, but it’s hurting the effort to go beyond SMS.
iMessage has one advantage, which is that it can fall back to SMS when it can’t teach its servers. In theory any app could implement that. I’m not sure if iMessage does anything to encrypt its fallback SMS messages (it could) or use a chain of them to also send the necessary metadata to put the SMS messages into an iMessage conversation, but it’s always an option.
For Android users, Google Messages and soon RCS adds the ability to communicate with iMessage users without requiring iMessage users to install another app. In the silly bubble shaming countries, this is a major advantage. Outside those, everyone probably already has either WhatsApp, Line, or Vibe, or in China WeChat, so you can just use that. On the other hand, it RCS is no different than all the others and comes preinstalled on your phone, why not use it?
With the European DSA quickly approaching, there’s a good chance we’ll also gain some kind of cross messenger interoperability in the future. Google already uses the MLS standard for group messaging, which is part of an effort to standardise messaging protocols, and when MIMI gets finalised next year, perhaps large European gatekeeper apps like WhatsApp will become interoperable with RCS and other messaging apps. In a perfect world, you could just install the messaging app you prefer, or stick with the default one, and communicate with every other messenger app out there. Kind of like how iChat/MSN used to work, but as part of the standard.
On the one hand: I don’t see a reason for Google to keep supporting old versions.
On the other hand: pushing an update to an old device and sabotaging it by showing an “install updates” popup (as if that’s even possible for devices still running Android 7, that’s bullshit) is just dickish.
The old version of Android Auto works perfectly fine. Show a popup once if you want (“your device will no longer receive Android Auto updates, third party apps may stop working”) but don’t actually disable anything that’s working perfectly fine.
Google pulled that shit before. I would understand if they had a customer support department that’d get flooded when newer hardware stopped working, but all Google has is a forum that no Google employees ever pay any attention to.
I don’t really see what server side stuff an app on the dashboard of a car would need. Their Google Maps API works all the way back to the one installed with Android 2, and failing that users can install a number of navigation apps. Same with their music app (they already killed Play Music anyway).
The only thing I can think of is that they’d be killing Google Assistant on old phones, but that wouldn’t mean the rest of Android Auto couldn’t still work.
I’ll be honest, personally I think the nail in the coffin was the Spotify-deal. If Google had been able to prove that it either has no special deals or only with tiny publishers (so it feels more like helping the underdog) then I don’t think they could have claimed that Google is treating anybody unfairly.
I use the app’s by local transit services and organisations (9292, NS) and so far that’s working out pretty well.
They don’t have the reminder to indicate when your stop is coming up, but the last two or three times I tried to use that with Google Maps it just didn’t warn me, so I don’t think I’m missing out on much.
There are a bunch of open source transit apps as well, but little work as well as Google does when it comes to planning trips and finding alternatives. Sometimes there just isn’t any open data about public transit and only a few shitty commercial apps have up to date information, but you could always check Google if the routes they suggest seem inefficient or too good to be true.
I think it makes sense. Xiaomi had a lot of issues with shady companies importing cheap phones for the Asian market, flashing the xiaomi.eu ROM onto them, and passing the off as official.
The fact they still allow you to unlock the bootloader in the first place shows they value the freedom to unlock these phones. When they came up with a plan to combat these reflashed phones, they could’ve simply locked down the bootloader entirely. Setting up a whole web service with SIM validation and such isn’t cheap, they spent money on keeping their phones open!
Level up your YouTube experience with these new Premium features (blog.youtube)
TLDR: Jump ahead button, PiP window, and smart downloads for Shorts
Ram in phones?
I don’t get why Android phones have so much ram....
Remember NFC dimples? (dimple.io)
I don’t and I wish I had known about them when they were still a thing....
Beeper ready to wave white flag if its latest iMessage fix gets shut down (www.androidauthority.com)
Android Auto will soon stop working on older devices (9to5google.com)
The Epic question: how Google lost when Apple won (www.theverge.com)
I’ll be honest, personally I think the nail in the coffin was the Spotify-deal. If Google had been able to prove that it either has no special deals or only with tiny publishers (so it feels more like helping the underdog) then I don’t think they could have claimed that Google is treating anybody unfairly.
Google Maps transit is still a frustrating experience despite the latest changes (www.androidauthority.com)
Samsung Adds More Devices to Its Self-Repair Program, Including Foldables for the First Time (news.samsung.com)