Quote:
Originally Posted by Dazrin
I think Verizon's Galaxy S3 had (has?) a locked bootloader even though the other flavors of GS3 didn't, so that might be the issue. Also, Samsung (and to be fair, almost everyone else) always put their own UI on their phones instead of plain Android, which is a big issue for some (e.g., the Samsung remote wipe issue a couple weeks ago.) The Nexus branded phones get stock Android and don't have the extra, uninstallable without rooting apps that most phones have. I have a Galaxy S/Captivate, it works ok, but it definitely needed Cyanogen to get to where I am happy with it.
|
Oh yeah. Wife just got a Galaxy S 3 last night, and while it is a really nice phone, the UI sucks. For instance the app drawer button, is off to the side, instead of bottom center like on every other android phone. the notification drawer has power controls, but they're set to take up half the screen. Just silly stupid stuff.
Quote:
Originally Posted by Prestidigitweeze
I'm not certain I follow you. The Samsung smartphones I've owned have all allowed third-party ROMs after rooting. It's no coincidence the company hired Steve Kondick of Cyanogen based on the third-party ROMs he'd created for various Galaxy and pre-Galaxy devices.
|
It is more of an issue with the non GSM carriers. For instance, the Galaxy S II does not have much in the way of third party support due to the lack of availability for drivers for the wireless for Sprint. You could get a ROM built for it, if you really didn't want 3G or WiMax.