News for hackers. Stuff that matters.

A comment on Android Orphans: Visualizing a Sad History of Support. Parent comment

Re:Android Orphans: Visualizing a Sad History of Support by ConstantineXVI on Thursday October 27, 2011 @10:45AM (#3163330)
Newer (late 2010+) phones have finally learned to start putting a reasonable amount of onboard NAND, so app storage isn't near the problem it used to be. The "disable" feature sounds like it also `chmod -x`'s the app in question so it can't start, not just hide away the icon.

The one bit I'm worried about is if carriers are going to be able to comment out the feature (and the data controls, which I'm far more concerned about getting removed)

[ Parent | on HN ]
Re:Android Orphans: Visualizing a Sad History of Support by mdwrigh2 on Thursday October 27, 2011 @04:26PM (#3165357)
I suspect they will not be able to remove the feature as long as it's an official Android phone. My initial guess is that this will be added to CTS, or at least the list of requirements for things that work on Android.
[ Parent | on HN ]
Re:Android Orphans: Visualizing a Sad History of Support by ConstantineXVI on Thursday October 27, 2011 @05:40PM (#3165705)
Thus far, Google has shown a remarkable lack of backbone when it comes to the carriers. They're free to kill/restrict tethering, block non-Market apps, disable SIP support, not to mention the non-removable bloatware situation that motivated the app-disable feature in the first place. I'm not yet convinced they're willing to say 'no' to the telcos.
[ Parent | on HN ]