Hi Anderson, > > Phone Alert Status has a method to silent the ringer during a incoming > call. It also allows to change to/from "silent" profile. Alert > notification allows to enable/disable notifications of incoming > calls/SMS. > > All of this is platform specific, therefore if we are going this route > for BlueZ 5, we need a more complete telephony interface that allows > to implement platform specific telephony bits outside BlueZ. > These are indeed highly platform specific, moreover, they are UI/UX specific. >> or should be implemented into telephony daemon. > > Maybe myself or Claudio are not clear, but I think the > "org.bluez.Telephony" interface name were supposed to mean a generic > telephony interface for BlueZ (so any Telephony related component > could use), but for me looks like it is just a HFP/HSP "proxy" > interface. > > In other words, if we wanted to move the Phone Alert Status or Alert > Notification to e.g. ofono, your interface (as is) would be not > suitable to connect to a LE socket. It sounds like moving these to oFono is not a good idea in the first place, since oFono is not responsible for the UI, ringtone generation, etc. The question is whether you want to reserve .Telephony interface for some LE specific bits (in which case we can use something like VoiceTelephony or HandsfreeTelephony for the current proposal) or try not expose the LE bits over D-Bus at all (e.g. using bluez plugins.) Regards, -Denis -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
