"We'll happily put that down to the presence of Android 4.2.2 which remains, I feel, a mixed bag because its mixed user interface metaphors offer plenty of chances for early user confusion."
Care to elaborate?
Samsung's Galaxy S4 is as wonderfully polished as you would expect from the Korean manufacturer's latest flagship, but the software the company says turns it into a “life companion” will be an acquired taste for many. Samsung yesterday officially launched the S4 for Australians at a lavish event staged at Sydney's Opera House …
Sure. I personally find Android's mix of Apps and Widgets, combined with customisations from manufacturers, means I need to spend a good 15 minutes customising Android handsets so the interface is to my liking. And my liking is for a very consistent and clean experience.
That's NOT me saying everything should behave like iOS. Rather it's a statement that I feel Android is a little untidy and inconsistent.
15 minutes? I fail to see how this is an issue... If you'd said a day, then I'd agree.
Personally, the ability to customise it massively outweighs the time to do so.
On the very rare occasions when I do a full wipe, it takes longer for my installed apps to redownload (automatically, though) than it does for me to customise the home screens.
Also, on the discussion of lag, I can't help but feel that this is Samsung's issue more than Android itself. I have the original Sensation running a kang of CM 10.1 (Albinoman887, for those that are interested) and don't have any issues with lag.
(Isn't it time for a Google/Android icon?)
The price of flexibility... and let's be fair, 15 minutes spent customising on the first time out of the box is pretty small potatoes - imagine how long you spend installing and customising all the applications and settings with a new, fresh-out-of-the-box PC.
I guess the initial setup is geared towards what the average person is most likely to want - we in the tech game are a bit more demanding :)
Pint - to look forward to once the setup is complete and I can relax in the knowledge of a job well done.
>Does it have rSAP?
http://www.android-rsap.com/compatibility.html would suggest that it does. Curiously, my uber-geek mate (the sort who always sticks his previous gen Samsung Galaxy on eBay a day before the official announcement of the next model) drives a recent Audi, and he likes the integration. A nice car, but he only discovered that he has to put anti-feeeze in his windscreen in winter when he crashed into a parked car a few months back... a selectively-smart chap.
AIUI it's got a IR trasmitter on it.
Next step would be a 433MHz transmitter for various RF remotes and DECT for when the phone is at home.
(My DSL router-cum-PBX - a Fritzbox - is a Dect base station with an app to treat wifi-based smartphones as internal extensions when they're in the house, but wifi range is a bit "lacking")
I rather agree it's a shame about the Oct core version not being available in the UK and other territories. The premise of a low power chip performing the humble tasks, that kicks in the hight power chip as necessary, seems a sensible and battery saving measure ( though I don't really see why the low power chip required 4 cores).
My understanding is the the Octa chip isn't in various territories because they couldn't make it work with 4G (which is present or rolling out in those territories). Can't think why given they'd have designed the chip in full knowledge of the time-scales and technical challenges of 4G, but there you go.
Apparently 70% of UK chips will be snapdragon and the rest Octa so it may be that they sell those via networks that won't make use of 4g for the next couple of years. Apologies if any of the info in this is inaccurate - it's just what I gathered after researching the same question when they did the NY launch.
This post has been deleted by its author
I've been stung by the poor software on HTC handsets, so this time I'm going where the action is. I have never used a S3, so all the reviews that directly compare the two are a bit pointless to me. This handset will be bang up to date for ages (Sensation XE was superseded within a month of ownership) and has enough of a balance of gimmicks and power to keep my interest. So what if S-translate is muck? Sat nav on the 5" screen will make up for that for me personally.
Swings and roundabouts, this one being more swings...
Yawn...Samsung would never now accept a maps application that points you in the wrong direction, has places in the wrong place, has imagery that looks like it was printed on jelly then dropped on the kitchen floor, has an antennae that has to be held a certain way to get it to work, has a UI where some apps have to have black bars down the side, has a primary desktop that is nothing more than rows of icons, etc etc.
Every phone has it's faults. The iPhone's are just more serious and actually affect real-world use.
You phrased that incorrectly, Samsung is outselling Apple, it just so happens that Samsung's flagship OS is Android.
Android as an OS was well on it's way to market saturation before Samsung kicked up a gear due to the amount of manufacturers selling various amounts of handsets at different price points, that was always the key ingredient to it's market share success. Samsung has just helped hammer that last nail in Apple's coffin (unless they start doing some amazing innovation with their handsets that helps them claw back some market share).
....but the software........will be an acquired taste for many.
Look, it's very simple. Make the bloody thing and put on the OS and hardware-specific apps required to make the whole device work (camera etc). Add your cruft as ordinary user apps that can be removed / replaced / whatever. Host same pointless cruftapps on the app storeplay skool, limited to users of your device, for updates (as you already do) and just in case anyone who dumped 'em wants 'em back.
Easier to do, makes your OS update process quicker / cheaper / simpler and avoids pissing off that large chunk of your user base who hate the added crapware. Get it right.
Those who buy the thing because your FaceTwitWank app is better than others' offerings will still do so and you may just sell a few more to those who want it for its capabilities.
Don't take this personally Samsung, I'm looking at everyone here.
@TeeCee that is the perfect solution. Honestly I read this review thinking that it's a shame that I just won't even consider what is obviously a nice bit of tin because of the Samsung crapware that gets loaded on (and I can't be doing with the faff of rooting and applying custom roms). I hope someone in Samsung is getting this feedback - "Wake up! You are actually losing customers because of this"!
>It's the audio latency that needs improving, they are far from laggy.
That's something Google stated they were concentrating on in Jelly Bean- I'll give it ago when the update drops for my handset this month. Previously, people who have wanted to use their phone or tablet as DAW control surfaces have gone iOS. A real Korg Kaoscilator is a fun toy, but too pricey to justify to myself!
"One reason is weak integration with social networks: the photo app doesn't offer a share to Twitter or share to Facebook option until those apps are installed."
As far as I'm concerned that's the app done right, and isn't a Samsung failing. The 'Share' function is part of Android, and relies on apps telling it you can share via them - meaning you can't share via an app that isn't installed.
Much better than baking in sharing options that may/will stop working when the social network either changes it's API or disappears.
If you are going to review a phone, at least understand why it does things, and who is responsible.
P.S If i'm talking rubbish, happy to be corrected
No that is completely correct.
I was rather confused by the author's statement when he mentioned that. I mean why should the device have to have links to twitter and facebook clogging up the share menu if you don't use them?
Add in Instagram, Myspace, G+, Digg, Pintrest, etc then you're going to have a whole lot of shares for apps you don't use.
It's far better to share with apps that have been chosen by the user. I get a feeling it is perhaps the author having had an IPhone before (assumption?) and having to have all links between apps and shares preset. Android uses intents to link apps and data between each other seamlessly.
Indeed, the intents system (of which Share is one of a unlimited amount of intents) is what makes Android light years ahead of iOS.
In laymens terms:
All applications are sandboxed by way of unix style user accounts. No application can talk to any other application full stop, nor can it talk to the outside world unless it has permission (granted on installed).
To share data with other apps, you use intents, which are a public interface for passing data. It's a very simple, but ingenuous solution, and provides unlimited flexibility, and only available on Android.
You want to write your own mapping application? Sure you implement the Navigate intent, and when your app is installed, and something tries to navigate somewhere, your app will be listed as a receiver of the navigate intent (along with Google Maps and any other application that implements the navigate intent).
Android has a massive list of built in intents, and there is a list of 3rd party ones here, if you want to implement communications with another 3rd party app.
http://www.openintents.org
The other good thing about using intents is that you can easily change your default app.
Using the Maps example a user, when clicking in an app or a hyperlink that might open up in Google Maps can choose to either make a totally different app the default for that action or always have a choice menu come up to choose each time.
If Google screwed their Maps app up you could just choose another and set that as the default opener for that intent.
It's not complex either, when you click on an action (such as choosing Navigate here from a Qype app) it will present you a list of everything that can perform the task with the option to choose "Just Once" or "Always".
I just wish they had stuck to the old (pre-jelly bean) system of always choosing just once unless you also ticked the checkbox to make default. As I use "just once" for a lot of intents it means I always have to have an extra click.
@Ben 47 I was just spitting out my tea while eyeballing that same line. The reporter has the smell of an iPhone owner/ignoramus(any difference?). Weak integration is more like sophisticated functionality but I guess you have to be of a certain level of intellect to recognise and attribute these things. I would waffle on but I have tea to clean off my keyboard.
Agreed, if anything the opposite is a criticism of the fruity phone - "share via Facebook" is a kludge to try and pretend there's social network integration. What you'll find is that the iPhone has a "share via FB" option, regardles of whether you have a FB account tied to the phone - so unnecessary clutter.
Even worse, you can have the FB app installed, but you need to link the account through the phone's settings too. So clicking the "share via FB" options prompts the error message "no FB account associated" instead of doing what you'd think would be the sensible option of passing through to the FB app.