Re: Does the get_service_provider_name method only return a name if the SIM is a USIM?
la, 2010-02-06 kello 11:10 +0100, ext Faheem Pervez kirjoitti: As said in the title: dbus-send --system --type=method_call --print-reply --dest=com.nokia.phone.SIM /com/nokia/phone/SIM Phone.Sim.get_service_provider_name returns a blank string. As I only have a T-Mobile SIM to be trying this out with, I'd like to know if a string is only returned if a USIM is inserted. Or maybe I'm invoking it in the wrong manner? Not all SIM cards have the SPN field set. Overall, there are four sources of names for network operators: * Service Provider Name (SPN) field on the SIM * CPHS operator name on the SIM card * Hard-coded name based on a list that GSMA publishes periodically This is typically stored on the modem firmware * NITZ indications that the network sends What gets displayed on the home screen, for instance, is some combination of these names, depending on certain conditions set on the SIM card, and whether the device is roaming or not. Cheers, Aki ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Does the get_service_provider_name method only return a name if the SIM is a USIM?
ma, 2010-02-08 kello 08:09 +0100, ext Hartti Suomela kirjoitti:
In short, the digits for both MNC and MCC are stored in 4 bit fields
in the resulting 3 bytes
mcc2 mcc1 mnc3 mcc3 mnc2 mnc1
Note that the MNC can be either 2 or 3 digits long. In the former case,
it's padded with 0xF.
Cheers,
Aki
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Does the get_service_provider_name method only return a nameif the SIM is a USIM?
ma, 2010-02-08 kello 16:50 +0100, ext Aldon Hynes kirjoitti: I realize that they are mostly available over D-Bus, but not officially documented or supported. That is part of the reason I sent a message to this list in case any developers, or even folks at Nokia could unofficially share information that other developers might find helpful. Sure, what is it that you're trying to do exactly? Cheers, Aki ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Does the get_service_provider_name method only return a nameif the SIM is a USIM?
ma, 2010-02-08 kello 18:40 +0100, ext Dawid Lorenz kirjoitti: If I could join (aka steal ;) this thread, I'd also be interested in any methods that would return network registration specific details, such as LAC, CID, network type (ie. GSM/EDGE/WCDMA/HSPA) etc. Then, may I suggest you take a look at oFono [1] instead? oFono is a completely open source telephony stack, which will at some point be replacing the current Maemo stack. It's already available in extras-devel. Cheers, Aki [1] http://ofono.org ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Telephone API question - answering a call.
ti, 2010-01-26 kello 19:12 +0100, ext Matan Ziv-Av kirjoitti: how do I answer an incoming call from a C program (or command line, or a python program, for that matter)? One option is to try using oFono. There are some examples using python under test/ in: http://git.kernel.org/?p=network/ofono/ofono.git;a=summary Cheers, Aki ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: oFono
ma, 2010-01-11 kello 08:38 +0100, Denis-Courmont Remi (Nokia-D/Helsinki) kirjoitti: On Saturday 09 January 2010 08:40:29 ext Qole, you wrote: So wait, you're saying we now have a fully open source telephony stack on the N900 that works to make phone calls? Well not exactly. But I'd say not far from it either. First, oFono is signaling middleware; it does not, and never will include its own user interface. The call UI in Maemo5 uses Telepathy, which is open. So all we need is a Telepathy connection manager that uses oFono's D-Bus API. Second, certain things are still to be implemented, such as GPRS (working on it). I'm looking forward to the patches. ;) Last, some stuff might not be do-able, due to interference with the existing N900 cellular stack. SMS reception is one known case (and SMS sending fails too as a side effect). Yeah, SMS and CBS reception are a bit tricky. There can only be a single recipient active at a time on the application processor side. Hence, bootstrapping in the SMS and CBS drivers will fail on the N900 if the default telephony stack is running. You can of course disable the default SMS handler, but then SMSs will no longer be received on the UI, as we're missing that oFono connection manager to Telepathy. Also, the default stack on N900 has some further features related to SMS that are currently missing from oFono. Those features will eventually be added there, too. All and all, oFono should be considered alpha level on Maemo5 at this point. Audio path has not been investigated, but likely would fail too. Right, there is a piece missing in isimodem that sets up the audio path. Currently it's not a big deal, as the default stack will shadow the signaling initiated by oFono and do the Right Thing. Cheers, Aki ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: oFono
to, 2010-01-07 kello 14:04 +0100, Niemi Aki (Nokia-D/Helsinki) kirjoitti: to, 2010-01-07 kello 13:48 +0100, ext Jeff Moe kirjoitti: You should use the isimodem driver in oFono. It is specifically made to support Nokia modems, such as the one on N900. I've been told, and tried my self, and it doesn't work on the N900. It _should_ work out of the box on the N900. In fact, I did some quick packaging of the 0.15 release and just pushed ofono in Fremantle extras-devel. So let's see... Right, ofono is now in extras-devel, and based on some quick testing, it seems to work fine. Note that the isimodem driver is still a work in progress and we don't have some things working properly. Most notably, the SMS or CBS drivers aren't implemented yet. Those are a bit tricky anyway, because they interfere with the regular telephony stack on the device. Cheers, Aki ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: oFono
to, 2010-01-07 kello 13:48 +0100, ext Jeff Moe kirjoitti: You should use the isimodem driver in oFono. It is specifically made to support Nokia modems, such as the one on N900. I've been told, and tried my self, and it doesn't work on the N900. It _should_ work out of the box on the N900. In fact, I did some quick packaging of the 0.15 release and just pushed ofono in Fremantle extras-devel. So let's see... There is some jumping through hoops required to get Phonet over USB working that would allow you to use oFono on the desktop with N900 or any other (recent) Nokia phone connected via USB in PC suite mode. I've been meaning to write a howto for that, and I guess it's high time I actually go and do that. ;) That said, you know far more about it! Do you have a sample modem.conf for N900? And other clues would be appreciated! There's no need for modem.conf on the N900; in fact, my ofono package builds with atmodem and udev disabled. The isimodem driver automagically detects modems via netlink. Cheers, Aki ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: oFono
ke, 2010-01-06 kello 15:26 +0100, ext Jeff Moe kirjoitti: On Wednesday 06 January 2010 08:25:15 you wrote: Hi, I wonder if you really need a laptop for making calls. The program pnatd gives you tty to a modem where you can send AT commands. I'm using it to send USSD codes. Very cool. That looks like it may work, actually, at least for within Maemo. Can you give me a hint as to how to use it though? You should use the isimodem driver in oFono. It is specifically made to support Nokia modems, such as the one on N900. Cheers, Aki ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
[Announce] Intel and Nokia announce open source telephony project (oFono)
Intel and Nokia are pleased to jointly announce the oFono project (http://ofono.org), an open source project for developing an open source telephony solution. oFono.org is a place to bring developers together around designing an infrastructure for building mobile telephony (GSM/UMTS) applications. oFono.org is licensed under GPLv2, and it includes a high-level D-Bus API for use by telephony applications of any license. oFono.org also includes a low-level plug-in API for integrating with Open Source as well as third party telephony stacks, cellular modems and storage back-ends. The plug-in API functionality is modeled on public standards, in particular 3GPP TS 27.007 AT command set for User Equipment (UE). Source code is available on http://ofono.org/downloads and a high-level architecture diagram is available on http://ofono.org/documentation. To join the mailing list, go to http://lists.ofono.org/listinfo/ofono. Nokia and Intel will jointly maintain the oFono project. We'd like to invite all developers to join the oFono.org effort and community. Marcel Holtmann holtm...@linux.intel.com, Intel Open Source Technology Center Aki Niemi aki.ni...@nokia.com, Nokia Devices RD, Maemo Software ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
