patch for more segments of sms
Hi Please review this patch which fixed more segments of sms issue. Also you can find the bug detail information at http://bugzilla.moblin.org/show_bug.cgi?id=8157 Also thanks Yang great help Thanks Zhigang patch_sms Description: patch_sms ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
Re: oFono running on new Freerunner distribution
> This seems to be a peculiarity of the Calypso modem. When using ATD on an > uninitialized port the ATD returns immediately. This means that > dialing/alerting calls can be hung up. However, we use CPI indications and > for some reason the ATD behavior changes when this is used. ATD now only > returns when a call connects, which means we can't hangup dialing/alerting > calls, as you point out. There are a couple of solutions we can try, stay > tuned. I pushed an experimental fix. Let me know if you can now hangup alerting calls. It did not make it into release 0.11 though. Regards, -Denis ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
First release with GPRS support
Hello everyone, I just tagged, pushed and uploaded 0.11 release of oFono. Besides the usual bug fixes in various areas, this comes now with GPRS support. If you happen to have a Ericsson MBM or Option HSO based modem, then you under lucky ones who can try GPRS support. To configure your Primary GPRS Context, you can use the create-context script from within the test directory: create-context You just have to give it the APN from your GPRS network settings. And then list-contexts will show you the configured context. A context needs to only configured once by SIM card. It will be stored on a per SIM card basis and restored after restart. To activate or deactivate the actual connect, activate-context and/or deactivate-context can be used. On success just call list-contexts again and you will see your IP settings. The integration of oFono GPRS support for ConnMan is work in progress and we hope to finish that pretty soon. So the next ConnMan release should be able to talk to oFono for data connections. Regards Marcel ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
Re: oFono running on new Freerunner distribution
Hi Dario, > GREAT It worked!!! :) > It registers in less than one minute! :) > I noticed I don't need to call the Register method of > NetworkRegistration interface but I just need to power up the modem, is > it ok? By default the netreg atom registers you automatically. However it does remember the setting, so if you choose manual registration or deregister from the network it will not attempt to register you the next time you reboot. > I have another question but maybe it's my fault: I noticed if I want to > hangup a call during its "alerting" state, I can't, the other party > continues ringing even if I call the hangup method on the correct path ( > /calypso0/voicecall01). What am I missing? This seems to be a peculiarity of the Calypso modem. When using ATD on an uninitialized port the ATD returns immediately. This means that dialing/alerting calls can be hung up. However, we use CPI indications and for some reason the ATD behavior changes when this is used. ATD now only returns when a call connects, which means we can't hangup dialing/alerting calls, as you point out. There are a couple of solutions we can try, stay tuned. Regards, -Denis ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
Re: Telit 864
Ryan, > so let me ask this then what's involved in getting data modem part working ? > >>Uhhh. This is not modem specific. Are the AT commands common between all modems then ? Aren't there TELIT specific AT commands that need to be considered here ? >>My suggestion is to read up on pppd and its interaction with modems. >>http://en.wikipedia.org/wiki/Point-to-Point_Protocol_daemon >>http://tldp.org/HOWTO/PPP-HOWTO/ I looked at the ppp document. Wondering how what changes are required to make the communication between the pppd and the module ? ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
Re: Patch on unsupported AT command
Hi Denis, > > This is first of all violating the coding style with the indentation on > > the second line of the if, but it is also way too complicated. > > There is actually a reason for this. > > > > > if (info->len == -1 && !strcmp(line, info->terminator) > > return TRUE; > > This part checks for static terminators, like "OK" or "BUSY" or ERROR. We do > whole string comparison here. > > > > > if (info->len > 0 && !strncmp(line, info->terminator, ...)) > > return TRUE; > > This part checks for variable terminators. E.g. +CMS ERROR: XXX. These are > well defined by the standard so we only do a prefix comparison for these. and your point is? I was just going by the pure algorithmic of the if statement to make it actually readable without getting a headache ;) Regards Marcel ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
Re: oFono running on new Freerunner distribution
DJDAS ha scritto: Hi Denis, Hi Dario, Do I have to take the git code or these features are already in the current 0.10 version? This change was made after 0.10 was tagged. So you'll need the git version. OK, I'm pulling from the git, I'll let you know ASAP. Bye, Dario. GREAT It worked!!! :) It registers in less than one minute! :) I noticed I don't need to call the Register method of NetworkRegistration interface but I just need to power up the modem, is it ok? I have another question but maybe it's my fault: I noticed if I want to hangup a call during its "alerting" state, I can't, the other party continues ringing even if I call the hangup method on the correct path ( /calypso0/voicecall01). What am I missing? Thank you very much in advance, bye. Bye, Dario. ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
Re: oFono running on new Freerunner distribution
Hi Denis, Hi Dario, Do I have to take the git code or these features are already in the current 0.10 version? This change was made after 0.10 was tagged. So you'll need the git version. OK, I'm pulling from the git, I'll let you know ASAP. Bye, Dario. ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
Re: oFono running on new Freerunner distribution
Hi Dario, > Do I have to take the git code or these features are already in the > current 0.10 version? This change was made after 0.10 was tagged. So you'll need the git version. Regards, -Denis ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
Re: oFono running on new Freerunner distribution
Denis Kenzior ha scritto: Actually a reference UI for oFono is something we're still lacking. We've all been too busy adding core features. This is something we want to fix... I know, following the list I imagine you're very busy. Maybe I can send you my code (after finishing and cleaning up) if you want a simple C test program... I have just one question: I noticed the Calypso modem registers on the network quite slowly (about 1,5-2 mins after powering up) is this normal? Can we help you in testing/patching the code to achieve faster times (normal phones usually register in seconds). This might have been related to automatic operator scanning. Freerunner is especially slow on this operation. The API was changed recently to disable this. Can you test git HEAD to see if this still happens? Regards, -Denis Do I have to take the git code or these features are already in the current 0.10 version? Bye, Dario ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
Re: oFono running on new Freerunner distribution (was: Palm Pre modem plugin)
Hi Dario, > Well, maybe you missed some of my previous email in this list some time > ago :) > I'm the project leader of a new distribution, called NEOPhysis, for the > Openmoko Freerunner and Niko is the UI team leader. > We are about 10 people in our team and started from scratch creating a > new distribution which differs from the others, approaching the system > concept as an embedded low resources device instead of a micro-desktop > system. Ah, I do remember seeing your previous post. Did not connect the two together though. > I asked in my previous emails if someone of the oFono team could send me > a simple C code because all the test code were written in Python (but > for the telephony part our focus is speed and reliability so its > mandatory to use a C/C++ framework/middleware) but received no answer, Actually a reference UI for oFono is something we're still lacking. We've all been too busy adding core features. This is something we want to fix... > I have just one question: I noticed the Calypso modem registers on the > network quite slowly (about 1,5-2 mins after powering up) is this > normal? Can we help you in testing/patching the code to achieve faster > times (normal phones usually register in seconds). This might have been related to automatic operator scanning. Freerunner is especially slow on this operation. The API was changed recently to disable this. Can you test git HEAD to see if this still happens? Regards, -Denis ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
oFono running on new Freerunner distribution (was: Palm Pre modem plugin)
Denis Kenzior ha scritto: Hi Niko, Nice to hear that. Anyway do not missunderstand, our team is adopting oFono, we are just digging incoming issues with the nogsm part integration!!! Sounds interesting. Let me know if I can be of assistance :) Well, maybe you missed some of my previous email in this list some time ago :) I'm the project leader of a new distribution, called NEOPhysis, for the Openmoko Freerunner and Niko is the UI team leader. We are about 10 people in our team and started from scratch creating a new distribution which differs from the others, approaching the system concept as an embedded low resources device instead of a micro-desktop system. The main focus was not in a "Linux distribution" but in a "Phone with advanced capabilities", so as I follow this project since its born, I proposed to use oFono as the main telephony stack and FSO for the remaining part. As a proof-of-concept I wrote a "ncurses phone app" which uses oFono to do simple calls and ATM I'm able to call a number dialed with the touch screen (yes it's very geek! :P ) and I'm finishing the parsing part to handle the call status to be able to answer calls. I asked in my previous emails if someone of the oFono team could send me a simple C code because all the test code were written in Python (but for the telephony part our focus is speed and reliability so its mandatory to use a C/C++ framework/middleware) but received no answer, OTOH this let me learn using DBUS and oFono APIs so it was not as bad :) We put up a build host which produces even an oFono package for the OpenEmbedded repository and we are very proud to be the first (AFAIK) to use oFono. If you need/want to test oFono on the Freerunner we can provide you the packages built each time you need to. I have just one question: I noticed the Calypso modem registers on the network quite slowly (about 1,5-2 mins after powering up) is this normal? Can we help you in testing/patching the code to achieve faster times (normal phones usually register in seconds). Thank you very much for your great work, good bye. Dario. ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
Re: Patch on unsupported AT command
Hi Marcel, > This is first of all violating the coding style with the indentation on > the second line of the if, but it is also way too complicated. There is actually a reason for this. > > if (info->len == -1 && !strcmp(line, info->terminator) > return TRUE; This part checks for static terminators, like "OK" or "BUSY" or ERROR. We do whole string comparison here. > > if (info->len > 0 && !strncmp(line, info->terminator, ...)) > return TRUE; This part checks for variable terminators. E.g. +CMS ERROR: XXX. These are well defined by the standard so we only do a prefix comparison for these. Regards, -Denis ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
Re: Palm Pre modem plugin
Hi Niko, > Keep in mind I'm speaking about general developers and their interest, > not about organizations, just pointing that *actually* FSO carries > more interests on *some* areas. Yes, I believe we completely agree on this point. oFono's intention was never to be an entire application framework. Our ambitions are only to create the best flexible, customizable and easy to use telephony stack. > May you elaborate about that? May not a close source project use oFono > by calling it's DBus API? Marcel explained some of this very well already. But just to add: oFono takes nearly full control of the modem, so even if it is technically possible to go behind oFono's back and try to do something in a closed/proprietary way, it would not be very practical. This is also something we will actively discourage. > That's one of the reason FSO is modularized. Anyway resource > management in a complex system has to be handled in a central way to > take coherency between subsytems. > Having a middleware doing that is really important, just a case about > the correct way to suspend/resume a device should be not the interest > of a high level software. > Sure, however alternatives exist. For this reason oFono does not dictate any particular approach. In oFono everything is setup as a plugin / driver, so customizing any part or making it integrate with your particular environment should be quite easy. > > Nice to hear that. Anyway do not missunderstand, our team is adopting > oFono, we are just digging incoming issues with the nogsm part > integration!!! > Sounds interesting. Let me know if I can be of assistance :) Regards, -Denis ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
Re: Palm Pre modem plugin
Hi Nicola, > >>The forth and worring is that a developer may be forced to use > >>ofono, as the target device has some closed parts necessary for the os > >>that does not work anymore if you remove ofono and use FSO. > > > > Please do not post these crazy conspiracy theories here. oFono is GPLed for > > exactly this reason. > > May you elaborate about that? May not a close source project use oFono > by calling it's DBus API? see my other email I wrote to explain it a little bit more. Yes, you can write an UI and keep it closed source. This is on purpose. However the D-Bus API is designed in a way that your UI is simple to begin with since we moved all the logic into the daemon. This is the big difference to the FSO GSM part. oFono does the heavy and complex work and all that is 100% GPL. Exactly how it should be. Regards Marcel ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
RE: [PATCH 1/1] emit settings signal before active signal
Hi Martin, > > > --- > > > src/gprs.c | 13 +++-- > > > 1 files changed, 7 insertions(+), 6 deletions(-) > > > > quick question on why? I did remember that Denis and I talked about on > > IRC, but I forgot what our conclusion on the order of these two signals > > was. We should really document this. Do you remember? And please prepare > > a patch that also puts a comment about this in the API documentation. > I can find below log > > (2:02:38 AM) holtmann: Not sure if we need the Settings empty, but for > completion it makes sense. > (2:03:05 AM) holtmann: We might wanna emit the Settings empty before > Activated false, so that ConnMan can clean up the interface before it goes > away. > (2:03:27 AM) denkenz: What's the difference? > (2:03:54 AM) denkenz: strictly speaking we shouldn't even bother for empty > settings > (2:04:05 AM) denkenz: useless signal anyway > (2:04:13 AM) holtmann: Yeah. Just easier for some code path in ConnMan. > (2:04:49 AM) denkenz: holtmann: ok, that's simple enough anyway > > I cannot find the conclusion on active TRUE order. But I think it should the > same with active FALSE. > So ConnMan can setup interface before set network connected. sounds good enough for me. Patch has been applied. However please submit a patch that updates the documentation with the details about the signal order. Regards Marcel ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
Re: [PATCH] Add mpty field to ofono_call
Hi Zhenhua, > A field 'mpty' is added to ofono_call so that we can know > whether the call belongs to multiparty call or not. According > to 27.007 7.18, it is a defined return value of AT+CLCC. > --- > drivers/atmodem/atutil.c |4 +++- > include/types.h |1 + > 2 files changed, 4 insertions(+), 1 deletions(-) patch has been applied. Thanks. Regards Marcel ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
