What's supposed to happen when the battery is full?
I have been charging 24h with display on, but the battery icon still shows the charging animation and the yellow Led is on.

Also I have to unlock my sdcard after every reboot to get write permission: chown -R user:users media/mmc1/

hi

here is my problem : i cannot connect my N900 to the internet but i can download packages manually to my pc . Is there a way to install kernel power through terminal ? And the magnet sensor of keyboard is always giving a closed state .
Sorry if it has been asked before

@myname24,

download the .deb's directly (go to maemo.org/packages, type kernel-power, and download relevant packages) -- SEE FIRST POST for instructions on how to install them.

Add.: @myname24, please respond here, not per PM. Post the exact output of the dpkg commands you execute. Otherwise nobody can help you.

well it didn't work and give me conflicting package with maemo kernel and pre dependecy errors

edit :
Nokia-N900-51-1:~# cd /home/user/MyDocs/kernel/
Nokia-N900-51-1:/home/user/MyDocs/kernel# dpkg -i kernel-powe
r_2.6.28-10power51_armel.deb
dpkg: regarding kernel-power_2.6.28-10power51_armel.deb containing kernel-power:
kernel-power conflicts with kernel-maemo
kernel-maemo (version 2.6.28-maemo19) is present and installed.
dpkg: error processing kernel-power_2.6.28-10power51_armel.deb (--install):
conflicting packages - not installing kernel-power
Errors were encountered while processing:
kernel-power_2.6.28-10power51_armel.deb

@myname24,

Well, then remove kernel-maemo first. It's now obsoleted by kernel-power.

If you also have kernel-flasher-maemo, remove it as well.

Then try again.

edit : now works thanks

See my last few posts about termination_current, and sysfs entries et all.

After another few charging cycles, I've noticed that neither default 150 mA (6550 as sysfs value, when read) nor 50 mA (6500 sysfs) works OK - first one terminates charge too early, without switching VDQ to 1, while latter never terminates it (in case of my dual-cell battery, result for regular ones may wary).

6500 (100 mA) seems to work best - IIRC, it was also default used by BME?
---

As for SD card, no such problems here.

/Estel

Can some1help me with his pls.

Try to remove the backports-modules package, then retry to update the kernel.

Sorry for not posting "the rest" but I forgot what it was. Today I had batterry/charging bug I suppose. I couldn't boot my device for long time after crash or emergency shutdown. It succeeded without reflash after long time of retries. The reason why I think it is related with batterry state is the batterry was almost empty at the shutdown or another problem forced my device to shutdown.

I want also to remind old known bug I suppose - in kernel power with multiboot implementation (read it as - not direct booting only kernel otherwise) it fails to boot properly into system while charger is connected - it seems to lock at ACT-DEAD state despite trying to leave it in a way which worked previously. I don't know if it is the same bug as one from ages but rarely occuring or it was new since Kp51 - but I feel forced to remind that - even if user resolution/workaround is trivial - just to disconnect charger, boot up until desktop shown and reconnect it. I hope you would find some time to adress that.

PS: the time it failed to boot was too long for the time it having too low batterry to do the manuever, and I also had the fbcon log with error which I couldn't catch long enough to know what were written, but long enough to see there was at least one then.

EDIT: it seems reseting the device by pulling out batterry for 30 seconds were neccessary to recover non-booting problem but not enough anyway.

---------------------------------------------------------------

it seems from the behaviour that kp51 after "full" batterry and wallcharger present tries to overcharge the batterry by mistake but it may be wrong device Charging Reporting behaviour under kp51.