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

[fixed in] Fix power consumption Other Half [released]

asked 2013-12-24 22:04:30 +0200

Jarno gravatar image

updated 2014-04-09 16:51:36 +0200

chemist gravatar image

Although a workaround is already known it would be really great if the power consumption caused by the Other Half connection/NFC gets fixed. Turning the feature off makes the Jolla suddenly very power friendly

For those who missed it at e.g. http://reviewjolla.blogspot.nl/2013/12/jolla-battery-life-power-consumption.html open terminal and stop the process:

systemctl stop tohd.service
edit retag flag offensive reopen delete

The question has been closed for the following reason "released in a software update" by eric
close date 2014-03-19 16:36:28.673215



I know you are working on this issue, probably first priority. I just want to suggest to fix it before the "important" reviewers make their reviews (battery issues are always highlighted). It will not matter to us early adopters, but it could be crucial for potential users.

Neo ( 2013-12-31 17:02:04 +0200 )edit

If Jolla is already working to fix this why isn't this question taggetd with "roadmap" ?

foss4ever ( 2014-01-04 15:15:56 +0200 )edit

How about receive a hotfix NFC The Other Half solution without dev mode from jolla care support ?

redge73 ( 2014-01-09 03:30:04 +0200 )edit

@jjaone Since you mentioned it first in one of your comments above and since no one is answering, I have a suggestion: tag this question with "roadmap" and see what will happen (@eric will either leave it be or maybe give some information if he removes the tag). If you don't want to do it, I will. I just think we should have more information on such a big issue.

Neo ( 2014-01-10 23:48:11 +0200 )edit

@Neo your proposal would be counter productive to be honest... I'm confident some information is coming soon, just a little patience, thank you.

eric ( 2014-01-11 00:07:16 +0200 )edit

6 Answers

Sort by » oldest newest most voted

answered 2013-12-24 22:25:22 +0200

petros gravatar image

updated 2013-12-24 22:27:13 +0200


systemctl mask tohd.service

systemctl stop tohd.service

if you want to disable it even after a reboot. You can always enable it by this command

systemctl unmask tohd.service

edit flag offensive delete publish link more



My answer still applies: systemctl mask tohd.service can make the system unable to boot, and bricking your device.

Sfiet_Konstantin ( 2013-12-24 22:28:03 +0200 )edit

I have rebooted a couple of times since then..Was I lucky?

petros ( 2013-12-24 22:33:17 +0200 )edit

In what role you're sharing the warning? Considering adding it to the article, at least if official.

simo ( 2013-12-25 00:32:51 +0200 )edit

I've been using dev-mode commands to stop/unmask tohd.serivice with no probems in using/booting device.And it has significant effect on battery consumption: in normal use from 1800 mW to 700 mW, and in idle (screen off) from 1000 mW to 50 mW, according to some powertop runs I conducted :)

foss4ever ( 2013-12-25 07:41:59 +0200 )edit

A warning added to the article anyway - this should guide unexperienced users to use the foil solution instead. Better for them to not accidentaly break anything ;)

simo ( 2013-12-25 23:54:46 +0200 )edit

answered 2013-12-25 20:49:30 +0200

phle gravatar image

For those of us not yet ready for tampering in the terminal, do note that a simple hardware tweak works just as fine: (option #2 from the above linked page)

  1. change to an Ambience not used by The Other Half (TOH)
  2. remove TOH from phone
  3. re-boot phone
  4. take a piece of tinfoil, fold it a few times (three layers should work, according to same page)
  5. cover the TOH NFC-chip with the tinfoil (attach it with some tape, so it stays in place)
  6. put TOH back on phone

If the Ambience now does not change to the one used by TOH, your amount of tinfoil layers was enough, and you should now have a less power-hungry Jolla. (You may now choose whatever Ambience you prefer. :-) )

I guess we'll expect a software update after the holidays, but 'til then this works.

edit flag offensive delete publish link more


Has this foil trick been tested, with powertop for example?

jsiren ( 2013-12-26 00:49:21 +0200 )edit

Tested by several users, found to work great with at least 3 layers of fold.

