Incoming sms problem on Motorola Droid 4

Hi! I have problems with incoming SMS. ofono tries to use +CNMI=1,2,2,1,0 > AT+CNMI=? < +CNMI: (0,1,2),(0,1,2,3),(0,2),(0,1,2),(0,1) < OK ofonod[3070]: drivers/atmodem/sms.c:build_cnmi_string() ofonod[3070]: drivers/atmodem/sms.c:construct_ack_pdu() > AT+CNMI=1,2,2,1,0 < OK ofonod[3070]:

AT commands in U0001AT+FOOBAR form

Hi! I have a motorola droid 4 here; it uses gsm 07.10 multiplex. Over that, there are AT commands, but prefixed with serial numbers, in U0001AT+FOOBAR form. Corresponding reply then has U0001 prefix, too. Has anyone seen that before? Any hints for me trying to add the support? Best regards,

Re: Incoming sms problem on Motorola Droid 4

On Fri 2018-05-11 05:39:26, Tony Lindgren wrote: > * Pavel Machek <pa...@ucw.cz> [180511 12:36]: > > Is there way to power cycle the modem without reboot? That should make > > the debugging... less bad. > > Yeah you can currently do: > > # rmmod ohci-platfo

Re: Voice calls over qmi was Re: Incoming sms problem on Motorola Droid 4

Hi! > nice to hear, somebody else is using it. > > The voicecall driver needs to be refactored as Denis already pointed > out on the mailinglist before it can go upstream. > > The original idea of the voice_generated.c/h files was to create a > prototype how qmi generated files should look like

[rfc] Fix incoming sms on Droid 4 was Re: Incoming sms problem on Motorola Droid 4

Hi! > > Is this actually an AT command modem or one of those modems where AT > > commands were only bolted on for carrier certification? Does it > > support QMI > > or something maybe? > Ok, so ... this is complex. And maybe this is one of "those" modems. > There's USB

Re: Incoming sms problem on Motorola Droid 4

Hi! > >> I have problems with incoming SMS. ofono tries to use +CNMI=1,2,2,1,0 > >>> AT+CNMI=? > >> < +CNMI: (0,1,2),(0,1,2,3),(0,2),(0,1,2),(0,1) > >> < OK > >> ofonod[3070]: drivers/atmodem/sms.c:build_cnmi_string() > >> ofonod[3070]: drivers/atmodem/sms.c:construct_ack_pdu() > >>>

Re: Incoming sms problem on Motorola Droid 4

Hi! > > > AT+CNMI=1,2,2,1,0 > > < OK > Well you can try to see what Android is doing for SMS with: > > # echo 0x7fff > /sys/module/ts27010mux/parameters/debug_level > # dmesg | grep ts27010 | grep AT > > To send SMS, looks like Android RIL first does: > > 2 AT+CMGS=327 where 327 seems to

Re: AT commands in U0001AT+FOOBAR form

Hi! > >I have a motorola droid 4 here; it uses gsm 07.10 multiplex. Over > >that, there are AT commands, but prefixed with serial numbers, in > >U0001AT+FOOBAR form. Corresponding reply then has U0001 prefix, too. > >Has anyone seen that before? Any hints for me trying to add the > >support? > >

Re: Incoming sms problem on Motorola Droid 4

