I love you Quim and I love the way we feel part of this project, an active part of it.
I've always been frustrated by being 'just' a customer, even if I am a developer.
I love the way the Maemo team is handling communications with us as developers and customers.

Thanks. To all of you guys.

Quim:
Thanks for the link. Very good!

(Off-topic: This is my posting #1000 to Internet Tablet Talk. Never thought it would get that far. Virtual beers for everyone! )

(hope i did not double post..)

thanks a lot for the kernel and scripts. i tried it and so far my n800 is still kickin. I wrote the steps down here, so perhaps others can refer to it when needed.

one thing i noticed after the update is the slight improvement of response time when i start a software or so. is it just a feeling, or generally something has been improved?

thanks agin.

I have updated kernel flasher so it won't print that scary message about size mismatch. Now the size is properly checked (kernel has its size stored in its header). Smaller files (=incomplete downloads) are detected and flashing is aborted. Larger and already padded kernels (those extracted from full firmware images) are properly reported. I hope there is no additional bug introduced.

I am missing something, while this seems to have fixed my problem, the description of the issue it fixes does not match my experiences. When untarring large files from flash to mmc1 or mmc2 (2gb kingston mmc mobile or 8gb class 6 kingston) 50% of the time my system would reboot, regardless if I download to flash, mmc, or copy using card reader. This indicates to me a problem, not having anything to do with wlan, and everything to do with mmc kernel support. Will we ever know what really went on, or why Nokia took so long to acknowledge this issue? As I said before, after 2 years I am sick of being the unpaid beta tester for this product!!

As the Beastie Boys say, GET IT TOGETHER!!!!

That sounds like a real problem and I can confirm it happened to me too when I tried to untar XFCE files in my tablet. (Wasn't the latest kernel that time, though... but I assume nothing changed on that respect.)

Another issue I have seen and happens on both of my tablets is that I can not run Windows disk check utility on either of my SDHC cards: 4GB Sandisk and 8GB Patriot. It just stops after about 30 seconds, the N800 display backlight come on, and Windows tells that it is unable to complete the disk check. At the same time the memory card is not seen by Windows any more. Unplugging and replugging the USB cable bring the access to the card back. The issue does not happen if the cards do not have many files, but if there is thousands of MaemoMapper files then this happens 100% of the time. It is very reproducible. If I run the same disk check on these cards using external USB card reader they can complete the same process without issues, and reports no errors on the cards.

Maybe this is fixed in the next Chinook firmware... I need to test that... If not, then I'll file a bug report.

Because they weren't able to reproduce it internally due to the bug reports not having enough detail. Fixing bugs is a hell of a lot easier if you have a rule to reproduce a bug. For example, if everytime you run the alarm program, the tablet crashed. Due to the type of bug this was as well as the fact that most of the bug contributors didn't include details they didn't think was necessary (not their faults since they aren't paid professionals), it took a hell of a lot more time to figure out what the issue was. The problem was a bug in the Linux kernel and we're basically the first ones that had the right conditions to discover it. Not Nokia's fault.

Do you also believe in Santa Claus? Perhaps nokia should put instructions in the documentation, so all users would know how to file bug reports? This is just crap, the problem could be reproduced at will on my and many other tablets, perhaps a little qa testing would have proven this. I guess they consider the user community their qa?

crap crap crap,

If you were able to reproduce this at will, why didn't you contribute to the bug report then? You could have saved a lot of people their memory cards. Again, you clearly have no idea what's going on and you have no idea what caused the bug and no idea how QA works. Big surprise.

Zero, if all some people choose to do is skim the subject, you're wasting your time and effort leading them to water...