Well, I'm going to agree with everyone who's said "get a new one", as mine (new on Monday 7th December, delivered from Mobilephonesdirect.co.uk) has been randomly rebooting all week and last night it made its terminal reboot - now I have a rather boring black Nokia paperweight! What's more irritating is that nobody at Nokia UK or MPD seems to work on the weekend so I've got to wait til Monday to sort out a replacement :-(

It is not only reboots that are random, seems like the rebooting units also are random, no particular batch or factory.

Mine arrived 9th December from MPD also developing random reboots fault, sent them e-mail in thursday, try to contact MPD, no response what so ever, only real people i talked on the other side of phone was staff from nokia retail who is not able to do anything like replacement without authorization from MPD, nokia retail assured me i will have e-mail back from MPD in Monday as they are so extremely busy. Hope will receive e-mail in Monday.

Nokia should state if this reboot issue is SW/driver issue or a (unsolvable) HW issue. So far they have been dodging the whole issue judging by the bug-tracker comments. Returning/replacing a device can be a PITA sometimes when ordering from the net.

Reboots on mine are getting more frequent, and it is well beyond usable. Since Nokia is unable to state what is wrong, or if it is fixable, I have to return mine as well. This is low end by Nokia.

Charging from USB cable, it is rock steady. Replaced batteries with one from a 5800 - no change (reboots every 10 min when used). Sitting on the table - can go for hours or days? without rebooting.

Why are you suffering, why not just take your device back and get a new one. Nokia can sort his out in the background, but you don't need to suffer. Most people do not have this problem.

Day 2 of using new (replaced n900). No reboot yet, even in multitask using, web, music, chess, sms. One fact that battery is more longer, i still have 60% on the 1st day. First n900 died in the end of 1st day.

You are missing the point. 10% have this problem, and it is completely random regarding batches and factories. If I get a new one, it is still a 10% chance it will be faulty. This problem is old by now, but Nokia have so far not done a single thing to solve it. They have made no statements whatsoever. When you purchase a device worth 600 Euro, you expect more than 90% chance it will be in working condition. If Nokia released a statement saying this will be fixed in the next FW release - no problem. If they released a statement saying they are removing the faulty sets off the marked - no problem. But they are doing no such thing.

Am I suffering - no, but I am annoyd at Nokia, they are not doing their job, I am in all respect doing it for them. It is as simple as that,

I understand that you are p****d, but here is what the Nokia Engineer has said as per bug report. There is only one specific use case that is likely to get fixed in the next firmware release (this might not be what you want to hear).

The inter-relationship between hardware and firmware is such that it is possible to fix it both in hardware and software in many cases. Right now there is a hardware fix for 32wd_to crashes, and that is to swap your device. The more devices that go back to Nokia the better chance they can sort this.

=================Nokia Engineer comments=============
This bug contains many different reboot issues.

One set of issues is system service crashes. These seems to be quite rare in
this bug though.

Another set is crashes when the device is heavily used. This could be memory
management related issue (e.g. between CPU, GPU and DSP, they all can change
the memory mappings).

One set seems to be related to power management (device wakeup from sleep) and
happening more often on some specific devices, but it may be more of a slight
difference in how they behave than "hardware bug"[1].

Last set seems to be related to networking and an Oops in network related
functionality. This may be something that triggers based on what kind of a
network environment one has or traffic that network has.

Most of them so far seem to be triggering randomly, but that doesn't mean that
it would be a HW issue. Things that depend on power management, memory
management, network environment, timings etc on the kernel side, may get
triggered seemingly randomly when the device has as complex HW and SW
interactions as what e.g. N900 has.


The important thing is to check what kind of reboot is in the question; sw_rst
or 32wd_to, whether former was because of a critical system service
termination, or whether they were because of some specific kernel oops, or
whether 32wd_to was just due to device freezing (without Oops being logged) and
provide the information in which kind of situations these happen and steps
leading to it.

Based on that information from all of you, we can then try to come up with
specific steps where some *specific* reboot cause can be nearly always be
triggered within reasonable time (say 15 mins). After that finding the cause
for the bug and fixing it becomes much easier.


[1] As to HW, every device from every manufacturer has "HW bugs", at least if
you consider any component in device working even slightly differently from its
specification as a bug. SW adapting to these is normal driver work.

Then there are variations between individual devices. HW in devices is not
100% identical, they just comply to certain set of tolerance limits and
functionality tests. Some components are calibrated at the manufacturing line
and these calibrations may also differ between devices. With the complex HW &
SW combinations & interactions & radio/network environments these small
variations may sometimes cause unexpected situations for the SW.

As to whether one could say that some issue is a "bug" in some specific device
HW, requires first determining the exact cause of the issue and whether SW can
handle that reasonably.

I have read all that, old news. That is part of the point, it is OLD news. Nokia is still spitting out these faulty devices at a rate of one for every 9 good ones. This is unacceptable for any manufactoring process, it is completely out of line by several orders of magnitude.

To say that a "fix" is to replace a faulty unit is wrong. It is NOT a fix as long as the fault rate of these new units still are 10%. Nokia is simply dodging the issue alltogether, leaving the basic QA to the customers. Now, if the fault rate was 0.01% or even 0.1%, this is acceptable, but 10% is not, not by a long shot.

Just on the train on my way back from NFS Regent Street. My original N900 was rebooting from day 1, so I've had it replaced. Jon in store couldn't have been more helpful and I've had no more reboots in almost 3 hours of really thrashing this new one, and I do mean *really* thrashing it! I sat in the Maemo lounge for nearly 2 hours before declaring myself happy with the replacement, and I've been playing with it on the tube from Oxford Circus, going in and ou og cellular signal coverage, hopping on to random wifi AP's, etc. Absolutely steady as a rock.

Moral of the tale - if yours isn't working properly, get it replaced!