On Tue 2018-05-08 17:08:25, Denis Kenzior wrote: > Hi Pavel, > > On 05/08/2018 04:51 PM, Pavel Machek wrote: > >Hi! > > > >I have problems with incoming SMS. ofono tries to use +CNMI=1,2,2,1,0 > > > >>AT+CNMI=? > >< +CNMI: (0,1,2),(0,1,2,3),(

Re: Incoming sms problem on Motorola Droid 4

Hi! > >PDU Len 2, strlen 4 > >PDU last char 48 > >^ZCNMA=1,2 > > >^ZCNMA=1,2 > >< +CMS ERROR: 304 > >ofonod[3057]: CNMA acknowledgement failed: Further SMS reception is > >not guaranteed > >< +CIEV: 1,4 > > > >Modem does not like our CNMA acknowledgement. AFAICT, we are sending > > >

[PATCH] simple fixes

Fix typo in location-reporting-api.txt. AFAICT, at_cmt_notify() calls ofono_error even in case stuff is okay. Fix that. Move debug print to more useful place in setup_gobi(). Explain "delivery report" parameter in send-sms. diff --git a/doc/location-reporting-api.txt

Re: Incoming sms problem on Motorola Droid 4

Hi! > > > > > AT+CNMI=1,2,2,1,0 > > > > < OK > > > > > Well you can try to see what Android is doing for SMS with: > > > > > > # echo 0x7fff > /sys/module/ts27010mux/parameters/debug_level > > > # dmesg | grep ts27010 | grep AT > > > > > > To send SMS, looks like Android RIL first does: >

Re: Incoming sms problem on Motorola Droid 4

Hi! > >>>If I attempt to do AT+CNMA=1, AT+CNMA=0 or just plain At=CNMA, it does > >>>not like that, either, but with +CMS ERROR: 500. > >> > >>CNMA=1 is required to work in PDU mode according to 27.005 btw. How about: > >> > >>window.open(); > >>window.throw(modem); > > > >Heh :-). Well, there

Re: Incoming sms problem on Motorola Droid 4

Hi! > >> If I attempt to do AT+CNMA=1, AT+CNMA=0 or just plain At=CNMA, it does > >> not like that, either, but with +CMS ERROR: 500. > > > > CNMA=1 is required to work in PDU mode according to 27.005 btw. How > > about: > > > > window.open(); > >

Re: Voice calls over qmi was Re: Incoming sms problem on Motorola Droid 4

Hi! > > It looks like the QMI voicecall driver is just a stub with no operations > actually implemented. > > I hope I'm not stealing their thunder, but Alexander Couzens at sysmocom > seems to be working on implementing it [0]. Last fall, I had > incoming/outgoing calls in oFono working on my

Re: Incoming sms problem on Motorola Droid 4

Hi! > > > And that's probably the incoming SMS size. But I don't see > > > anything for what actually reads the incoming SMS. > > Hmm it occured to me that maybe the incoming messages are read > using QMI over USB. > > > That seems to be standard message > >

Voice calls over qmi was Re: Incoming sms problem on Motorola Droid 4

Hi! > > More explanation needed it seems: > > > > I can already do USB with AT commands, no multiplexer needed. We'd > > actually prefer to go over serial (with multiplexer), because USB > > needs to be powered down in idle, and you still need communication > > ovre serial to know that wakeup of

Re: Modem not detected by oFono

On Sat 2018-06-09 15:37:18, Davide Depau wrote: > Hello, > I just built oFono on Arch Linux from git [1]. I made sure no other program > was using the modem (Huawei ME906s LTE M.2 Module) and started oFono. The > modem is not recognized and I get no output in logs: > > systemd[1]: Starting

Re: place to intercept BT audio packets?

