----- Message d'origine -----
> * AT+CPBR and friends is hooked to the phonebook, which is
> therefore inadequate inside oFono.
I am not buying into the AT+CPBR for the local and user specific
phonebook. That one is inside Tracker anyway and also inside the user
session. Trying to really support this is a broken idea. CPBR can not
expose the information of modern contacts storage anyway, so just don't
I can see how AT+CPBW could be problematic, more so than AT+CPBR. But that is not
relevant. If a big enough customer wants it badly enough, it has to be done. I do not want
to end up with an architecture that forbids satisfying some of my employer's potential
If you really care about it then use Bluetooth PBAP via obexd which
have enabled already.
> * At Nokia, we also have some non-standard commands for internal
> * Some operators require some funky AT commands of their own. It might
> possible to open-source them, even if we want to.
And these should be on an engineering mode only USB CDC ACM interface
with a different backend anyway.
I already mentioned that the same software must run in certification and in user's
hands for "whole device" certification to be valid. But anyway, some of those
commands were requested as DUN extensions, not as testing stuff. So no no no.
Only because someone wants to shoehorn this into something nasty,
doesn't mean we should do it. And I am not going to scarifies the
simplicity of the oFono D-Bus API for this.
We are talking about the Originated boolean call property?!