5 ms·

I've never understood this ridiculous "it's the carriers" argument. Apple doesn't have a problem with releasing timely updates. So how come the Android OEMs ca

I've never understood this ridiculous "it's the carriers" argument. Apple doesn't have a problem with releasing timely updates. So how come the Android OEMs can't ?

drivebyacct2 14y ago
Have you read any of the posts up to the point in the thread? They don't want to. They have no incentive to. The carriers regularly drag their feet on updates, even after the manufacturers released them. Apple had the great thought to tell Verizon to, kindly, shove off, and they handle them by themselves. They manage the hardware, and every layer of the OS. That's not true of any Android phone, and the current situation is a result of that reality.
cookiecaper 14y ago
>Apple doesn't have a problem with releasing timely updates. So how come the Android OEMs can't ? Because Android doesn't have the same ridiculous cult around it that Apple does. The iPhone made enough money to make carriers beg Apple to let them carry their phone -- more often it's the other way around, which is why bloatware and disabled features and all that other stuff infects every non-Apple phone. The demand for iPhone is astronomical, and that is the only reason Apple is in a position to instruct the carrier. If normal OEMs try this, the carrier will simply destock their items, remove the subsidy, and the OEM will never get any meaningful sales.
antihero 14y ago
Because they have literally hundreds of handsets to support, as opposed to about 4
mgkimsal 14y ago
I'm assuming some of it has to do with licensing agreements. My guess is carriers want to keep control of the code on the device because many preload their images with extra stuff ('crap' or 'value added service', ymmv). Sun/Oracle can put out timely JRE/JDK updates for Windows/Linux - why doesn't Apple? Similar situation, and one which I thought was incredibly stupid for Sun to get itself in to years ago. If Java is really that core to your business (changing stock symbol to JAVA even!), don't let a third party control the availability and release schedule of that software for some of your users. Sun did it with Apple/Java, and Google's going it with multiple manufacturers and Android.

I've never understood this ridiculous "it's the carriers" argument. Apple doesn't have a problem with releasing timely updates. So how come the Android OEMs can't ?

drivebyacct2 14y ago

Have you read any of the posts up to the point in the thread? They don't want to. They have no incentive to. The carriers regularly drag their feet on updates, even after the manufacturers released them. Apple had the great thought to tell Verizon to, kindly, shove off, and they handle them by themselves. They manage the hardware, and every layer of the OS. That's not true of any Android phone, and the current situation is a result of that reality.

cookiecaper 14y ago

>Apple doesn't have a problem with releasing timely updates. So how come the Android OEMs can't ? Because Android doesn't have the same ridiculous cult around it that Apple does. The iPhone made enough money to make carriers beg Apple to let them carry their phone -- more often it's the other way around, which is why bloatware and disabled features and all that other stuff infects every non-Apple phone. The demand for iPhone is astronomical, and that is the only reason Apple is in a position to instruct the carrier. If normal OEMs try this, the carrier will simply destock their items, remove the subsidy, and the OEM will never get any meaningful sales.

antihero 14y ago

Because they have literally hundreds of handsets to support, as opposed to about 4

mgkimsal 14y ago

I'm assuming some of it has to do with licensing agreements. My guess is carriers want to keep control of the code on the device because many preload their images with extra stuff ('crap' or 'value added service', ymmv). Sun/Oracle can put out timely JRE/JDK updates for Windows/Linux - why doesn't Apple? Similar situation, and one which I thought was incredibly stupid for Sun to get itself in to years ago. If Java is really that core to your business (changing stock symbol to JAVA even!), don't let a third party control the availability and release schedule of that software for some of your users. Sun did it with Apple/Java, and Google's going it with multiple manufacturers and Android.