• 0 Posts
  • 18 Comments
Joined 1 year ago
cake
Cake day: July 11th, 2023

help-circle








  • No, to clear confusion when they mean transfer they are not really transferring the SIM. To explain fully, when you first setup eSIM, you give IMEI to your operator. Then you get a QR code which is associated with your IMEI. When you scan it you are connected to Remote SIM Provisioning system and your phone downloads SIM profile. Now when you switch phones if your carrier supports eSIM transfer, which is not supported by all carriers. Your old phone which has the eSIM will tell carrier your new phones IMEI, once you confirm the transfer, your new phone will contact Remote SIM Provisioning system to download new SIM profile. Then once it’s activated the old phone deletes the eSIM. The way how your old phone knows your new phone is through the Apple account for iPhones and for Samsung/Google it will something similar. Also keep in mind for iPhones you need to have same Apple account for both old and new phone, I am not sure about Samsung/Google’s implementation. Currently there is no standard for iPhone to transfer to Android or vice versa. Probably GSMA will come up with something or Apple and Google can make a standard.







  • First of all major corporations contribute to Linux kernel and there is very little contribution to a distribution. Why are they doing it? Because they benefit from their hardware being supported by Linux kernel(e.g Samsung contributing to Linux Kernel for SSD drivers) and now they can sell more, they can do this because it works with their business model. That is not the case with smartphones, in the smartphone world they are selling directly to a consumer and they need to do everything they can to differentiate themselves from other Smartphone makers. Mozilla tried the business model you mentioned but it didn’t catch on. Lastly you forget to understand the number of apps available on Google Play vs on Flathub. Google Play has ~3.5 Million Apps vs ~2000 Apps on Flathub. We are talking a different scale here

    Also speaking about Flathub, Flathub solves the issue of fragmentation by building an entire OS on top of another OS just to avoid the challenges of backwards compatibility. This has implications like huge app sizes because you are basically downloading the runtime and everything it depends on for each app. It works for most people because storage is cheap and can be upgraded at least in PC world. But still you will have issues with RAM because most flatpaks don’t share the runtime and you need to need load each runtime to memory and this implications like higher memory usage, slower app start times because you need to load the entire runtime first before even you start the app.


  • If you have any corporate backing wouldn’t it turn back into same situation as Android? Maintaining the app store, build tools, making new features, patching vulnerabilities e.t.c all require massive amounts of capital. Why would a company openly take initiative to do that? Meanwhile all others could free ride on it? Also any OEM’s coming in and customizing it to their liking and not following the standards because they are not bound too like in Android, wouldn’t that cause massive fragmentation. Back in the Symbian days this was the case where you need to customize your app slightly for each Symbian device, which meant you had to have the physical device. I remember back in the back in the day your office would be filled with these devices.