From: Pavel Machek <pavel@ucw.cz>
To: ofono@ofono.org
Subject: Re: Quectel EC25 vs. ofonod 1.29 (on PinePhone)
Date: Thu, 08 Apr 2021 20:34:47 +0200 [thread overview]
Message-ID: <20210408183447.GA7673@duo.ucw.cz> (raw)
In-Reply-To: <20210407235127.2848.76714@ml01.vlan13.01.org>
[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]
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. Another was trying to get WWAN set up correctly.
>
> Ubuntu Touch messily applies QMI call patches to oFono in a branch on our GitHub repository of it: https://github.com/ubports/ofono/tree/xenial_-_edge_-_pine. I'll send another reply once I know where Plasma Mobile gets its builds. Hopefully they've got a bit cleaner commit log.
>
Thank you for the information. I assume... even if I fixed
modem<->ofono communication, there would be still nontrivial work
involved getting the audio to work... right?
> You will have problems with the modem further than you're having now, though: for one, it likes to fall off of USB every now and again when waking from sleep. We're currently investigating this issue since all PinePhone operating systems have devised workarounds that are far more complicated than the issue seems to warrant. If you want to talk more PinePhone development, I recommend you join us at #pinedev on freenode or #pine-dev:matrix.org
I can do irc.
Best regards,
Pavel
--
http://www.livejournal.com/~pavelmachek
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2021-04-08 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 22:56 Quectel EC25 vs. ofonod 1.29 (on PinePhone) Pavel Machek
2021-04-07 23:51 ` dalton
2021-04-08 18:34 ` Pavel Machek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210408183447.GA7673@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).