Who's drinking my battery juice????
 

My processes when IDLE:

http://img535.imageshack.us/img535/3...0060421041.png

40-100% of CPU is being used all the time when IDLE.

I did restart and the CPU usage is still the same :confused:

IDLE battery chart:

http://img717.imageshack.us/img717/3...0060421081.png

Re: Who's drinking my battery juice????
 

U shouldn't be watching 1080p p0rn on your n900 !

Im using now maybe 2 desktops, and my juice's his stamina is x4 (overrated ofc,. but atleast it can hold on to the next day)

Re: Who's drinking my battery juice????
 

nub device is idle ...

Re: Who's drinking my battery juice????
 

Who? Don't you mean what?

Try killall pulseaudio and see what happens.

Re: Who's drinking my battery juice????
 

It stops for a minute then reopens and starts eating processor again.

Re: Who's drinking my battery juice????
 

What apps did you install? Pulseaudio is basically used by everything but opens multiple processes. An equalizer maybe?

Re: Who's drinking my battery juice????
 

Obviously the device is not idle, there's something waking up on a pretty regular basis. Your device certainly isn't chewing through power, as your graph shows a decline of ~60% over 10 hours.

You've got something kicking your audio subsystem. Is your device absolutely idle or are you playing audio? Also, getting a shot of it at 50% or higher would be much more useful.

Re: Who's drinking my battery juice????
 

Well, no apps are runniing in the background. Not playing any audio file. Also device was near me on the desk all the time, screen didn't turn on at all.

Anyway pulseaudio isn't the only thing using CPU, check the run time on all processes.

Re: Who's drinking my battery juice????
 

Can you list everything you've installed (either via apt-get or Application Manager?)

Just because something you installed isn't listed under its own name in htop doesn't mean it's not running. Plugins, for instance, run under the name of the process that loads them, and your system's behavior certainly isn't typical.

Re: Who's drinking my battery juice????
 

Hmm, this may be helpful, today i did the following:

- Updated carbon theme and used it.
- Updated array theme
- updated callnotify
- updated fennec nighty build
- updated healthcheck
- installed shaded chat theme

Also i recieved a call today but device hanged for like 10 seconds and couldn't answer, and he called like 4 times in a row but i don't hear him talking when i answer.

I think the strange behavior started after that.

Re: Who's drinking my battery juice????
 

Hmm..try removing call notify. What does that do exactly? Anyway it's a good thing that it might be related to calls. I used to have: "Internal Error: Application X closed" all the time for everything. Then at one point in the conversations app it gave me a Nokia white screen so I removed extra protocols for IM Jabbar, Facebook etc, and no more errors.

Re: Who's drinking my battery juice????
 

that looks different to me,

my battery lasts at least 10 hours connected on wi-fi with a fully charged battery and 15 hours when connected on 2.5G GPRS.

the "flash launcherr" and "twitter widget" app was the last 2 apps i installed that make my battery drain 30% faster. even though these 2 apps are closed, they consume CPU and Battery. A reboot totally closes those apps.

Re: Who's drinking my battery juice????
 

Callnotify shows missed calls on the task bar near clock, it also vibrates and makes sound every 3 minutes to notify about missed events.

Re: Who's drinking my battery juice????
 

This behavior is completely abnormal. And this isn't the first time you've posted regarding this issue so I doubt that it only happened today.

Instead of a selection of today's actions, a bigger list of installs is probably necessary.

Or you could try flashing the eMMC and rootfs. You shouldn't ever see that sort of issue on a clean system.

Re: Who's drinking my battery juice????
 

I guess by flashing rootfs you mean flashing the .bin image. Also what should i flash first emmc or the .bin?

Will the problem return if i took backup then restored it after flashng? including application list.

Re: Who's drinking my battery juice????
 

Always flash Fiasco first (.bin). Then flash Vanilla (eMMC)

This should help: http://wiki.maemo.org/Repartitioning_the_flash

Please read the instructions carefully. And Backup! eMMC erases MyDocs so photos and music are erased to unless on the microsd. And after restoring backup pay attention at what you install.

Re: Who's drinking my battery juice????
 

The applications are exactly what is in question here. Anything from Extras will likely be installed again, nothing from testing or devel would.

If you do flash, take a back up, flash the eMMC, then flash the rootfs.

People say this, but with PR1.2 if you try chances are you'll end up toasting the thing due to the loading of resources on the eMMC (and freeing rootfs space.)

Re: Who's drinking my battery juice????
 

So first vanilla emmc then the .bin image?
also should i include apps list in the backup?

but when i flash emmc the backup file gets deleted too i guess, no?

Re: Who's drinking my battery juice????
 

do you reject the gps part when loading healthcheck. that may be a possibility. fixing it this wkend.
it would keep the gps going and healthcheck running in the background. but you should be able to see it running.

Re: Who's drinking my battery juice????
 