On Wed 2018-08-29 15:01:50, d...@rivaretica.com wrote: > New to ofono: looking for documentation/pointers that can inform about the > best point in ofono to intercept Bluetooth audio packets from/to headset to > implement custom audio processing (and does audio stream even thread through >

Re: [RFC PATCH] new gemalto plugin

Hi! > > Also, there are security and interference aspects to consider. One can > > send some AT command that interferes with the functioning of an atom > > driver for example and then your entire system breaks. Trust me, it is > > just not a good idea. If you want to shoot yourself in the

Re: [PATCH 1/6] coex: adding coex interface doc for coex api

Hi! > +*header for params > += > +string > + uint16 MobileNetworkCode [readonly, optional] > + Contains the MNC of the cell. > +string > + uint16 MobileCountryCode [readonly, optional] > + Contains the MCC of the cell. Confused.

ofono fails to compile on gcc-6.3

Hi! I'm getting this: CC drivers/rilmodem/network-registration.o drivers/rilmodem/network-registration.c:40:32: error: unknown option after ‘#pragma GCC diagnostic’ kind [-Werror=pragmas] #pragma GCC diagnostic ignored "-Wrestrict" cc1: error: unrecognized command line option

Re: [PATCH 3/3] sim800: adding documentation to inform about the udev rule the user must add

On Tue 2018-09-18 22:36:27, ClémentViel wrote: > From: clem > > --- > doc/sim800-modem.txt | 7 +++ > 1 file changed, 7 insertions(+) > create mode 100644 doc/sim800-modem.txt > > diff --git a/doc/sim800-modem.txt b/doc/sim800-modem.txt > new file mode 100644 > index 000..6731879 >

[PATCH] Fix error handling in at_cmt_notify()

at_cmt_notify() calls ofono_error even in case stuff is okay. Fix that. diff --git a/drivers/atmodem/sms.c b/drivers/atmodem/sms.c index 68b89862..217971e7 100644 --- a/drivers/atmodem/sms.c +++ b/drivers/atmodem/sms.c @@ -440,6 +436,8 @@ static void at_cmt_notify(GAtResult *result, gpointer

[PATCH] Fix typo in location-reporting-api.txt.

Fix typo in location-reporting-api.txt. diff --git a/doc/location-reporting-api.txt b/doc/location-reporting-api.txt index 21e346d4..ff0a35dc 100644 --- a/doc/location-reporting-api.txt +++ b/doc/location-reporting-api.txt @@ -13,7 +13,7 @@ Methods dict GetProperties()

[PATCH] Better help for delivery reports

Explain "delivery report" parameter in send-sms. diff --git a/test/send-sms b/test/send-sms index 98808aaf..cabe0652 100755 --- a/test/send-sms +++ b/test/send-sms @@ -6,6 +6,7 @@ import dbus if len(sys.argv) < 4: print("Usage: %s [modem] " %\

[PATCH] Move debug print to more useful place

Move debug print to more useful place in setup_gobi(). index ff5d41af..a4b18488 100644 --- a/plugins/udevng.c +++ b/plugins/udevng.c @@ -233,10 +233,11 @@ static gboolean setup_gobi(struct modem_info *modem) } } + DBG("qmi=%s net=%s mdm=%s gps=%s diag=%s", qmi,

Motorola motmdm support

Hi! Motorola phones use "interesting" setup. There's qmi and "normal" (but very buggy) AT interface on them. Unfortunately that uses USB and uses too much power (which is a problem on phone). Plus there's /dev/motmdm1, motmdm3 and motmdm9, multiplexed over serial line. It uses subset of AT

Trouble compiling ... Re: ofono fails to compile on gcc-6.3

Hi! On Tue 2018-09-04 11:44:16, Pavel Machek wrote: commit f13047bf9334795b89b09fef3a051e7dfbe207f2 Author: Denis Kenzior Date: Thu Dec 27 18:19:31 2018 -0600 stktest: Fix immediate response test I have updated to recent ofono -- and the problem is still there: > > CC d

Re: Motorola motmdm support

Hi! > Oh, I think I forgot to answer your question regarding PM, > there's nothing that the user space needs to except to avoid > polling the /dev/motmdm* devices unnecessarily. And to type > AT+SCRN=0 on /dev/motmdm1 when no notifications for signal > strength and network status are needed. Is

[PATCH] document getting of ell, point people at useful docs

Currently there's README and HACKING... each describing part of what needs to be done to build ofono. Provide some cross-links and fix build example. diff --git a/HACKING b/HACKING index 15ea291..b1bd599 100644 --- a/HACKING +++ b/HACKING @@ -45,7 +45,8 @@ bootstrap-configure since it could

Re: Motorola motmdm support

Hi! And thanks for a quick replies. > >There's qmi and "normal" (but very buggy) AT interface on > >them. Unfortunately that uses USB and uses too much power (which is a > >problem on phone). > > > >Plus there's /dev/motmdm1, motmdm3 and motmdm9, multiplexed over > >serial line. > > Kernel

Re: Trouble compiling ... Re: ofono fails to compile on gcc-6.3

Hi! > >> CC drivers/rilmodem/network-registration.o > >> drivers/rilmodem/network-registration.c:40:32: error: unknown option > >> after ‘#pragma GCC diagnostic’ kind [-Werror=pragmas] > >>#pragma GCC diagnostic ignored "-Wrestrict" > >>cc1: error: unrecognized command line option

[PATCH] fix compilation on gcc-6.3

gcc-6 fails to compile ofono due to #pragma directives. Limit them to gcc versions where they are needed. diff --git a/drivers/rilmodem/call-forwarding.c b/drivers/rilmodem/call-forwarding.c index eb65c23..231a06c 100644 --- a/drivers/rilmodem/call-forwarding.c +++

Re: [PATCH] sim: Sim PIN1 cache upon modem reset/crash

On Wed 2018-12-12 08:59:34, Giacinto Cifelli wrote: > No, absolutely not! > It is forbidden to do this by the 3GPP! Checking if 3GPP is allowed to make laws in this country no. :-) I'm not sure if it makes sense by default, but... I don't think 3GPP has or should have power over ofono

Re: [PATCH] sim: Sim PIN1 cache upon modem reset/crash

On Thu 2018-12-13 23:01:45, Pavel Machek wrote: > Hi! > > > If a firmware crashes on a device with a PIN lock and the user was browsing > > the internet at that time, it would be quite intrusive to interrupt the user > > and prompt them for a PIN (after all, they

Re: [PATCH] sim: Sim PIN1 cache upon modem reset/crash

Hi! > If a firmware crashes on a device with a PIN lock and the user was browsing > the internet at that time, it would be quite intrusive to interrupt the user > and prompt them for a PIN (after all, they already entered the PIN). > Additionally, if the PIN was stored for just this case and the

Re: [PATCH 2/3] coex: coex agent implementation

Hi! > + dbus_message_iter_init_append(reply, ); > + > + dbus_message_iter_open_container(, DBUS_TYPE_ARRAY, > + OFONO_PROPERTIES_ARRAY_SIGNATURE, > + ); > + > + value = coex->bt_active; > +

Re: [PATCH 1/3] coex: Adding documetation for coex interface

Hi! > +LTE Coexistence hierarchy > +=== > + > +Service org.ofono > +Interfaceorg.ofono.IntelLTECoex* > +Object path [variable prefix]/{modem0,modem1,...} The interface should be generic, not Intel-specific in the end, right? > + a(a{sv})

Re: Motorola motmdm support

On Mon 2018-12-31 14:23:29, Tony Lindgren wrote: > * Pavel Machek [181231 21:54]: > > Is it possible that epoll() does not work properly with /dev/motmdm*? > > I am debugging weird problems with ofonod, and that would be an > > explanation... > > > > epoll.poll()

Re: sd-bus

Hi! > would it be interesting to port ofono from GDBus, which comes with the > huge GLib dependency, to sd-bus? > It is a lot of work, but the main question is whether we can assume > that systemd is deployed enough to allow the switch. As someone said, ell already has dbus support. But

Re: Motorola motmdm support

Hi! > >>How are you handling data connections? PPP? Or is there some other protocol > >>to transfer packets back and forth? > > > >All the data connections in this case are done using QMI over USB. > > > >And that probably explains why I have not seen any data related > >stuff on ts 27.010. > >

Re: Motorola motmdm support

Hi! > Motorola phones use "interesting" setup. > > There's qmi and "normal" (but very buggy) AT interface on > them. Unfortunately that uses USB and uses too much power (which is a > problem on phone). > > Plus there's /dev/motmdm1, motmdm3 and motmdm9, multiplexed over > serial line. > > It

Re: [PATCH] document getting of ell, point people at useful docs

On Sat 2018-12-29 23:47:04, Pavel Machek wrote: > Currently there's README and HACKING... each describing part of what > needs to be done to build ofono. > > Provide some cross-links and fix build example. Any news about this and parent patch? I don't see them in https://git.kernel

Re: [PATCH 2/6] sim: Added new properties to simmanager for DSSA

On Wed 2019-03-27 17:39:12, Antara Borwankar wrote: > Adding two new properties to sim manager interface to handle > dual SIM single active use case. > > CardSlotCount [readonly] > Contains the count of number of SIM card slots available. > > ActiveCardSlot [readwrite] > Contains the index of

Re: Test clients for ofono: rfone, Unicsy Demo

Hi! > > >SMS messages should be handled in similar way e-mails currently are -- > > >stored in maildir or mailbox formats, and accessible by common email > > >clients. Access by two or more clients at the same time should be > > >possible. Of course, special GUI client should be provided to work

Manually packetizing data for motorola modem was Re: Test clients for ofono: rfone, Unicsy Demo

Hi! I'm still fighting with SMS sending on Motorola Droid 4. Yes, its kernel driver is somehow interesting... and work in progress. If packets are split correctly, SMS sending works. ofonod[2900]: OutSMS: > AT+GCMGS=\r ofonod[2900]: OutSMS: > 3100098106343401F3A70A73F45B4E07D1CB733A

Re: Droid 4 modem support in kernel & ofono

Hi! > > Ok, so I got calls and smses somehow working in kernel ... which > > is really all I need. > > Nice :) > > I think the SIM card reading and writing should be doable > using dlci10 /dev/motmdm10 for AT+CRSM calls.. Might be. Sorry, this is outside of my area of interest, because LTE

Re: Test clients for ofono: rfone, Unicsy Demo

Hi! > > What ofono client are you using for development.. and for real usage > > on a cellphone? > > > > There are scripts in test/ which are suitable for early development, > > but not really for real use or 'does everything work?' testing. > > > > Anyway, I created some. > > > > RFone --

Re: Reason ofono flakeyness

Hi! > > > OK I think I found the reason fo ofono doing a variable > > > number of commands on start-up with sudo test/enable-modem. > > > > > > There seems to be some kind of issue with handling of > > > commands and results in ofono. See the logs below for > > > test/enable-modem. The AT+SCRN=0

Reliable SMS receive

Hi! I see that great care is taken not to lose outgoing message: " Persisting of outgoing SMS messages. Whenever oFono is asked to send an SMS message, it adds it to an internal queue and persists it on disk. The queue is persistent across reboots of oFono and allows to queue SMS messages even

Better help text for dial-number

Better help text for "dial-number". Without details, user may be tempted to pass 0|1 (as send-sms uses) or true|false. diff --git a/test/dial-number b/test/dial-number index fe5adad3..4c0ee142 100755 --- a/test/dial-number +++ b/test/dial-number @@ -4,7 +4,8 @@ import sys import dbus if

Droid 4 modem support in kernel & ofono

Hi! Ok, so I got calls and smses somehow working in kernel ... which is really all I need. I pushed the tree to g...@github.com:pavelmachek/ofono.git , branch d4... But I had to do some "rather interesting" hacks. D4 modem expects packets and current kernel drivers rely on write() boundaries and

Re: [PATCH] document getting of ell, point people at useful docs

Hi! > > diff --git a/README b/README > > index 45bb2e9..04a50a5 100644 > > --- a/README > > +++ b/README > > @@ -16,11 +16,14 @@ To configure run: > > ./configure --prefix=/usr --mandir=/usr/share/man \ > > --sysconfdir=/etc --localstatedir=/var > > > > -Configure

Re: [PATCH v2] qmimodem: support wake on SMS receive

Hi! > Some modems, like Quectel EC25, support waking the host platform from a > suspend state upon an SMS reception. Current SMS handling configures the > modem to not save incoming messages. On platforms where the modem's > interfaces (eg, cdc-wdm, wwan, etc) disconnect on suspend and

Re: [rfc] Motorola Droid 4 voice: integrate into atmodem or completely separate?

Hi! > >Droid 4 has ... something similar to AT commands, but not quite. For > >voice calls, I modified atmodem... but I guess there are so many > >changes that creating separate motorolamodem/voicecall.c might be > >an option? (send_clcc() changes make sense as a cleanup, and were sent > >in

[rfc] Motorola Droid 4 voice: integrate into atmodem or completely separate?

Hi! Droid 4 has ... something similar to AT commands, but not quite. For voice calls, I modified atmodem... but I guess there are so many changes that creating separate motorolamodem/voicecall.c might be an option? (send_clcc() changes make sense as a cleanup, and were sent in separate mail.)

Re: [rfc] Motorola Droid 4 voice: integrate into atmodem or completely separate?

Hi! > >>The send_clcc change does sort of make sense separately. > > > >Yes, you should have it separate in your inbox ;-). If not, let me > >know and I'll resend. > > Doesn't look like I do? You should have now. :-). I pushed updated sources to

