Ask / Submit
15

A switch (or section) for TOH in System Settings

asked 2013-12-30 09:48:33 +0300

NikosAlexandris gravatar image

updated 2014-01-19 20:52:04 +0300

lk gravatar image

This is yet another request-question: wouldn't it be practical to have an On/Off switch for the tohd.service appearing right in the main page of Settings (as well, of course, as in the System Settings)? This would ignore on-demand any reaction following any replacing of TOH cover.

Update: As suggested by @simosagi, a dedicated section for TOH in the System Settings would be, perhaps, suitable so as to manage the effects when the "Halves" get together!

edit retag flag offensive close delete

Comments

2

I think probably there may be a section of the settings reserved to TOH behavior.
It's not only about an on/off switch for the service, but e.g. you may want to keep the service but not automatically switch ambience in every circumstance. Also, later TOH may use other detectors than NFC.

simosagi ( 2013-12-30 14:24:58 +0300 )edit
1

@simosagi Right, the idea is not only for saving-power, but simply prevent TOH related (re-)actions.

NikosAlexandris ( 2013-12-30 16:29:50 +0300 )edit

1 Answer

Sort by » oldest newest most voted
4

answered 2013-12-30 12:27:01 +0300

Actually, I would prefer to have a turn off NFC feature. NFC is a connectivity entry, so just like Wifi, Bluetooth, there should be a LED controlling NFC, and I was quite surprised that in the initial release, there were no NFC switch. tohd can still be running, but without NFC, it will just be useless.

Of course, turning NFC could display a warning, saying that TOH identification will be disabled too.

edit flag offensive delete publish link more

Comments

2

Well, I think your and the original idea are only partly related. At the moment NFC is the only method TOH communicates with SailfishOS. But as there are other interfaces between TOH and the main unit future TOH implementations can use them (I have the I2C bus in mind at the moment) for TOH identification. Therefore I believe the NFC control and TOH daemon control (if any) should be handled separately.

strnous ( 2013-12-30 13:30:26 +0300 )edit

Just to make it clear, IIUC, NFC in Jolla serves, and will serve only, TOH. Right?

NikosAlexandris ( 2013-12-30 16:31:06 +0300 )edit

I think that I2C and NFC are unrelated. I2C sounds more like USB to me, and turning off I2C makes as much sense as turning USB port off on a computer ... However, NFC is wireless connectivity, much like Wifi. And I hope that NFC on the Jolla can do better than just TOH.

Sfiet_Konstantin ( 2013-12-30 16:35:30 +0300 )edit

@Nikos Alexandris From what I have read so far I do NOT think NFC is going to be used for TOH only in the future. And I hope there will be also other usage to it.

@Sfiet_Konstantin The original idea asked for a possibility to deactivate the daemon handling the TOH connection/identification. At the moment only NFC is used for that purpose. In the future TOHs will use the other connections available (I2C and power connectors). Therefore I mean the deactivation of NFC would eventually not be enough to disable the TOH identification. That leads me to the idea of separate switch for NFC only (which will disable the NFC connectivity altogether not limited to TOH) and another switch to disable the daemon handling TOH which would disable handling of TOHs (effectively turning them into a dumb cover) but will let the NFC turned on to be able to interact with other NFC enabled stuff (NFC tags, other phones, ...) I hope I do express myself clearly enough to be understood :)

strnous ( 2013-12-30 16:48:07 +0300 )edit

@strnous sounds good, but disabling a feature don't sounds great to me, and that was originally my answer. Disabling connectivity points such as NFC, I2C (even if IMO this don't makes sense to me) sounds better to me. That's all :)

Sfiet_Konstantin ( 2013-12-30 16:56:39 +0300 )edit
Login/Signup to Answer

Question tools

Follow
2 followers

Stats

Asked: 2013-12-30 09:48:33 +0300

Seen: 323 times

Last updated: Jan 02 '14