and still
HTC drags its heels.
Samsung has posted the source code for its Ice Cream Sandwich, Android version 4 for the Galaxy SII, opening the way for hackers to create their own Android spin. The release follows three iterations of Gingerbread (the last incarnation of Android v2) which are also available from Samsung in all their open-source glory, and …
True Samsung have the one top of the range phone while HTC appear to churn them out. When they do release an update it always takes ages to reach the UK. It's even worse if you have a branded handset, one reason I now buy the phone outright.
There's so many variation of android on so many different types of phone. It seriously makes me yearn for an iPhone, well for about a second or so, one operating system, on phone and it tends to work without complaint....mostly.
The only way to update a Galaxy S (yes, I know, 18 months old, get with the project, gramps) is to use the truly execrable Kies software. I have now tried it on five physical machines and one virtual machine and the most I have ever managed (twice, different machines) is for the phone to be recognized for ten seconds or so.
I'm not alone, according to Mr Google's helpful search engine, not alone by a loooooooooooooong chalk.
All parts of Samsung Kies should be removed, formatted, wiped out of memory - both your computer and yours. It's rare that I come across software that's so gob-smackingly awful that you're left in a gibbering state wondering just what the **** were the developers thinking?
My specific problem with the phone comms (and not alone in this) was that Kies recognised the phone when the device was in USB mass storage mode. Switch the device into Kies mode and Kies just refused to recognise that it exists.
Solution? Use some of the rather good 3rd party tools to update the device. Google for ODIN and you should find some good guides and links.
Depends what part of Samsungs direction you want to follow...
Being fined by the Korean FTC for price fixing
Being fined by the Korean FTC for obstructing the price fixing investigation
Being investigated by the EU for anticompetitive use of patents
A lot of companies would be a lot better off not following Samsungs methods at all.
Readers must remember that Samsung, like most Android deployers, has in fact been in *license violation* for the entire period between distribution of handsets running ICS and their current code dump. Although the userspace of such phones is composed of BSD and Apache licensed code which does not require source distribution, the critical part as far as getting actual hardware to run is the modified Linux kernel -- and that is licensed under the GPLv2 license.
That license contains a "Liberty or Death" clause -- if a company violates the license by distributing a binary without an active offer to provide the source code -- from the very beginning -- then it loses its right to distribute *permanently* the software without forgiveness from the rightsholders.
No one has yet enjoined one of the Android distributors for engaging in this widespread and flagrant licensing violation, but I hope that it happens at some point. License compliance is not something "optional", or to be done when "convenient" -- it is part and parcel of using the code to build a product.
And this includes the distribution of binary modules to speak to the hardware on essentially every phone. Most who have made a study of the legal requirements of the GPLv2 that all software linking against internal symbols of the kernel (as opposed to standard system call interfaces) must also be provided in source code have agreed that the increasing use of unpublished binary kernel modules to speak to hardware is in direct violation of the GPLv2 license. Samsung should be ashamed for not publishing full sources of the modules used to communicate with the GPS, data connection, voice, and wireless hardware. But it's not just shame -- it is a direct legal violation of the license.
io_uring
is getting more capable, and PREEMPT_RT is going mainstream