We have moved to a new Sailfish OS Forum. Please start new discussions there.

All of a sudden: battery drain [not relevant]

asked 2014-04-08 19:33:51 +0300

steff gravatar image

updated 2015-04-24 14:53:03 +0300

r0kk3rz gravatar image

All mW measures I'll mention are delivered by 'Hunger Meter'.

After upgrade to Ohijärvi ( it was fantastic! The battery lasted for almost four days while surfing and doing a few phone-calls. But after four weeks, all of a sudden, the battery drained completely whithing 10 hours. Excessive heat around the camera lens. 'Hunger Meter' showed an average consumption of ~3500 mW - and even more, and the current consumption fluctuated between 2500 mW and 3500 mW. After a reboot, the average consumption leveled off at around 600 mW just to raise up to 3500 mW again after an hour, sometimes after two hours.

The main suspect was 'Mitakuuluu' because this problem occured after upgrading Mitakuuluu to v02-4. But it persisted even after upgading to latest release v02-10 and even after removing Mitakuuluu completely, the battery kept draining off it's power soon after rebooting.

How comes?

edit retag flag offensive reopen delete

The question has been closed for the following reason "question is not relevant or outdated" by r0kk3rz
close date 2015-04-24 14:53:20.458877



Have you tried to look for high CPU usage, e.g. with top in terminal (dev mode) or using the app Lighthouse? Edit: Might be a duplicate of https://together.jolla.com/question/37774/jolla-is-overheating-by-itself/

lenggi ( 2014-04-08 20:41:35 +0300 )edit

I doubt this has anything to do with Mitakuuluu. I use Mitakuuluu v02-10 and I do not recognize this behaviour. Do you run any other applications in your home screen? Have you checked what services are running with Crest? Did you mod your phone, wireless charging for example?

Jozz ( 2014-04-09 00:05:05 +0300 )edit

Related or not, but during the few past software releases, I've witnessed a sudden battery drain occasionally (perhaps ~5 times in last three months). It's been always solved by a reboot (which I've ususally done as soon as I've noticed it) As the event is rare, I've not got any clues of processes causing it. At least once it seemed to be triggered by or during charging the phone. I've suspected that it might be Android subsystem or apps because my Xperia phone does exact same thing sometimes.

jsievikorte ( 2014-04-09 10:40:21 +0300 )edit

OK, 'top' shows me these processes on top: d.process.acore hits the process table with constantly 58% systemd-journal between 24% and 33% system_server quite constantly using 21% e.process.gapps between 15% and 17% alienlogd between 3% and 4% The rest is negligible...

@Jozz: no, it's definitly not Mitakuuluu eating up the power resource...

steff ( 2014-04-09 15:44:46 +0300 )edit

Has anybody an idea what causes the processes above, especially d.process.acore to use almost 60% of the resources? After a reboot, not one process is using more than 1.6%!

steff ( 2014-04-10 09:53:04 +0300 )edit

3 Answers

Sort by » oldest newest most voted

answered 2015-04-22 08:48:30 +0300

cy8aer gravatar image

updated 2015-04-24 08:55:47 +0300

This seems to be an 1.1.4 issue for me: Yesterday: Full battery load in the morning, 100%, one hour podcast/gsm/car/bluetooth 92%, work day 86%, ca 20:00h then looking for updates and installing world clock (so nothing very critical stuff), 23:00h 56%, 06:00 device off (!) after boot 14%. One hour later 4%. I cannot find any problems via top/lighthouse or powertop. Till 20:00h the device worked normal and then the draining crash. I had the effect that it took a lot of time to load the battery again (so draining was faster than loading!). Because of the issue I have only 0-2 applications running (was about 5-6 before: clock, calendar, messages, phone, gpodder, jolla weather with 1.1.3) and three days working with one battery load was possible, not possible for a day now.

Update I am actually loading the battery. On 22% I stopped the device and cleaned the battery connection (seems to bee voodoo because everything was clean). After starting again: 46%. Hm, wrong measurement of the battery state?

Just another update Device running the third day now, 36%. Probably a battery contact problem?

edit flag offensive delete publish link more



Might be this. (jolla-randomly-shuts-down)

Or your battery is dying - let's hope this is not the case, as I've understood a spare battery is somewhat tricky to get hands on.

Also see this: immediate-battery-level-drop-from-more-than-half-charged-to-empty.

raketti ( 2015-04-24 09:56:52 +0300 )edit

answered 2015-04-21 11:15:17 +0300

Mr.Thumb gravatar image

updated 2015-04-21 11:43:38 +0300

Hmm.. I got the same thing, got a ingoing call > 10min , the phone was shudden hot around the lens , it showed 33% but , I fired up an app and it shudden said : low battery and shot down !!?? Complet flat . I'm on OS ver : now after 5 min recharge is say 43% battery !?? that's a quick recharge !! ..a bug in battery daemon maybe ?

edit flag offensive delete publish link more



Your battery is reaching the end of its life.

Giacomo Di Giacomo ( 2015-04-21 11:50:12 +0300 )edit

not sure, i had this issue on my one month old jolla too. 50 to 5 within minutes, back to 50% after 5 mins of charging. i assume my battery is not dead after one month, and since two weeks no such problems again. however 1 day and somethin of operation is maxon my jolla

pawel ( 2015-04-21 18:56:16 +0300 )edit

Have you fixed the battery connection? You need to add some padding between the end of the battery and the case, to make the battery be more tightly connected.. that fixed the random battery/reboot/crash problems for me.

pasikarkkainen ( 2015-04-21 19:03:22 +0300 )edit

answered 2014-04-09 22:10:30 +0300

bilgy_no1 gravatar image

There's another battery drain issue (sudden booting and the 'reboot loop'). The suggested fix (by Jolla) for these is to let the battery drain down completely, and then take the battery out of the phone for at least 10 minutes. Finally, pop the battery back in and charge the battery.

It might help with your issue as well, and it can't hurt to try...

If this doesn't help, and you can't isolate an app or process, get in touch with the people at care@jollamobile.com

edit flag offensive delete publish link more


My phone never ever botted randomly. My phone recovers from excessive powerdrain instantly after reboot.

I suspect, that if the signal rate is poor, the phone gets into trouble,..

steff ( 2014-04-10 09:55:14 +0300 )edit

I understand you don't suffer from the reboots, but the underlying issues might be related. E.g. people report battery levels dropping from perhaps 70% to 4% instantly.

I also suffeted from the overheating and battery drain issue, it seemed to have something to do with poor reception and wireless connections, but that was prior to 1.04.20. Since Ohijärvi: no more overheating and high energy consumption.

Howver, sometime after the update I did experience the reboots and reboot loop issue (that was supposedly patched in the update). Doing the prescribed procedure did at least provide temporary relief. Given the loose similarity, I thought I'd give you the tip to just try this. If it works, great! If not, it may help Jolla to further pinpoint the problem.

bilgy_no1 ( 2014-04-11 09:58:38 +0300 )edit

Bilgy, fully agree! But my beloved Jolla didn't loose the power since I initiated the last reboot. I'll wait until the power goes vamoose again :-) and will follow your hints then. You know, it always was all of a sudden when it happened. It just didn't happen since a few days. It probably happens only then, when I got no charging cable with mie ;-)))

steff ( 2014-04-11 14:15:24 +0300 )edit

Hi both of you :), i experienced the same problem described in steff's first post, did this procedure really help?

Francesco ( 2014-04-29 12:12:26 +0300 )edit

Question tools



Asked: 2014-04-08 19:33:51 +0300

Seen: 1,855 times

Last updated: Apr 24 '15