New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SMS send don't work in 4G-mode #40
Comments
Just flashed the 003.003 modem firmware. Nothing changed. The issue still present in both (002 and 003) variants. |
Did it work in stock? That seems to either work or not depending on the carrier. There's a command to force the modem to use a specific method to send SMS, and that is
Still, some users do have problems sending messages even after changing this setting. I have not been able to replicate this though, so if it works please let me know |
tried all of the setting without success. Do you have an e-mail that I could attach all modem-logs (for security reasons I would not post it here)? |
@pizdjuk It's a problem with the provider and the workaound is to disable IMS in eg25-manager which means that calls and SMS will use 2G instead of VoLTE (and during the SMS sending or call there data transfer will not use LTE speed). That's the change to the eg25-manager config to disable IMS:
You may also try to set |
Yeah, man! Thanks! It worked. I with value="1" The call-quality of 2G is completely ok for me :) |
Dont work anymore :/ |
Didn't check the docs but with value = 1 I don't think it will disable IMS, try 0 or 2 and reboot, I would say. |
With value=0 didn't work. With value=2 works. Thanks!! I could sent about 12-15 sms without problems till now. I close the issue for now. |
Something strange is going on. I rebooted and cannot send SMS again. The file didnt change |
I've also had this problem. Data&Calls work across all networks, but when I'm on 4G, I can't send and receive SMS.
I've commented out this line in
And the problem has gone away, I can reliably get SMS, do calls & 4G internet. Call quality seems ok to me |
That worked for me, thank you! |
worked for my carrier, however ... ... how long will this workaround fix this? "It's a problem with the provider and the workaound is to disable IMS in eg25-manager which means that calls and SMS will use 2G instead of VoLTE" OK, but my carrier has announced that all remaining 2G & 3G fallback will be terminated by EOY 2022. Probably to coincide with 5G rollouts. So this will break for a lot of Pinephone users as fallback options go away. |
It's a tough question. Disabling IMS doesn't disable LTE, what it does is it stops trying to send SMS and calls over IP (IMS means IP multimedia subsystem), so you use the good ol' GSM way of sending messages. That said, the problem is, to use IMS, you need to have a compatible profile for your carrier, and the Quectel modem only provides a few + a generic one, which works for some but doesn't for others. But pushing those profiles to the modem won't work either, because they're digitally signed and will only work for the vendor whose signature match. So short of re-signing those files and hoping for the best, or asking Quectel to bundle profiles for major carriers everywhere, there's not much more I can do about it (I even made a tool to push the mbn profiles to the modem) I want to, at some point, to try to sign those files with test keys to see if they load, but I don't know what's inside, so I don't really know if they're chipset dependent or only have some kind of apn, proxy or what, so no promises on whether it'll work or not |
Yea, too many variations of carrier-modem configurations. Or push this onto users but with a more more streamlined/standard way for users to re-config the modem, like pointing everyone to eg25-manager. Mobian discussion basically re-iterated the carrier profile point for this same IMS issue with SMS: https://gitlab.com/mobian1/issues/-/issues/254. The TOML profiles for eg25-manager are device specific (ex: pine64,pinephone-1.2), while the Quectel modem profiles are carrier specific (hVoLTE-Verizon) -- but just a few and generic. Seems like a marriage of these two approaches would line-up compatibility if users were guided on where to re-config. Maybe it won't be a big deal. I think this year (2022) with Pinephone Pro purchases happening using the same Quectel modem and carriers everywhere terminating UMTS & CDMA we'll see how much carrier-modem compatibility was dependent on falling back to non-LTE or a specific configuration. |
P.S. A Mobian user posted LineageOS's list of carrier profiles in an eg25-manager issue, so x-posting that here b/c it looks to be a better option (to externalize the profiles in a common config): https://gitlab.com/mobian1/devices/eg25-manager/-/issues/25 |
Hi everyone, I'm working on a small tool to convert, unpack and repack IMS/VoLTE configuration files. It's not yet finished but it already seems to work for some files, but I have no idea if the modem is able to connect to IMS with them as I don't have access to those providers. If your carrier is somewhere in this folder, can you link me the file and I'll try to provide you a converted mcfg_sw file so you can push it to the modem and tell me if it works? |
@pothos How confortable are you with command line stuff? And here the profile you linked, converted How to try this:
If Autosel is enabled (it is by default), it might choose it automatically on next reboot if your SIM belongs to that carrier or if the connected network matches. You can also select manually, but let's not get ahead of ourselves. If you can give it a try, please post results here, especially the results of the command
It will mean the profile is correctly enabled. Worst case scenario the modem will crash and you'll have to reboot the phone to get it back online |
Hi again, I tested the profile I posted before and it wasn't being correctly added (despite the modem saying everything was fine.... ) Attaching a new profile: If everything works as expected, you should get this in QMBNCFG list: Small explanation for what you see in that list: Following my own example, if you have a SIM from Telefonica Germany, and you manually select the profile, you should get |
Thanks for the detailed instructions and the update! Immediate result after applying:
After the modem reboots I get this here, however:
|
With |
Now it seems to switch by itself to 2G when I do an USSD code, previously it didn't work and I had to switch manually to 2G for it to work. I wonder whether it switches back to 4G eventually because currently it's stuck on 2G even after making a call (the call was 2G as I could hear a lot of noise).
Edit: I guess it means that the profile isn't working correctly |
So... Selected but not active. This is the same result we had with a custom built profile the other day, but there are so many things involved here and so little debugging capacity I have to ask the dumb questions just in case |
Yeah, not directly Telefonica… |
I found some old log from 2021 where I had played with the profiles there I had |
Makes sense, |
With the default profile VoLTE calls work, just SMS/USSD not until I switch to 2G/3G |
@bircoph Test profile here: Tested in one of my modems and it gets correctly loaded, but that's as far as I can test:
Let me know if it works! |
Wow! This is something amazing. By accident this is not a common VoLTE profile, but VoWIFI profile just recently announced by the provider for "a limited number of phone models". It allows voice phone calls via wifi access points without mobile network at all. I will test it when I'll be in an area of such point. Meanwhile while looking how to enable VoWIFI support I found that for both VoLTE and VoWIFI I need to enable "internet calls, technological mark" service option in my personal account at provider. It is free of charge, but disabled by default. After enabling it 4G-only VoLTE calls work on my pinephone even on default VoLTE profile. SMS over 4G (technically over IP intranet) also work. Only USSD requests does not work in 4G-mode. I found another suitable profile in the repo here. Could you please convert it for testing as well? From its dump it looks like this is a common VoLTE profile, not VoWIFI, but it has a special option ussdAcceptContact — maybe USSD requests will work with this profile over 4G. Thanks! |
Even if the profile says "VoWifi" it should work without wifi, the baseband uses only one profile for a carrier so they won't have two different profiles for the same operator and change them on the fly (it would need to disconnect a IMS session and reconnect to do that). You won't be able to use VoWifi in the Pinephone though, as the wlan adapter isn't connected directly to the modem, so the modem can't route through it Here's the profile you linked to: mts_test2.zip Send
I made the profile conversion as seamless as I could with mcfg tools. If you find some other profile and want to check it out, it's just two commands:
Then just load it with mbnloader as with the other profiles |
Hi! I was finally able to test this. Sorry for a delay, but pinephone is used as my main phone, so I have limitations for time slots when I can conduct dangerous experiments. Both profiles load and work, but worse than default ROW_Generic_3GPP in 4G-only mode:
For now I reverted on ROW_Generic_3GPP where in 4G-only mode everything except USSD requests and calls to short service numbers work. I'll try to test other profiles, at least it should be possible to bisect why ipv4 works on one profile and don't work on another. |
@Biktorgj shared a bunch of commands not to use IMS for SMS, and for me it works :
Here the process Reading the current value
if there is an error, Values are : Writing the new value
Checking it was saved
RebootThank you @Biktorgj |
Great stuff, I did
and it directly worked plus it is preserved over reboots :) |
@bircoph sorry to necrobump this but could you convert these: Pannon/Telenor/Yettel HU, Vodafone HU profiles? |
But works if the modem put in 2G mode only (I didnt test other variants). In 4G mode mmcli returns "timeout was reached".
The text was updated successfully, but these errors were encountered: