<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Update on Tony Andrew Meyer</title><link>http://tonyandrewmeyer.com/tags/update/</link><description>Recent content in Update on Tony Andrew Meyer</description><generator>Hugo</generator><language>en-nz</language><lastBuildDate>Mon, 05 Jul 2010 17:51:37 +1200</lastBuildDate><atom:link href="http://tonyandrewmeyer.com/tags/update/index.xml" rel="self" type="application/rss+xml"/><item><title>Latest MySky (HDi) update</title><link>http://tonyandrewmeyer.com/2010/07/05/latest-mysky-hdi-update/</link><pubDate>Mon, 05 Jul 2010 17:51:37 +1200</pubDate><guid>http://tonyandrewmeyer.com/2010/07/05/latest-mysky-hdi-update/</guid><description>&lt;p>The latest (and heavily publicised) &lt;a href="http://skytv.co.nz">MySKY&lt;/a> (HDi only?) update was released today.  Oddly, our update was applied around 2 p.m. - the currently showing program was replaced by a very ugly notice that the system was being updated.  I can&amp;rsquo;t understand why the update wasn&amp;rsquo;t deployed during the night (e.g. 4 a.m.), when the number of viewers must be significantly lower.  What if I had really cared about the program that was showing?
My initial reaction was &lt;strong>very&lt;/strong> negative.  After it was pointed out (via &lt;a href="http://twitter.com/skynz">Twitter&lt;/a>) that many of SkyTV&amp;rsquo;s mistakes are correctable via new options in the settings back, I&amp;rsquo;m slightly less negative, but it&amp;rsquo;s still not an improvement.  This is especially frustrating considering that the UI is so terrible, and has been ever since MySKY was introduced about five years ago (I&amp;rsquo;ve had MySKY since just after the launch).  Being told that they know about the many problems and fixing them isn&amp;rsquo;t possible until the hardware is revved doesn&amp;rsquo;t inspire any confidence at all, since the problems existed with the original MySKY and certainly were not fixed when the hardware &lt;strong>was&lt;/strong> revved (with HDi).  Someone at SkyTV is responsible for selecting the hardware - if the platform doesn&amp;rsquo;t support creating a decent UI, then they should choose something else.
(Has anyone on the MySKY team used an Apple product?  Or even Windows 7 or a Zune product?  Would they recognise good UI when they saw it?  Do they have anyone that has any UI talent or experience?  If so, perhaps they could give that person a bit of power to fix things?)
The &amp;ldquo;what&amp;rsquo;s new&amp;rdquo; page has a &lt;a href="http://www.skytv.co.nz/Default.aspx?tabid=1356">feedback form&lt;/a> where you can comment on the recent changes.  I encourage you to do so.  My comments were:&lt;/p></description></item><item><title>My 2GB, 4 day 0.0.1 iPhone update</title><link>http://tonyandrewmeyer.com/2009/08/03/my-2gb-4-day-0-0-1-iphone-update/</link><pubDate>Mon, 03 Aug 2009 11:24:26 +1200</pubDate><guid>http://tonyandrewmeyer.com/2009/08/03/my-2gb-4-day-0-0-1-iphone-update/</guid><description>&lt;p>A few days ago, &lt;a href="http://apple.com">Apple&lt;/a> released version &lt;a href="http://support.apple.com/kb/HT3754">3.0.1&lt;/a> of the iPhone OS, which addressed a pretty major SMS vulnerability.  When Olyvia tried updating her 3GS to 3.0.1, something went wrong.  The iPhone entered &amp;ldquo;Recovery Mode&amp;rdquo;, which means that it displays an image indicating that you need to connect it to iTunes, and you can&amp;rsquo;t do anything else (no phone calls, no iPod, no applications - absolutely nothing).  Connecting the phone to iTunes prompted a message indicating that the phone needed to be recovered - doing so downloaded the 3.0.1 update, and then got stuck on the &amp;ldquo;Verifying Restore with Apple&amp;rdquo; step for a long time, until it would finally fail with error &amp;ldquo;3104&amp;rdquo;.  This process could then be repeated, with the same results.
What this meant in practice was that the phone was bricked as of last Friday.  &lt;strong>An update should never be able to brick a (legitimate, not jailbroken) phone!&lt;/strong> Even more, failing to verify a restore with Apple should never leave the phone in a broken state.
I tried many thing to resolve this:&lt;/p></description></item></channel></rss>