simo ( 2013-12-26 00:53:26 +0200 )edit

With only one layer i still have 80% after exactly 24 hours :-)

hase5911 ( 2013-12-26 11:28:42 +0200 )edit

@jsiren; yes have tested this and SW-tweaks with powertop and the results are simular. And if the.foil is difficult to attach, just remove the tag altogether, works like.a charm ;)

foss4ever ( 2013-12-26 22:23:38 +0200 )edit

@K.T The chip may be necessary if you want to redownload the the ambience. (unless they register it to your Jolla account). It will be necessary if they offer any new features using other halves (like tying accounts to an OH, for lending your phone to someone to play a game without giving access)

Vaskinn ( 2014-01-08 22:08:56 +0200 )edit

answered 2014-02-01 00:46:19 +0200

jsiren gravatar image

The Naamankajärvi update ( seems to fix this. I installed the update, unmasked & started tohd - no increase in power consumption. (Hunger Meter running before & after.)

edit flag offensive delete publish link more



I was waiting for this :) Time to close, finally. Great work fixing this Jolla Crew!

simo ( 2014-02-01 00:53:30 +0200 )edit

Before updating I was getting at least 3 times as much battery time (with tohd service stopped), than I am now with the update, with or without tohd service stopped. Am I the only one? I went from having the perfect phone battery (almost 4 days of regular usage), back to old android times with 1,5 days after the update!! Please help!

dsilveira ( 2014-02-03 17:50:50 +0200 )edit

@dsilveira I was the one closing this up, as new battery issues might have any other reason too... Maybe you put up a new question of your experience? (or test if the old workarounds helps you again, so that we could consider reopening this anyway)

simo ( 2014-02-04 01:43:41 +0200 )edit

answered 2013-12-24 22:05:48 +0200

Please note that some people reported that disabling tohd service can brick your device. Please use with care and wait for an official Jolla fix.

edit flag offensive delete publish link more



I've missed that. Could you provide me with a link?

If so, should I at least remove the commands?

Jarno ( 2013-12-24 22:12:53 +0200 )edit

Someone on JollaFr reported it, saying that it changed the phone to a brick, and required assistance on IRC to repair the phone. It's in French though. Link to the comment here

Sfiet_Konstantin ( 2013-12-24 22:15:34 +0200 )edit

FWIW, the brick was unrelated to this.

But yes, anything in developer mode: use with care! you get to keep both pieces if you break something

Stskeeps ( 2013-12-24 23:35:04 +0200 )edit

However I had my phone hanging a couple of hours after stopping the deamon. Happend three times. Used the tin foil instead. No more hang ups since then.

Aequanix ( 2013-12-26 17:41:34 +0200 )edit

Works for me with no problems. Dramatic reduction of battery discharge rate. Richard

richardski ( 2014-01-22 11:18:28 +0200 )edit

answered 2014-01-10 15:54:05 +0200

foss4ever gravatar image

No it can't brick your device, your answer is just rumors, never confirmed by anyone. But, care should be taken when fiddling with system services in the device.

edit flag offensive delete publish link more

answered 2014-01-07 22:41:59 +0200

clau gravatar image

Disabling tohd.service may produce unexpected behavior: Bug: Call timer slows down considerably when screen is off (closed)

edit flag offensive delete publish link more


To clear out: Disabling tohd.servce, or masking & stopping tohd.service, or both?

simo ( 2014-01-07 22:44:13 +0200 )edit

Shouldn't matter as long as tohd.service is not running. Masking and rebooting, OR just stopping the service will get you in the same situation. AFAIK, disabling it has no effect, it will still start on next boot.
Though, if you can test the report above too, I would appreciate it.

clau ( 2014-01-07 22:49:49 +0200 )edit

Just disabling tohd is not enough, tried to reproduce it, stopped tohd, let proxity sensor poweroff the screen for 20s and then woke up display and the time on the phone was correct.

miska ( 2014-01-07 23:49:23 +0200 )edit

Question tools



Asked: 2013-12-24 22:04:30 +0200

Seen: 3,052 times

Last updated: Feb 01 '14