New Year's hangover for Zune users
A leap-year issue with Microsoft's Zune music player is still leaving many users cold, despite the company's reassurance that all would be well by sometime on New Year's Day.
Postings on Zune message boards Thursday morning, as people tried out Microsoft's recommendations and fellow Zune users' suggestions, ranged from the hopeful...
"The wipe process should only take a minute or two. If it is hanging on this screen, disconnect it from power, let the battery drain, and then reconnect it to start the device again," user Raw Deluxe wrote on Zune Forums.
...to the melancholy:
"Mine never made it back. The battery drained ok, but it tried to start one time and is now good and dead. I talked to support and they agreed - its a brick," wrote brotherdiesel.
Scores of Zune users on Wednesday -- the last day of a 366-day leap year -- reported that their 30GB Zune devices were freezing up. Complaints rippled across message boards as people booted up the gadgets and found they could not get to their songs or pictures.
By the middle of the day, Microsoft had identified the root of the problem: the Zune's internal clock was stumbling as it tried to handle a leap year. (See Microsoft's Zune support site for more details.) Things would start to resolve themselves, the company said in its Zune 30 FAQ, by noon GMT (4 a.m. PT), and it advised users with frozen Zunes to follow these steps:
1. Disconnect your Zune from USB and AC power sources.
2. Because the player is frozen, its battery will drain--this is good. Wait until the battery is empty and the screen goes black. If the battery was fully charged, this might take a couple of hours.
3. Wait until after noon GMT on January 1, 2009 (that's 7 a.m. Eastern or 4 a.m. Pacific time).
4. Connect your Zune to either a USB port on the back or your computer or to AC power using the Zune AC Adapter and let it charge.
One ZuneBoards forum user claimed to have identified the actual trouble spot in the clock driver code. (A tip of the hat to Ars Technica for spotting the post.)
"The Zune's real-time clock stores the time in terms of days and seconds since January 1st, 1980," wrote user itsnotabigtruck. "The Zune frontend first accesses the clock toward the end of the boot sequence. Doing this triggers the code that reads the clock and converts it to a date and time." The post continues:
Under normal circumstances, this works just fine. The function keeps subtracting either 365 or 366 until it gets down to less than a year's worth of days, which it then turns into the month and day of month. Thing is, in the case of the last day of a leap year, it keeps going until it hits 366. Thanks to the if (days > 366), it stops subtracting anything if the loop happens to be on a leap year. But 366 is too large to break out of the main loop, meaning that the Zune keeps looping forever and doesn't do anything else.
For those who hadn't yet run into problems, Microsoft said to refrain from connecting the Zune to a PC before noon GMT on Thursday.
To disconnect the battery, or not to disconnect the battery
Microsoft strongly advised users to ignore advice from forum visitors who suggested disconnecting the Zune's battery to reset the device:
This is a bad idea and we do not recommend opening your Zune by yourself (for one thing, doing so will void your warranty). However, if you've already opened it, do one of the following:
Wait 24 hours from the time that you reset the Zune and then sync with your computer to refresh the usage rights; or
Delete the player's content using the Zune software (go to Settings, Device, Sync Options, Erase All Content), then re-sync it from your collection.
Judging from forum comments Thursday morning, however, a number of users had indeed disconnected the battery.
"I got tired of waiting.....opened it up and did a hard reset. Seems that 'triggered' it cause now its telling me to connect it to my PC and then open the Zune software and restore the firmware. It seems to be seeing it.....hopefully all is on the road to recovery," wrote floozuki.
By midday Pacific Time on Thursday, some users found life returning to normal for their Zunes: "Mine came back today just as advertised.... all songs intact...no worries.....," wrote DadGuy, though it wasn't clear which recovery method he had followed.
But others griped that the New Year's freeze was just the latest in a series of problems they'd been facing. Said emilysuz:
I tried the button combo, it's currently stuck on 'Connect Zune to your PC' but it is currently plugged in to my PC. I have had trouble with this thing fopr days, before the widespread crash and I'm beginning to think this thing is just your garden variety piece of crap. I loved my Zune until the battery wouldn't charge. Maybe my Zune troiuble is not the same. It refuses to charge, it only charges long enough to tell me my battery is low and then it dies again, even if it's plugged up. It won't sync, wired or wireless. Again, I love my Zune, but if it's dead it's no good to me.
User JediFarfy sought to mollify emilysuz about the Zune's failure to sync:
Mine wouldn't at first, so I kept disconnecting it and reconnecting it on both ends (comp and Zune). Took about 4 times and it finally connected. Your Zune had a rough, confusing day, give it some love and it'll be fine.
See also:
I want to believe: Reflections on my Zune year
The new Zunes in action
Jonathan Skillings is managing editor of CNET News, based in the Boston bureau. He's been with CNET since 2000, after a decade in tech journalism at the IDG News Service, PC Week, and an AS/400 magazine. He's also been a soldier and a schoolteacher. E-mail Jon. 


The problem is self resolving with the date change. If you are going to attack a company for oversite, be sure to be fair and credit them when the issue is resolved using the advice they gave as well. It is unfair for you to attempt to blame the company for this issue when the issue is already being resolved and not acknowledging that fact.
In addition, my 3rd gen Nano is still bricked due to the unit crashing and Apple is unwilling to do anything about it other than tell me to buy a new one. I don't find that to be 'funny' at all, regardless how much you are laughing.
The Zune bricking issue is being fixed. My dead bricked Nano is not. That's the plain and simple truth of the matter. It does not matter how much spin you wish to put on it, it doesn't hide the truth.
You couldn't be more wrong Blu-meanie, it's the Apple ear buds that sound like trash (and they hurt my ears), however, iPods sound incredible when you use quality ear gear like my V-moda Vibes or Sony MDR-710s.
"It is unfair for you to attempt to blame the company for this issue when the issue is already being resolved and not acknowledging that fact."
The issue is not resolved - it was just put off. What's to acknowledge - that MSFT's big fix was to do not much of anything?
"In addition, my 3rd gen Nano is still bricked due to the unit crashing..."
You are one anomaly of how many millions of people whose last-gen 4GB iPod Nanos are working just fine? Meanwhile, the Zunes bricking-out are not an anomaly - they dropped like flies. Therein lies the rub - break-downs due to statistical anomalies vs. breakdowns due to statistical near-certainties. Which would you want to buy into?
Besides, where's the subscription service for Apple? That, by itself, makes all iPods a non-starter for me.
For the record: Two 30-GB Zunes, both now working. One reset itself after the battery died out. The other one would not, so we disconnected the battery, then reconnected and all is now fine. I think my son was a bit hasty trying to get his back up.
--mark d.
Incidentally, how's MobileMe these days?
anyone out there with a zune successfully boot it while charging with a computer usb port?
thank goodness they don't design NASA tools.
"NASA has released new information about the shuttle Columbia disaster nearly six years ago. All seven astronauts were killed when Columbia broke apart upon re-entry over Texas in 2003. in a 400-page report, NASA says the seat restraints, suits and helmets did not work well...."
http://www.msnbc.msn.com/id/28436908/
The good news? NASA was able to compile a report and release it within a mere 6 years.
Don't dare start blaming the DoD, who insisted upon certain design decisions along with Rockwell and other firms. Obviously, it must all be completely NASA's fault.
The sequence events *should* read:
1. Disconnect Zune from USB and AC power sources.
2. Wait until the battery is empty and the screen goes black.
3. Purchase iPod or other media player not manufactured by Microsoft.
4. Recycle Zune in ecologically responsible manner.
Hope this helps.
Whoooooaaa Haaaaa Haaaaaa
Heeeee Heeeeee (cough cough)
Repeat
you left out the part where you return ipod for a zune because of the ipods inferior sound quality.
@ terminalblue
I've listened to a Zune and an iPod side by side, and I can tell you they're just about the same. I love my Nano for it's sleek design, great sound quality, and the ground breaking innovation of actually turning on when I want to listen to music.
Granted, I did go out and buy a Touch, so they did get $500 (July prices) out of me instead of repairing the existing unit, but I still have the Nano and would like to get it working again.
Think different, think sh*t-brown ;-)
My Zune was a different story. It had apparently been running through the night, and the battery was already mostly depleted. The battery disconnect did not work, nor would the battery charge. She swapped her Zune battery in place of mine just long enough to allow my Zune to restart, then put the original battery back in. My zune is working again. This may be the way to "unbrick" a Zune.
1. The click wheel is having issues with recognition.
2. The menu screen lags.
3. The lack of customization.
And, I don't know about you, but I certainly don't go around saying this:
**** The Dark Knight would have been sooooo much better if only it had a couple of more pixel's to make it look sharper!!!
And buying a product shouldn't be about whether it has 2% or 98% of the market share; it should be about quality.
This is something that sadly, many people have lost sight of. Including you.
This is the world's largest software company !
Microsoft able to turn your 2009 speed demon quad core server into a PDA with one software installation.
Microsoft is to software like KFC is to chicken
> FINGER -l chicken @kfc.com
If it weren't for all the software bugs my company deals with (homegrown apps, vendor apps, microsoft, and apple), I wouldn't have a job.
Have you taken a look at the .NET framework? If you don't know what it is, you are not qualified to make a statement that bold. Microsoft has its problems, but employing competent programmers is not one of them.
and no i don't own a zune. I'm an ipod owner.
iPods can and do last - my friend, after five years, just replaced her iPod mini.
How can you get a zune for $400 cheaper than the ipod when the most expensive ipod costs $399 (btw thats the ipod touch 32) Did microsoft give you a zune then pay you to use it?
random truth: He could have gotten it before the Touch's price was brought down.
Apple has always been very restrictive with what you can do with their products which is why I'd never own one. I've tried itunes and I surely wouldn't want that POS on my computer. I'm happy to copy mp3s right to my device how I want to, not how I'm forced to.
Ohhh the ironing
"I don't know anyone that as older ipods because they just don't last."
iPods can and do last - my friend, after five years, just replaced her iPod mini.
sadly, my iPod Classic is having functionality issues only a year after I bought it.
- by mikehill33 January 1, 2009 3:29 PM PST
- so glad I junked my Zine months ago. Poor engineering re-affirms the **** poor experience of the Zune.
- Like this Reply to this comment
-
-
- by xxenclavexx January 2, 2009 11:45 AM PST
- engineering, or a source code error? Nothing is physically wrong with the product
- Like this
-
- by mbenedict January 2, 2009 12:31 PM PST
- @xxenclavexx:
- Like this
-
Showing 1 of 3 pages (113 Comments)It was a source code error... not even Microsoft's error but an error in the driver code supplied by the real-time clock's manufacturer (Freescale, which I believe was still owned by Motorola at the time the code was written years ago.)