Al Johnson <[email protected]> writes:
> I haven't checked whether this is possible, but it would make usage really
> easy if it can be done. A setting to allow bluetooth gps capability would
> advertise the serial port when bluetooth is enabled, but the GPS would only
> be
> requested when another device connected to the bluetooth. That way gps is
> available if required whenever bluetooth is switched on, but not actually
> using power unless something is using it.
I believe the GPS-only-on-demand part of this is what already happens.
IIUC:
- the 'rfcomm 0 1 watch "gpspipe..."' invocation means that the
"gpspipe..." part will only happen when some client connects to the
bluetooth serial port
- GPS only gets switched on when gpspipe makes a connection to fso-gpsd.
The other part of what you've described is "listen on the bluetooth
serial port whenever bluetooth is enabled", as opposed to "enable
bluetooth now and start listening", and I agree that that makes sense.
Given that approach, does this even need a setting? Given that someone
using this will still have to explicitly pair their GPS client device
with their FR, is there any reasonable scenario where someone wouldn't
want the GPS service available?
(Maybe if the client device is one where you trust the software for one
kind of Bluetooth thingy, but you don't trust its software for accessing
GPS. Is that plausible, and should we be bothered with it, at the cost
of less automatic operation?)
> You just need to turn bluetooth on
> and off through Quick Settings, rather than looking for the app or digging
> into the settings each time.
My current SHR-T (which is the latest available) doesn't have bluetooth
in the quick settings, but I imagine a new release may address that.
> The setting that controls this should be available under both the gps
> and bluetooth areas of the settings app as both are logical places for
> a user to look.
As suggested above, I think it would be neatest not to have a setting at
all. If a setting is needed, I think just one place is best; having the
same thing in two places is a source of possible confusion.
Regards,
Neil
_______________________________________________
Shr-User mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-user
