Recently, I bought a Teracom datacard (Linktop / LW273) distributed by BSNL
in India. The device was not working out of the box with ModemManager or
ofono as the usb_modeswitch was unable to switch the device from data
interface to modem.
After few trials, I managed to switch the device to modem mode using
usb_modeswitch and then ModemManager was able to detect my device and I was
able to use NetworkManager to make connection. But with ofono, it's not
working even though it's stated on the ofono wiki that generic AT modems
should work out of the box.
Then I tried with different existing ofono drivers by adding udev rule in
/lib/udev/rules/97-ofono.rules and found that the `nokia` driver (which is
used for Nokia CS-10 and CS-17) is working with this device. However, ofono
debug (with OFONO_AT_DEBUG=1) says sms feature is not available for the
device. So I think, this driver needs to be more generic,
In my opinion, ofono should have a generic driver for such AT modems say
`atgen` or similar. I am attaching lsusb output as well as output of udev
monitor. Hope this will help.
Data and Fax call forwarding is not supported in oFono. Currently, oFono triggers the property change only for voice call even when the Data/Fax call forwarding is active.
In one particular case, the Data and Fax property change gets triggered. This patch handles that particular case as well.
Issue observed in call forwarding feature information list parsing.
Due to this, isimodem reports Erase failure to the core even when the
Erase request is successfully handled by the network.
Considering the current logic, this is the fix that can be provided without
changes to other parts of the code. One of the other option is to initialize the status in the calling function
and check its validity before the usage.
TODO | 10 ++++++++++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/TODO b/TODO
index c484871..5806ef0 100644
@@ -507,3 +507,13 @@ Miscellaneous
Owner: Sjur Br��ndeland <sjur.brandeland(a)stericsson.com>
+- Add CELL_DCH state indication support. Add a new optional property to the
+ RadioSettings atom for indicating radio bearer idle/active status. This
+ feature is useful for many types of power management schemes that schedule
+ non-realtime operations over the UMTS radio interface to when the interface is
+ active for other purposes as well, i.e., in CELL_DCH state.
+ Priority: Medium
+ Complexity: C4
+ Owner: Aki Niemi <aki.niemi(a)nokia.com>
I am writing, because I found in software version history, that from
commit 7c2529077cb885d8fb4c50b6696c53c2b4e5d20b" (Release 0.34)
Modem.conf should not be used to configure ofono with
phonesim(phonesim: Don't use modem.conf for phonesim modems")
I want to configure ofono(release 0.36) with phonesim.
How can I do this, if shouldnt use modem.conf?
I will be very grateful, if you help me.
Thank you in advance and Best Regards,
Dial strings can now be as long as 120 digits (not counting '+'). This feature
is going to be needed by the FDN feature.
An FDN may consist of a phone number plus a DTMF string. In order to have the
call succeed when FDN is enabled, both parts need to be provided when making a
call, as a single dial string.
For AT modems the long dial string can be and has to be passed as is to the
modem, for ISI modems the dial string needs to be split into phone number (dest.
address sub block) and DTMF tone (post dest. address sub block) before feeding
it to the modem.
Andras Domokos (3):
common: add long dial string support
voicecall: add long dial string support
isimodem/voicecall: add long dial string support
drivers/isimodem/voicecall.c | 83 +++++++++++++++++++++++++++++++++---------
include/types.h | 2 +-
src/common.c | 38 +++++++++++++++++---
src/common.h | 1 +
src/voicecall.c | 6 ++--
5 files changed, 103 insertions(+), 27 deletions(-)
According to the 3GPP specifications there is some missing points in the SATK DisplayText implementation and I want to propose some API changes here.
1. clear message after delay / wait for user to clear flag
This flag corresponds to the bit 8 of the command qualifier (see ETSI TS 102 223) and indicates how the message should be cleared by the UI.
In the STK agent documentation it's indicated that this flag is handled using different timeout value for the Agent DisplayText method call. But that doesn't seem the case in the code: there is no check of the flag.
For me it's to the UI to handle the way how the message must be cleared and not to ofono. With the current Agent DisplayText method API this is not possible as there is no indication if the message must be cleared after a delay or after a user action. So I want to propose the following change for the STK Agent:
Change void DisplayText(string text, byte icon_id, boolean urgent)
By void DisplayText(string text, byte icon_id, boolean urgent, boolean clear_after_delay)
Where clear_after_delay boolean must be set to '1' for the clear message after delay case and to '0' for the wait for user to clear case.
2. Busy screen
The other missing point in the DisplayText implementation is the case of the busy screen.
According to the sequence 1.2 of the ETSI TS 102 384 we must return a terminal response with the error "screen busy" when the ME is not in the idle screen and if the text message is not urgent. In the current implementation there is no way to return this type of error in the terminal response.
I propose to add a new error code ScreenBusy in the same way of what it's done for GoBack and EndSession event.
Please let me know if you agree with it.
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number: 302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.