4 ms·
Android architects should be able to make it easier for proprietary drivers to interoperate with future Android releases, by standardizing on interfaces. I thi
by jerrya 15y ago
Android architects should be able to make it easier for proprietary drivers to interoperate with future Android releases, by standardizing on interfaces.
I think though, that there has to be real push back against the rooting/warranty policies. If I take my car to an independent mechanic, it does not void the warranty. If I hire an HVAC contractor to fix my air conditioner, it does not void the warranty.
If Samsung, et. al., can point to legitimate ways in which a rooted/modded phone can break the phone irreparably, what that tells me is that's an indication of poor design on their part. As consumers we should expect they fix that, not make third party mods difficult.
- drivebyacct2 15y agoIt's not really about the architechure of Android so much as it is the bullshit, erm, unfortunate licensing that goes into the graphics drivers, RIL, etc. Even the 4.0.3 source drop for the Galaxy Nexus was awkward because half way through it Google had to stop and go get terms to release updates to the proprietary drivers for their own Nexus device. From my limited understanding, if you want to build a (not cheap, but... affordably, expensively cheap) phone today, there aren't exactly open-firmware hardware choices. The only way to physically damage the phone is to do some of the (inane) extreme overclocking. Not sure what they can do about that except do more at a hardware level to set caps on that sort of thing. I still suspect the reluctance for rooting/roming is from the carriers (tethering and support primarily). This seems to be backed up by the fact that at least one of Motorola's new phone has an unlocked bootloader everywhere except the United States.