carrier "subsidy" [LWN.net]

carrier "subsidy"

Posted Jan 30, 2014 1:51 UTC (Thu) by dlang (guest, #313)
In reply to: carrier "subsidy" by Del-
Parent article: Stallman on GCC, LLVM, and copyleft

I think we are using similar terms.

I'm saying that unless you do a tivo-type lockdown of the phone, your other bundled apps won't matter (if you decide to cripple the kernel that may be harder to fix)

If users can install their own stuff without a tivo type lockdown, then they can and will override whatever lockdown your bundled apps try to force.

to post comments

carrier "subsidy"

Posted Jan 30, 2014 8:05 UTC (Thu) by Del- (guest, #72641) [Link] (4 responses)

> I'm saying that unless you do a tivo-type lockdown of the phone, your other bundled apps won't matter

I believe we disagree here. I believe very few people will alter the OS image shipped with a smartphone, even with access to all source code. Therefore, I believe simply disabling stuff in the shipping image is sufficient to block most customers from tethering.

> If users can install their own stuff without a tivo type lockdown, then they can and will override whatever lockdown your bundled apps try to force.

As I said, people do this to iphones today, so even with a tivo type lockdown they can and will override. For a company (be it vendor or carrier), I believe the real issue is how many would do it given a certain level of inconvenience.

carrier "subsidy"

Posted Jan 30, 2014 10:20 UTC (Thu) by dlang (guest, #313) [Link] (3 responses)

it's funny that you use the iphone, because that is an example of a tivo type locked down device.

carrier "subsidy"

Posted Jan 30, 2014 14:43 UTC (Thu) by Del- (guest, #72641) [Link] (2 responses)

> it's funny that you use the iphone, because that is an example of a tivo type locked down device.

Of course, that was why I used it as example. It is an example showing that in practise it is often impossible to lock down the device. Hence for any practical concerns whether you lock it down Tivo style or just make it inconvenient for the consumer to use it in unintended ways (like removing the tethering possibility from the system, requiring somebody to patch system internals to enable it again), can amount to the same end result for the vendor. They get their money, and they get fine grained control on what functionality the user has access to.

I have one very real life example of how ridiculous the Tivo stuff can be. As already mentioned HTC actually provides tools to unlock their devices, so you could say that those devices are not locked, but there is a level of inconvenience if you want to swap out the image it came with from the carrier. Now my daughter got a HTC Desire, and I wanted to flash a newer version of Android on it because HTC stopped providing newer versions of Android for it. I would say this is a prime example of what we are talking about here. I knew HTC provided tools, went over there downloaded the tools and started looking for documentation. I found the whole thing quite confusing, especially since it seemed geared towards windows users, and I only had linux. I ended up just deleting all of it, headed over to CyanogenMod and used their un-official tools to unlock the boot-loader, just as I did for my Tivotized Galaxy S2 earlier. You see, whether the device is Tivotized or not doesn't necessarily amount to much. Most funny part of the story? When I finally got the boot-loader unlocked, my daughter didn't want me to flash the device anyway. I usually follow the nerd slogan "if it works, fix it!", that may have something to do with it. I didn't even succeed in making my own daughter take advantage of the possibilities provided by an open device, simply because she did not trust anything but the official image from the carrier.

Moral of the story? Tivotization is plain stupid when it comes to consumers. I see no benefits for anybody. Even worse, as long as there is no software license pushing it away, I am afraid the madness will just continue for decades.

carrier "subsidy"

Posted Jan 31, 2014 0:04 UTC (Fri) by dlang (guest, #313) [Link]

I have several tivos that have been hacked for a _long_ time.

I am very aware that it's impossible to stop someone who's really determined.

However, lawsuits (or threats of lawsuits) against manufacturers are frequently based on how easy they make it to get at the data

and with the DMCA making it illegal to bypass even the most inept protections, there really is a point to them from a legal point of view.

Do not get me wrong, I think that these sorts of lockdowns, along with DRM are bad for customers, they don't stop the real bad guys and hurt legitimate users.

carrier "subsidy"

Posted Feb 3, 2014 11:34 UTC (Mon) by nye (guest, #51576) [Link]

>When I finally got the boot-loader unlocked, my daughter didn't want me to flash the device anyway. I usually follow the nerd slogan "if it works, fix it!", that may have something to do with it. I didn't even succeed in making my own daughter take advantage of the possibilities provided by an open device, simply because she did not trust anything but the official image from the carrier.

To be fair, HTC's version of Android 2.2 is far better than any stock Android I've ever used. Compared to the 4.x on my N7, it's faster, slimmer, easier to use, and less buggy. Plus all the features added in later versions are either completely worthless to me, or outright antifeatures.

Also, reflashing always comes with some degree of risk, especially if you hope to do so without resetting the device to factory defaults. Case in point: an OTA update to the aforementioned N7 a couple of months back rendered it unbootable, and I've not yet found the time to work out how to fix it without wiping it completely.

If you actually want to *use* a device for its intended purpose, rather than just having it as a toy, it's perfectly reasonable to want to keep to the path.