Other smartphones don't turn off with battery at 40%...

you can ofcourse try changing the battery to a new one, if you happen to have a one that does voltage dropping already at 40%. Usually that happens at 20-30%.

This nokia link update is fun and all, but my N9 never had this installed in the first place. Neither do i have connection issues, so is it recommended to install nokia link thru apt get, or should i use nokia-suite to update my firmware, as described in the link above? Or should i do nothing? What do you guys think?
thanks!

Ah, I had that too
Switching the power safe mode level (from the settings) helped a bit.
For example to 10%.

The difference between the 3G- and the battery-bug is that the first will (in the worst case) make your device stop working entirely, whereas the second "only" makes the device run (more) badly.

The first case is a major problem for the manufacturer both from an customer point of view (warranty) and a network-carrier point of view (cause a mess on their networks and they will give you the boot in no time). Hence the manufacturer will fix those usually without much delay.

The second case is literally a "non-problem" for any manufacturer unless the affected customers cause a massive ****-storm on the net or do a class action lawsuit. To really appreciate the unimportance of the battery-bug just remember Apples antennagate where even a fatal conceptional design-flaw was shrugged off with a "Don't hold it that way" and then - after a massive ****-storm in the media - some bumpers were reluctantly offered but not a real fix. Since the number of N9 users is rather small any chance for Nokia to even notice there is a problem is nonexistent. Even if they'd notice they'd shrug it off with something like that's what todays tech allows for.

So a fix won't happen not because there is no harmattan-team anymore but simply because of the difference of what a "bug" is from a manufacturers and a customers point of view.


Some remarks on solving the problem yourself:

Forget all those scripts and tricks you've read about here because their solving of the problem is purely cosmetic. Real world example: I get a drop from 37% to 4%, apply one of those fixes and get back to 28%, only to drop back to 4% two minutes later and the device shutting down a minute later.

The issue is that as the device is being overly sensitive when it comes to remaining battery power (voltage). Trying to trick the device into believing in higher values won't work because there simply is no leeway allowed for. To make it short: The device is set in a way so it only accepts a new or near new battery. Anything that shows even the slightest sign of being not fresh anymore gets the 4% treatment.

You can only solve the issue by changing the battery for a new one. Depending on your usage pattern you may then enjoy 6 to 12 Months of trouble free use. Then repeat.

It goes without saying the different view on the "bug" quality of the issue hurts multiple times more from a customer point of view when the device in question has no user replaceable battery. It also shows the manufacturer has not adjusted his relevant perception of reality.

To put the story into perspective: After a year of heavy use (up to two charging cycles per day, same as my N9 now) I thought "Li-ions are rated for 300-500 cycles, I'll treat my N900 to a new battery and enjoy better battery-life". Surprise! The new battery did NOT give me more battery life. I switched back to the old one which is still in use and which still doesn't show any problems.

So either the battery in my n900 is the miraculous super-battery that comes along every 1000 years or the battery-handling of the N9 is just broken. Your pick.

could you provide a log and some "screenshots" please?

Jokes aside, I tried aceso-iso again a mnd it disabled all connections after reboot.
So...

For the fun of it, updated my N9 (Denmark) and have no issues, also, so far nothing to report improvementswise.
FB/Twitter/Qneptunea etc all works.
Openmode kernel, and Inceptiom + Powerpack also installed.
I didnt have any 3G issues before this either
PR1.3 (40_2012.21-3.340.04.1_PR_340

Also, I did reboot - since acording to some, that should/might bring up the issue.
Not, after reboot (thanks thedead) my date/time was still correct - autoupdate is set from carrier.

Did you check your date and time like I mentioned earlier?

I've had no issues with this update since install, running pr 1.3.