atmodem: introduce send_clcc() to reduce code duplication

Reduce code duplication by introducing send_clcc function. --- > > Yes, you should have it separate in your inbox ;-). If not, let me > > know and I'll resend. > > Doesn't look like I do? sorry about that. Here you go... Best regards,

Motorola Droid 4 SMS sending

Hi! Motorola Droid 4 runs packet protocol over serial... and its kernel driver requires explicit "write()" boundaries at places where packet boundaries should be. So I can send SMS using low level g_at... functions (that are not normally accessible), but not using g_at_chat_send(). If anyone

Re: [PATCH 1/4] test: process-context-settings: use ip instead of ifconfig/route

On Thu 2019-07-18 13:49:34, Martin Hundebøll wrote: > --- > test/process-context-settings | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/test/process-context-settings b/test/process-context-settings > index 1d30b30d..a536a771 100755 > ---

Re: [PATCHv2 4/4] doc: document power-event signals for quectel Hardware API

On Fri 2019-07-19 12:19:14, Martin Hundebøll wrote: > --- > > Changes since v1: > * new patch split out from PATCHv1 7/7 > > doc/quectel-hardware-api.txt | 19 +++ > 1 file changed, 19 insertions(+) > > diff --git a/doc/quectel-hardware-api.txt b/doc/quectel-hardware-api.txt >

