asked 2013-12-24 22:04:30 +0200
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:
devel-su
systemctl stop tohd.service
answered 2013-12-24 22:25:22 +0200
devel-su
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
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 )editI'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 )editanswered 2013-12-25 20:49:30 +0200
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)
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.
@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 )editanswered 2014-02-01 00:46:19 +0200
The Naamankajärvi update (1.0.3.8) seems to fix this. I installed the update, unmasked & started tohd - no increase in power consumption. (Hunger Meter running before & after.)
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 )editanswered 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.
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 )editWorks for me with no problems. Dramatic reduction of battery discharge rate. Richard
richardski ( 2014-01-22 11:18:28 +0200 )editanswered 2014-01-10 15:54:05 +0200
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.
answered 2014-01-07 22:41:59 +0200
Disabling tohd.service may produce unexpected behavior: Bug: Call timer slows down considerably when screen is off (closed)
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.
Asked: 2013-12-24 22:04:30 +0200
Seen: 3,106 times
Last updated: Feb 01 '14
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 )editIf Jolla is already working to fix this why isn't this question taggetd with "roadmap" ?
foss4ever ( 2014-01-04 15:15:56 +0200 )editHow 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