LOL I did it countless times. I am trying to increase /home/ size by partitioning and I am screwing up everytime. I always reflash fiasco and vanilla. N900 still works. How should you reflash then?

Re: Who's drinking my battery juice????
 

Again, my understanding is that the PR1.2 image, on first boot, will copy stuff to the eMMC. Maybe the eMMC flash doesn't boot all the way, but it confused me multiple times when it resets the device and starts the boot process.

Re: Who's drinking my battery juice????
 

You should remove the -R at the end so the device doesn't boot.

Re: Who's drinking my battery juice????
 

eMMC flash process resets the device immediately, without the -R parameter. Perhaps it's the lack of visibility in the boot process that had me confused.

Anyway, do rootfs -> emmc and if that doesn't work, swap it.

Re: Who's drinking my battery juice????
 

And before reflashing, did you remove Call Notify to check if that wasn't a problem?

Re: Who's drinking my battery juice????
 

Ok now i'm extremely confused... rootfs or emmc first? xD

also should i include apps list in the backup?
when i flash emmc the backup file gets deleted too i guess, no?

Re: Who's drinking my battery juice????
 

I would suggest installing autodisconnect for network connections first and see if that helps. Also, if you do decide to flash, do only the firmware, otherwise I would do a complete backup before flashing both emmc an FW. I had the same problem with my battery and this seems to have helped me.

Re: Who's drinking my battery juice????
 

I'm sure callnotify is part of the problem, latest version of it made my device act wierd when recieving calls.

Re: Who's drinking my battery juice????
 

Yes, complete erase. Only your card will survive. Do a full backup somewhere else (or just skip flashing the emmc, there's nothing new in it). I would avoid reflashing if there's hope to fix the problem.

Re: Who's drinking my battery juice????
 

But did you remove it? :)

Re: Who's drinking my battery juice????
 

Yes removed it 20 minutes ago, not enough time to feel the difference i guess.

Anyway should i flash or try to fix the problem, if the later then how to?

Re: Who's drinking my battery juice????
 

Check if the CallNotify was the problem (as long as it takes), if that's not it - try dbus-monitoring who is talking to mafw and pulseaudio.

Re: Who's drinking my battery juice????
 

It depends. By flashing you will generally have a clean system. But you would need to reinstall everything. And most game saves are not kept.

But flashing a Maemo device is quite nice. It's very easy to restore it unlike the N95. But try to remove some apps that may be hurting the system. And then reboot and leave it overnight idle (while you sleep). If the battery still drains you should reflash. If not then it might be an app you removed, or an app that when opened and closed stays open.

If you flash I would first .bin and then eMMC. Works for me.

Re: Who's drinking my battery juice????
 

Well, I removed callnotify and some other suspected apps like twitter widget. I'll leave it idle overnight then report back here. It's 1 am now anyway...

Thanks everyone for help.

Re: Who's drinking my battery juice????
 

If you never updated to the new firmware pr1.2, then I would suggest doing that.

http://wiki.maemo.org/Updating_the_firmware

That way you can start out with a clean slate and go from there. If you think it may be callnotify then wait a day after a full charge and see how the battery is then.

Re: Who's drinking my battery juice????
 

Wasn't there a thread a couple days ago talking about the twitter widget being horrible on the battery?

Thought so:

http://talk.maemo.org/showthread.php...twitter+widget

Re: Who's drinking my battery juice????
 

I updated to PR1.2 OTA. but i may reflash soon because i didn't flash emmc since i bought the device.

Re: Who's drinking my battery juice????
 

I did the manual install of the firmware to PR1.2 only, without backing up any of the installed software. Here is a screen shot of the BatteryGraph for the past 12 hours. Not sure if this this normal or not. For now im happy. I would be curious to see how others are doing with and without callnotify installed and see if that is the problem.

Re: Who's drinking my battery juice????
 

BTW chrome, I like the thread title. :D

Re: Who's drinking my battery juice????
 

Ok, i did some tests today, and here's my results:

http://img85.imageshack.us/img85/389...0060511212.png

IDLE #1: With Callnotfiy and twitter widget.
IDLE #2: Without Callnotify and twitter widget.

After removing some programs including callnotify and twitter, things became much better.

But 3 processes are still eating some CPU, i marked them here:

http://img32.imageshack.us/img32/445...0060511200.png

If i do killall Xorg, device restarts so i think it's essential for the system.
Hildon-desktop and Hildon-status-menu also using some CPU, when i terminate them, they reopen and continue using CPU.

Re: Who's drinking my battery juice????
 

Good to see you are making progress :)

Well... It probably sounds a bit too obvious....
Hildon-desktop - controls what runs on your desktop, therefore a desktop app or widget it using the cpu. (Would assume that to happen reasonably often?)

Hildon-status menu - Hmmm - controls the top left menu? - wouldnt have expected that to be running? - still sounds like a dodgy app in the background to me :(