Re: [PATCHv3 2/4] doc: add documentaion for Quectel hardware API

Hi! > >+Hardware hierarchy > >+== > >+ > >+Service org.ofono > >+Interface org.ofono.quectel.Hardware > >+Object path /{device0,device1,...} > >+ > >+Methods array{string,variant} GetProperties > >+ > >+Returns hardware properties for

Re: [PATCH] atmodem: CGDCONT handling for cid 0

On Fri 2019-09-27 12:16:32, Antara Borwankar wrote: > Added handling for cid 0 in +CGDCONT callback. > --- > drivers/atmodem/gprs.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/atmodem/gprs.c b/drivers/atmodem/gprs.c > index 16f4927..defbba0 100644 > ---

Re: [PATCH v2 1/1] ublox: rework device initialization sequence

On Tue 2019-09-24 18:01:26, Jonas Bonn wrote: > uBlox devices present their USB interfaces well before those interfaces > are ready to respond to any commands. The documentation says to monitor > the 'greeting text' to detect readiness, but this 'greeting text' is not > actually specified for any

Missing documentation for SimManager property writing?

Hi! In doc/sim-api.txt, there are some properties marked read/write, but I don't see documented way to change those properties. Someone may want to fix that up. Best regards, Pavel -- (english)

Supporting modem in Droid 4

