There has to be a better way!
Posted by: dayjay on 06 February 2014
After prevaricating for weeks I've finally bitten the bullet and updated my Qute 2 to the new firmware. Everything worked as it should but, for my first time, it was a right pain in the backside to do and a fairly stressful experience not least because of all the the posts of doom and gloom on here from some of those that went before me. I have lots of devices connected to the net and without exception, excluding the Naim of course, they all update over the net with very little fuss. Why is it so much more complex and stressful with Naim kit?
It could be like Apple - https://forums.naimaudio.com/to...program-missing-help
Not for me because I wouldn't use the their products with the exception of my company Ipad! Puts things into context as that sounds bad
Totally. PCs have never suffered an update issue ever, those bastards at apple. grrr.
It could be like Apple - https://forums.naimaudio.com/to...program-missing-help
What a strange reply.
Are you really suggesting that the Naim update process is ok because Apple had problems
Are you really suggesting that the Naim update process is OK because Apple had problems?
Apparently, to you, yes.
However, it was my intention to point out that if the OP wants Naim to change from their current update process
( "worked as it should but, for my first time, it was a right pain in the backside to do and a fairly stressful experience not least because of all the the posts of doom and gloom on here from some of those that went before me." )
to something more like that of Apple
( "I had the same problem last weekend with the latest iTunes update. After giving-in and contacting Apple the solution is to uninstall every Apple app and associated programs so you can do a clean install of the latest version." )
then he should be aware that the other update techniques can throw up their own problems.
In addition - it is usually the problem updates that get reported. This is a Naim forum so there will be a focus on Naim issues - and problems.Even here the recent Apple Itunes update found several failed 1st attempts here. Luckily - there were more out on the internet with suggestions of, involved, solutions.
It seems that recently Naim's update is more capable of recovering from halts and hiccups than in the early days. If this IS the case then "the posts of doom and gloom" may cause unnecessary concern to current updaters.
As 'garyi' uncharacteristically points out - PC updates can also go wrong.
That said - it does seem sensible that an internet-connected device should integrate its update processes wherever possible.
I am very happy to now have an Apple free environment
But the OPs point about fuss free updates is a good one.
In terms of quality of updates, anyone arguing that Naim has Apple beat should look no farther than the Naim Servers 1.6H Update.
To be fair, Naim has seen steady progress and should be commended for their efforts, but more can and should be expected.
An Apple user since the 80s I can't remember ever having an update issue since leaving MacOS behind. Flash updates for Netgear routers - certainly but Apple devices and computers not at all.
The current update process for Mavericks seems very intuitive.
Tog
In terms of quality of updates, anyone arguing that Naim has Apple beat should look no farther than the Naim Servers 1.6H Update.
To be fair, Naim has seen steady progress and should be commended for their efforts, but more can and should be expected.
In order to add (remote) on-device updates (in general), one requires an update server (in the cloud), an update daemon (with persistent internet access) on the device itself, as well as reserved space on the device to accommodate the update payload. Authentication is also a good idea.
That said, this is not always as easy as it seems, especially if a (range of) legacy device(s) require(s) a bootloader change (not always trivial, with the potential for failure), or a modification to hardware (much more complicated)–given this, a manufacturer might choose instead to support the existing (in this case, serial + local network daemon) update method long after cloud updates for newer devices become available [or make the decision to discontinue support for older devices altogether].