Samsung all but guarantees no one will update to Android 4.0
geek.com
geek.com
My main issue is I have yet to get the OSX version of Kies to work on my MBP running Snow Leopard (not sure the OS matters, but maybe it does). When I open Kies, it tells me there's an update to the software (and I agree with the article here - wtf Samsung? Put the new version on the site). Now this update will download, then ask me for my password, but after that it just hangs. It takes up 100% of the CPU and does nothing. Canceling causes Kies to restart, but no indication that the update actually took place. Then plugging my phone in it says my phone cannot be upgraded. Now I'm stuck waiting until I have access to a Windows machine to try my luck there.
If AT&T doesn't want to give mobile bandwidth away for OS updates, they should have Samsung change AT&T branded devices to only allow OTA on WiFi.
Hardware manufacturers are the WORST software makers.
Except for Apple.
This is the main problem. Connecting via cable to a computer is easy enough, but Kies is a piece of garbage. Often it fails to recognize different devices and it doesn't handle updates very smoothly in some cases.
Unfortunately, these 2.x -> ICS upgrades on Galaxy SII devices requires a firmware update, which means you have to use something like Odin and a manually downloaded firmware to to the process on your own, which is a nightmare for anyone who isn't really into ROMs.
My MacMini media machine at home is several releases behind current Lion releases because its screen is only visible when I want to watch a movie, and the rest of the time its playing music, controlled via the iTunes remote.
This should (hopefully) lead to demand for newer versions of Android to be released everywhere (or at least backported patches).
"anything but X" is the opposite. It means "absolutely not X".
The AT&T Note 4.0 upgrade is happening over Kies, a desktop piece of software not unlike iTunes. Fullstop. How that turned into the ridiculous title is rather bizarre.
I appreciate that the software may suck, but here's the thing: If you install it, update the droid and uninstall it cleanly you should be fine.
Protip: Do it from a VM if you can, then roll back/blat the VM.
I suspect the real reason is that it is harder to reflash an OS from inside, and a higher risk of getting stuck in some bad state. Not impossible of course, just not as simple as reflashing from outside.
The procedure used on at least some products was to download the new version alongside the existing software, verify it, configure it all and then set it to be the boot version only when the install is done - then it can reboot. Until that point it will still boot the original version. You could even have a 'boot this next time only' mode and then at the conclusion of a successful boot it would set it to be the default and in the event of failure would go back to the previous version.
There probably are bad cases if the power is lost at the very end but the window is quite small and you are probably safer with the phone having its own battery (don't start installing unless there is enough charge) than you are with products like TVs. I know at least one TV manufacturer used such an approach and it seems a reasonable approach for reduced risk.