Hi! Two months I sent patch for Droid 4 support in ofono: https://www.mail-archive.com/ofono@ofono.org/msg19590.html I got no replies. Could I get some comments? Should I try to resend? Best regards, Pavel -- (english)

Re: [PATCH v3] Support weird modem in Motorola Droid 4

Hi! > > This is basic support for modem in Droid 4, accessed over > > ttyUSB4. That interface is unfortunately quite broken, so we need to > > force very specific SMS mode. > > > > Can you separate this into at least a couple of patches per our patch > submission guidelines? See HACKING,

Re: [PATCH v3] Support weird modem in Motorola Droid 4

Hi! > On 9/10/20 8:05 AM, Pavel Machek wrote: > > This is basic support for modem in Droid 4, accessed over > > ttyUSB4. That interface is unfortunately quite broken, so we need to > > force very specific SMS mode. > > > > Can you separate this into at least

[PATCH 1/3] droid 4: add special handling required for voice calls and SIM

Droid 4 modem is "special" (aka broken) so it seems to need a bit of error handling. --- drivers/atmodem/sim.c | 1 + drivers/atmodem/vendor.h| 1 + drivers/atmodem/voicecall.c | 4 3 files changed, 6 insertions(+) diff --git a/drivers/atmodem/sim.c b/drivers/atmodem/sim.c index

