Just try to use USB cable to charge from PC We want to check if bme show proper behavior, that way it shouldn't matter if You're charging from wall charger (data pins crossed) or USB. Unless we meet some strange bug with only fast-rate charge (enabled by mentioned earlier cross between D+/D- pin) - but i really doubt about that.

Flandry - this way You're right, of course. But please, don't do measurements (and don't recommend others to) of battery drain by using battery-eye. Battery-eye, using standard bme guessing methods, just... Well, guess - when we talk about battery charge percentage. Only info that may be useful from applications like that is Voltage - mAh, percentage of charge etc are just estimated values.

Even worse, this like to turn into total mess when You switch heavy/low usuage many times during one cycle, then, on another - for example - use only low use or only high use. For me, Battery-eye show under-zero capacity 1-2 hours before real discharge almost 100% times. Not to mention how it goes crazy when You replace battery with new one, or - scary word - hotswap it

Only one exception from that may be dr_frost mAH graph, tied strictly with voltage - but even voltage can fluctuate highly on power-cycle (yea, after turning off/on you can have higher voltage for even quite long time), so measurement by that way can show You that powercycle charge Your battery On the other hand, programs like battery-eye use some build-in artificial handling of powercycles - when you do it, it mandatory shows huge capacity drop, so, as i mentioned in other thread, You can do 50 power cycles, then use Your N900 for another day with -70 capacity all the time

After having this issue for several days it suddenly disappeared
Audio is transmitted just fine to and from carkit via bluetooth again. I have no clue what might have caused the issue as I didn`t change anything in the meantime
I can also confirm that kernel v47 works with bluetooth headset HS-56W.
So for me kernel v47 seems to have no issues with bluetooth for me...
Sorry for the confusion caused by this!

Thats important info, but are You sure that absolutely nothing changed on your N900, i.e no updates etc? That would be really strange, if happen out of nothing.

Yeah, at least no system or bluetooth relevant updates or changes...
I´ll keep an eye on this, but to me it seems just like a strange one-time event

I am dealing with SW development for at least 20 years and trust me, there is no such thing like "strange one-time event". There are reasons why you have had a problem and there are reasons why you don't have it anymore. Just do you best to find them (if possible), it will help a lot.

i would like to install kernel v47 BUT will i be-able to keep my packet injection kernel (2. Power46-wl1) ? these are my custom kernels.

1. Stock Maemo
2. Power46-wl1
3. Power46
4. n12 umay
5. Backupmenu

Well, the very day I posted here about my problem with the carkit I verified with my old bluetooth headset which worked right away. In between I received/installed an update for MIR Translator, not other changes.
This day I also asked in the thread regarding obex with PBAP support if someone else is having the same issue. HSchmitt answered that obexd can´t be the cause as audio transmission via bluetooth is done by bluez.
Over the weekend I updated and installed a few more apps but none of those is bluetooth related: Khweeteur, cutetube QML, Ytube, TweetSuite, appwatch, shaketowake2, Marble, eSpeak, witter and ZapLoc.
Hm, might be that I also played a bit with overclocking and undervolting during the days in question, but was only using stable configs...
As I said, will keep an eye on that and keep you guys updated...

Ok, for completeness, I installed v47 on March 3rd.
By checking my call history I can confirm that my carkit worked fine until end of April using v46.
One unusual thing I did today was disabling/enabling bluetooth accidentally using bluezwitch. Normally I just leave bluetooth enabled all the time.
I think, but am not 100% sure, that I rebooted the phone while I had the problem which would be like the same as re-enabling...

You are right about the music being fixed but you wont be able to change your alarm ringtone until another fix is made. Using newest version and I get 'internal error. Application clock closed.'

Hi PowerKernel47 devs,

thanks for all your work. I have been really pleased with many aspects of this kernel.

However, I was wondering if you acknowledge that there could be a problem with battery lfe on this version. I left my phone on standby overnight and it dropped from 8 to 5 bars with almost nil CPU activity.

Now it's possible that v47 is not to blame, but the problem seemed to start at the time I installed it.

Do any of the v47 devs notice a difference, and has there been any investigation?

Cheers, X.