4 ms·

> I'm not really sure those comparisons are accurate any more They never were accurate because it's mostly not in the users control if/when they upgrade. The c

by mhurron 12y ago

> I'm not really sure those comparisons are accurate any more They never were accurate because it's mostly not in the users control if/when they upgrade. The carrier has to 'bless' you with the privilege of even being offered an update. This is one of the reasons I just switched to an iPhone.

untog 12y ago
It's as if you totally ignored the rest of my post. Was this in the Android 2.x era? That was awful, I agree. But like I said, these days it doesn't matter very much. Almost every single core app is updated via the Play Store, out of the control of carriers.
- mhurron 12y ago
  That's nice. That doesn't update the base OS. Have a bug? You have it forever. New features your phones hardware supports? Maybe you'll get lucky but they would prefer you to buy a new phone, so don't bet on it. > Was this in the Android 2.x era? Galaxy S3. Galaxy S Relay 4g. Android 4.1/4.0 respectively the day they were bought and the day they were traded in.
- soylentcola 12y ago
  I'm definitely more familiar with the Android side of things than with iOS but it really has more to do with the OEM. Sure, if you buy a carrier branded device then they will stick their approval process after the OS release and OEM porting but in general, it's more a firmware/driver issue a lot of the time. Apple's strength is that they provide the hardware and the software so they are responsible for building any new version of iOS with applicable drivers and firmware for each device. Core apps are one thing but if you want to update to the latest version of Android, you're mostly out of luck without the OEM's involvement. Third parties regularly work on building current versions for all manner of devices as soon as Google publishes the source but without driver source from the maker of the actual chips and other hardware, they're left cobbling together unoptimized drivers for important things like the cellular radio or the camera or reverse engineering their own. If it was just a matter of carrier interference, there would be a "vanilla" build available for every device shortly after release.

by mhurron 12y ago

untog 12y ago

It's as if you totally ignored the rest of my post. Was this in the Android 2.x era? That was awful, I agree. But like I said, these days it doesn't matter very much. Almost every single core app is updated via the Play Store, out of the control of carriers.

mhurron 12y ago
That's nice. That doesn't update the base OS. Have a bug? You have it forever. New features your phones hardware supports? Maybe you'll get lucky but they would prefer you to buy a new phone, so don't bet on it. > Was this in the Android 2.x era? Galaxy S3. Galaxy S Relay 4g. Android 4.1/4.0 respectively the day they were bought and the day they were traded in.
soylentcola 12y ago
I'm definitely more familiar with the Android side of things than with iOS but it really has more to do with the OEM. Sure, if you buy a carrier branded device then they will stick their approval process after the OS release and OEM porting but in general, it's more a firmware/driver issue a lot of the time. Apple's strength is that they provide the hardware and the software so they are responsible for building any new version of iOS with applicable drivers and firmware for each device. Core apps are one thing but if you want to update to the latest version of Android, you're mostly out of luck without the OEM's involvement. Third parties regularly work on building current versions for all manner of devices as soon as Google publishes the source but without driver source from the maker of the actual chips and other hardware, they're left cobbling together unoptimized drivers for important things like the cellular radio or the camera or reverse engineering their own. If it was just a matter of carrier interference, there would be a "vanilla" build available for every device shortly after release.