[PATCH 2/3] droid 4: special handling for SMSes

Droid 4 modem is "special" (aka broken) so and getting incoming SMSes to work is quite tricky. This should get it right. --- drivers/atmodem/sms.c | 15 --- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/drivers/atmodem/sms.c b/drivers/atmodem/sms.c index

[PATCH 3/3] droid 4: Add probing.

. + * Copyright (C) 2009 Collabora Ltd. All rights reserved. + * Copyright (C) 2020 Pavel Machek. All rights reserved. + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2 as + * published by the Free Software

[PATCH v3] Support weird modem in Motorola Droid 4

file mode 100644 index ..4e048dbb --- /dev/null +++ b/plugins/droid.c @@ -0,0 +1,226 @@ +/* + * + * oFono - Open Source Telephony + * + * Copyright (C) 2008-2011 Intel Corporation. All rights reserved. + * Copyright (C) 2009 Collabora Ltd. All rights reserved. + * Copyright (C) 2020 P

Re: Supporting modem in Droid 4

Hi! > > Two months I sent patch for Droid 4 support in ofono: > > > > https://www.mail-archive.com/ofono@ofono.org/msg19590.html > > > > I got no replies. Could I get some comments? Should I try to resend? > > Please resend. Looks like they got buried in a thread and I must have missed >

Re: ofono enable-modem fails with dbus.exceptions.DBusException: org.ofono.Error.Failed: Operation failed

On Wed 2020-10-14 20:50:51, zoltanma...@pm.me wrote: > I'm trying to make Ubuntu 20.04 recognise AirPods Pro as a headset (not just > as headphones). I tried to follow the instructions in this AskUbuntu answer: >

Re: [PATCH 2/3] droid 4: special handling for SMSes

Hi! > And here per item M1. > > Also, I had to resolve a minor conflict manually. Please rebase against git > HEAD when sending out patches. > > Applied, thanks. Thank you! Pavel -- (english)

Re: AT modem on Droid 4: where is my sms?

Hi! > >> I have problems with getting CNMA to work, so I'm exploring other > >> possibilities. Apparently ofono should be able to work without > >> that.. but is it working properly? > >> > >> ofonod[5218]: < \r\n+CIEV: 1,3\r\n > >> ofonod[5218]: < \r\n+CIEV: 1,4\r\n > >> ofonod[5218]: <

Re: AT modem on Droid 4: where is my sms?

Hi! > >I have problems with getting CNMA to work, so I'm exploring other > >possibilities. Apparently ofono should be able to work without > >that.. but is it working properly? > > > >ofonod[5218]: < \r\n+CIEV: 1,3\r\n > >ofonod[5218]: < \r\n+CIEV: 1,4\r\n > >ofonod[5218]: < \r\n+CMTI: "ME",2\r\n

AT modem on Droid 4: where is my sms?

Hi! I have problems with getting CNMA to work, so I'm exploring other possibilities. Apparently ofono should be able to work without that.. but is it working properly? ofonod[5218]: < \r\n+CIEV: 1,3\r\n ofonod[5218]: < \r\n+CIEV: 1,4\r\n ofonod[5218]: < \r\n+CMTI: "ME",2\r\n ofonod[5218]:

Re: AT modem on Droid 4: where is my sms?

On Fri 2020-07-31 12:07:50, Pavel Machek wrote: > Hi! > > I have problems with getting CNMA to work, so I'm exploring other > possibilities. Apparently ofono should be able to work without > that.. but is it working properly? > > ofonod[5218]: < \r\n+CIEV: 1,3\r\n >

[PATCH] Support weird modem in Motorola Droid 4

/null +++ b/plugins/droid.c @@ -0,0 +1,226 @@ +/* + * + * oFono - Open Source Telephony + * + * Copyright (C) 2008-2011 Intel Corporation. All rights reserved. + * Copyright (C) 2009 Collabora Ltd. All rights reserved. + * Copyright (C) 2020 Pavel Machek. All rights reserved. + * + * This program i

[PATCH v2] Support weird modem in Motorola Droid 4

ns/droid.c b/plugins/droid.c new file mode 100644 index ..4e048dbb --- /dev/null +++ b/plugins/droid.c @@ -0,0 +1,226 @@ +/* + * + * oFono - Open Source Telephony + * + * Copyright (C) 2008-2011 Intel Corporation. All rights reserved. + * Copyright (C) 2009 Collabora Ltd. All rights reserved.

Re: Weird Droid 4 modem protocol and a way to support it

Hi! > >I'd really like to get support for Droid 4 modem... unfortunately it > >is quite special. Few words about Droid 4 modem protocol: > > > > >I'm not sure what is the best way to support it. I was not able to get > >atchat.c to work with it (and I don't think it is quite suitable), so > >I

Re: Weird Droid 4 modem protocol and a way to support it

Hi! > >I'd really like to get support for Droid 4 modem... unfortunately it > >is quite special. Few words about Droid 4 modem protocol: > > > > > > > > >I'm not sure what is the best way to support it. I was not able to get > >atchat.c to work with it (and I don't think it is quite suitable),

Weird Droid 4 modem protocol and a way to support it

+ * Copyright (C) 2008-2011 Intel Corporation. All rights reserved. + * Copyright (C) 2020 Pavel Machek + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2 as + * published by the Free Softwar

Re: Change code and commit process

On Mon 2020-11-23 16:45:17, Jupiter wrote: > How to commit code change, who should I contact for approving code >change? See HACKING file in your copy of ofono...? Best regards, Pavel -- http://www.livejournal.com/~pavelmachek

Re: Forking on MMSD

Hi! > > > This is not ofono I am forking, merely MMSD. > > > > So first, sorry, I was confused, I assumed mmsd is part of ofono. > > No worries! To the best of my knowledge, mmsd is a part of ofono? That > is why I have tried to submit my patches on the Ofono Mailing list > several times.

Re: Quectel EC25 vs. ofonod 1.29 (on PinePhone)

Hi! > > I can only speak for Ubuntu Touch and Plasma Mobile, but we're using the QMI > interface provided by the EG25G. We had more trouble trying to use the AT > interface than it seemed worth working on. One problem was, indeed, having > trouble receiving the RING indication reliably.

Quectel EC25 vs. ofonod 1.29 (on PinePhone)

Hi! I'm fighting with Quectel EG25 modem (included in PinePhone). AT+CGMM EG25

Re: Forking on MMSD

Hi! > In talking to the Debian Developer Mr. Federico Ceratto, since I have > been unable to get a hold of the Ofono Maintainers, the best course of > action for packaging mmsd into Debian is to simply fork the project and > submit my version upstream for packaging in Debian. My repository is >

Re: Forking on MMSD

Hi! > This is not ofono I am forking, merely MMSD. So first, sorry, I was confused, I assumed mmsd is part of ofono. I guess Marcel Holtmann is right person to talk to. I put him in Cc list. I'm also Ccing Denis and phone-devel list. > and asking about how to contact the ofono maintainers in

Re: Not able to do anything with incomng call

Hi! > Not sure if I'm at the right place for these kinds of questions. Sorry if > I'm not. > > I'm trying to automate test calls and I'm able to set up a call but not > able to see incoming calls and reject or pick them up. > I'm using a Raspberry Pi Zero 2 W with the newest raspbian 32bit lite.