Closed AndyM48 closed 1 year ago
So I installed the newish firmware using fwupd. Now I have:
AT+GETSWREV
0.7.2
OK
AT+GETADSPVER
EG25GGBR07A08M2G_30.006.30.006
OK
The 0.7.2 is the latest version available to fwupd, but I am not sure if the firmware version number is correct. Can someone confirm please?
If you mean the ADSP firmware version, that should be fine. There's one newer version (30.007.30.007) mentioned in the 0.7.3 release notes, but if 30.006.30.006 is working fine for you, you don't necessarily have to update. Fwupd won't update the ADSP firmware either way, that's a manual process (as described in the release notes).
Not really, the firmware version id does not seem to have changed. Is that correct?
The reason I ask is that the firmware version does not seem to have changed, and after the fwupd my calls have frankly stopped working altogether. SMS work fine MMS does not work, calls in are not recognised, calls out fail with
Apr 01 15:47:44 pinephone ModemManager[4891]:
Before the fwupd I at least got calls to connect sometimes although the audio was terrible
The version numbers themselves look okay (and I've used the same combination), I can't comment on what's going on with that call.
Some issue between Pulseaudio / Pipewire and calls probably :
Apr 01 15:48:09 pinephone gnome-calls[4300]: Failed to select audio mode: Timeout was reached
...
Apr 01 15:48:17 pinephone callaudiod[4056]: card has no usable source
Apr 01 15:48:17 pinephone callaudiod[4056]: card has no usable sink
If you start a call and manually change the profile from Phosh' Settings, does it work?
No real change:
Apr 02 19:30:56 pinephone ModemManager[3495]:
I don't know why flashall does not work for me.
I don't understand eg25-manager[3308]: Rescheduling upload since modem isn't online yet, in 30s
I think the anx7688
messages ares due to the power plug disconnecting and reconnecting, which I'm afraid it does frequently.
You're mixing things up, let's back up a bit please :)
Yes, the anx messages do make it look like your cable is a little loose, but doesn't matter for any of this.
About the flashall
errors: If it can't find any of the files is because it's not available in the folder where you unpacked the update file. The flashall
script is only used to flash the entire firmware, if you want to only flash the ADSP, then just use fastboot manually:
With the modem booted, run this (in a root shell):
echo -ne
AT+QFASTBOOT\r' > /dev/ttyUSB2`fastboot flash modem [PATH_TO_NON_HLOS.ubi] && fastboot reboot
With that the ADSP will be updated and the modem rebooted afterwards.
As for the audio errors (which don't have anything to do with the ADSP), you have some problem at the distro level: callaudiod[5027]: no available input found!
, it's not finding the microphone (at least), so switching profiles fail. If you have a microsd nearby I'd recommend you flash a clean distro on it and try to boot from it and check if audio works there, maybe some package broke in your current system?
I am afraid I was not making myself very clear. The flashall script fails because appsboot.mbn does not seem to exist in my arch system.
I already updated the ADSP
I think I see the problem with the audio, but I don't know how to fix it. It is some conflict between pipewire and pulseaudio :(
The flashall script fails because appsboot.mbn does not seem to exist in my arch system.
I do see that there is an appsboot.mbn file in the recovery repo. Can I use that? If so, I wonder why it does not exist in the upgrade release?
Which release package are you using? I just checked and it's definitely both in the 0.7.2 and 0.7.4 packages.
pinephone_modem_sdk-0.7.4
I don't see it. I will check again
git clone https://github.com/the-modem-distro/pinephone_modem_sdk.git
Can you tell me where to find it in the download?
The binaries aren't in the Git repository. Go to https://github.com/the-modem-distro/pinephone_modem_sdk/releases, pick the version you want, and download the package.tar.gz
from there.
I already tried that with 0.7.4 - as g=far as I can see the contents are identical to the cloned repo.
I do see that there is an appsboot.mbn file in the recovery repo. Can I use that?
I already tried that with 0.7.4 - as g=far as I can see the contents are identical to the cloned repo.
That means you downloaded the wrong file. You need the package.tar.gz
, not one of the autogenerated source archives.
Now I feel really stupid. I found the package.tar.gz
at the foot of the 0.7.4 page and as you say, it works fine. Thank you for being patient with me.
I just made a video on how I updated the ADSP version.
https://www.youtube.com/watch?v=XsCpmkE5ttg
Device: PinePhone OS: DanctNIX Arch Linux Arm Kernal: Linux danctnix 6.2.9-1-danctnix Phosh: 0.25.2-1
Thank you for the video. I have the same installation as you have Arch 6.2.9-1, Phosh 0.25.2-1 (fresh install)
Biktorgj firmware
$ sudo atinout - /dev/ttyUSB2 -
AT+QGMR
0.7.4 OK
and ADSP ihas been updated
AT+GETADSPVER
EG25GGBR07A08M2G_30.007.30.007
OK
The modem is connected:
$ mmcli -m 0
Bearer | paths: /org/freedesktop/ModemManager1/Bearer/1
and SMS works. MMS is not set up.
Calls do not work in or out. Here is the journal for an outgoing call:
Apr 08 08:57:01 pinephone gnome-calls[4766]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Apr 08 08:57:01 pinephone gnome-calls[4766]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Apr 08 08:57:01 pinephone dbus-daemon[3793]: [session uid=1000 pid=3793] Activating service name='org.gnome.Contacts' requested by ':1.73' (uid=1000 pid=4766 comm="/usr/bin/gnome-calls")
Apr 08 08:57:01 pinephone dbus-daemon[3793]: [session uid=1000 pid=3793] Successfully activated service 'org.gnome.Contacts'
Apr 08 08:57:03 pinephone ModemManager[3438]:
There are several warnings in the journal some of which look interesting, but I don't know which, if any, are relevant.
I will assume the flashing issue can be closed.
I think you now have a SIM card not activated or not registered. I will also assume you have not internet. Voice over LTE requires internet.
From your journalctl.txt, these lines point me to a SIM card issue or provider issue.
Apr 08 08:20:47 pinephone NetworkManager[3426]: <warn> [1680934847.9913] device (cdc-wdm0): retrieving IP configuration failed: modem IP method unsupported
Apr 08 08:21:12 pinephone vvmd[3863]: Could not get modem number!
Apr 08 08:21:13 pinephone mmsdtng[3861]: Could not find settings: Operator ID '208300' with APN 'symamobile.com' not found in service provider database
Apr 08 08:21:13 pinephone mmsdtng[3861]: Your MMS settings are not in the database! Please file a merge request at https://gitlab.gnome.org/GNOME/mobile-broadband-provider-info so they can be added
...
Apr 08 08:39:56 pinephone NetworkManager[3426]: <warn> [1680935996.1808] device (cdc-wdm0): Activation: failed for connection 'Syma'
symamobile.com is not on "PinePhone_Carrier_Support" https://wiki.pine64.org/wiki/PinePhone_Carrier_Support
"syma" is not on "PinePhone_APN_Settings" https://wiki.pine64.org/wiki/PinePhone_APN_Settings
I think you now have a SIM card not activated or not registered.
No, activated and registered, works fine in Android.
I will also assume you have not internet. Voice over LTE requires internet.
No I have internet, VoLTE is not supported by Syma I think?
However the flashall failure has been resolved.
I tried flashall as both user and sudo. As user the result was:
./flashall
Sending AT+QFASTBOOT...
< waiting for any device >
FAILED (remote: 'unknown command')
fastboot: error: Command failed
fastboot: error: cannot load 'appsboot.mbn': No such file or directory
./flashall: line 8: exit: Failed to flash the bootloader: numeric argument required
I am running arch linux and android-tools is installed
Can someone tell me where I am going wrong?