New Phosh image - first impressions

[MartijnBraam]

Failing to have wifi disabled then ofonoctl wan --connect seems to fail most of the time, or if it works DNS resolution fails on mobile broadband if you later disable wifi.
If modemmanager is in the default runlevel then minimal chance of the 3 ofonoctl commands completing OK, for me even the poweron mostly fails

Interesting, how does ofonoctl wan --connect fail exactly when wifi is enabled? do you get a stacktrace?

[dukla2000]

Not sure there is a *lot* of value in image-hopping for now, for you or for devs.

For now I am happy to stick with pmOS/phosh as I appreciate you pm folk are keeping damn close to the bleeding edge. Is there any way for us to report how close we are to the bleeding edge when making comments? Or just say "last update/upgrade 20 Feb 1900 GMT" or similar?

Failing to have wifi disabled then ofonoctl wan --connect seems to fail most of the time, or if it works DNS resolution fails on mobile broadband if you later disable wifi.
If modemmanager is in the default runlevel then minimal chance of the 3 ofonoctl commands completing OK, for me even the poweron mostly fails

Interesting, how does ofonoctl wan --connect fail exactly when wifi is enabled? do you get a stacktrace?

  I need to retract that line about WiFi enabled causing problems   Just did 3 boots and ran the sequence I listed with no problems!
Now to put modemmanager back in the default runlevel and find out if I need to eat more of my own words!

pmOS/phosh last update/upgrade 20 Feb 1900 UTC

[MartijnBraam]

No there aren't really usable version numbers except those for the seperate components

[dukla2000]

OK, so I have modemmanager in the default runlevel and WiFi disabled (because I have learned how to ssh via USB).

Now I want to get mobile data running but get this:

Code:

DuklaPP:~$ sudo ofonoctl poweron
[sudo] password for demo:
Powered on quectelqmi_0
DuklaPP:~$ sudo ofonoctl online
Brought quectelqmi_0 online
DuklaPP:~$ sudo ofonoctl wan --connect --append-dns
Traceback (most recent call last):
 File "/usr/bin/ofonoctl", line 11, in <module>
   load_entry_point('ofonoctl==0.3.1', 'console_scripts', 'ofonoctl')()
 File "/usr/lib/python3.8/site-packages/ofonoctl/__init__.py", line 240, in main
   action_wan(args.connect, args.resolv)
 File "/usr/lib/python3.8/site-packages/ofonoctl/__init__.py", line 148, in action_wan
   for path, properties in connman.GetContexts():
 File "/usr/lib/python3.8/site-packages/dbus/proxies.py", line 72, in __call__
   return self._proxy_method(*args, **keywords)
 File "/usr/lib/python3.8/site-packages/dbus/proxies.py", line 141, in __call__
   return self._connection.call_blocking(self._named_service,
 File "/usr/lib/python3.8/site-packages/dbus/connection.py", line 652, in call_blocking
   reply_message = self.send_message_with_reply_and_block(
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "GetContexts" with signature "" on interface "org.ofono.ConnectionManager" doesn't exist

After the poweron Chats throws its toys out the cot as the modem has gone away and never recovers. The dialler/phone calls recover after I restart modemmanager.

Then again I have yet to work out how to send an SMS using Chats - it says hit the + at the top which only opens a search bar ...

Or more realistically how to send an SMS? ofonoctl no longer cuts it

PHP Code:

DuklaPP:~$ ofonoctl sms +447771234567 -m "Hello world"
usage: ofonoctl [-h] {list,poweron,poweroff,online,offline,operators,wan} ...
ofonoctl: error: argument action: invalid choice: 'sms' (choose from 'list', 'poweron', 'poweroff', 'online', 'offline', 'operators', 'wan') 


I think for my purposes best to take modemmanager out of the default runlevel anyway and start it after I get the mobile data up and running.

[MartijnBraam]

Oh yeah ofonoctl in the binary repository is a version behind so it's missing the SMS command.

The other error is ofono not being able to set up mobile data, I'm not sure what the cause of that is but sometimes rebooting the whole thing helps.

[pjsf]

Thanks, just made my first (scratchy) pinephone call thanks to this thread and this tweet:
https://twitter.com/mozzwald/status/1229974218529529856

[dukla2000]

See pmOS post here.

I advise everyone to update their system.

Code:

apk update && apk upgrade --available

(note the "--available" argument)

We now have Qt 5.14.1 in postmarketOS!

First impression - seems a bit faster/smoother to me

[PureTryOut]

See pmOS post here.

First impression - seems a bit faster/smoother to me

That is nice, but I fail to see how that is related to Phosh.

[Nooblife]

Worked great What does the --available argument do? Should i use it every time i upgrade? and on all distros?

[dukla2000]

That is nice, but I fail to see how that is related to Phosh.

I guess you should know: for some reason I had some kind of 9999 placeholder installed and it did upgrade to 5.14.1