View Single Post
Posts: 67 | Thanked: 32 times | Joined on Oct 2011
#121
sorry maybe it's prejudgation but i got first time from ages the message about ressetting defaults by kernel-config because of some problem. It doesn't happen while low-batterry shutdown nor while the batterry is removed when the device is supposed to be off. So I quick judged it was problem with kernel crash. It could be hardware error either - I couldn't judge without properly reading logs. While the "emergency shutdown" due to some problem - were it real problem or kernel imagined one from wrong readings of availible sensor and HW-traces - the batterry was on too high level to shutdown due it beeing too low. Just remove the batterry put in and boot and it worked for 30 minutes to discharge. When it gently shutdowned due too drastically low charge i put the charger and it was behaving most gently since update to kp50 so some bad device state was reset so the bugs doesn't happen yet. I had problems with nokian batterry meter for long time but it worsened at kp51 update. After Device HW state reset problem is cured until now. BNF seems to measure batterry properly while QT batterry widget which uses most of nokian metter mechanics was able to show my batterry is at 5mah while in reality it were 33% or something less. The thing that worries me most since mild overheats (44c to 55c spikes on batterry) are mostly gone that bnf showed in it's popups that batterry data were recalibrated at least 3 times while I didn't recalibrated it in on purporse. I would exactly know how to collect log from file anywhere in mounted filesystem but I don't know how to collect it from /dev/mtd2 which is device - is it that cat command is enough and how much would it weight in kilobytes? Maybe some help or a link to an howto? I'm in hospital without wifi but my phone have already bought a few hundreds of megabytes of transfer. Let talk more later.