On Wed, 2016-04-06 at 10:49 +0200, Aleksander Morgado wrote: > On Mon, Apr 4, 2016 at 11:13 AM, Jarosław Bielski <[email protected] > m> wrote: > > > > > > > > Could you gather debug ModemManager logs while the capabilities > > > are > > > set to "gsm-umts" only? Get the modem registered in the network > > > and > > > connected, while getting the logs, please. We should see what the > > > modem replied in each of the commands we send. > > It seems that setting mode to 2g only failed because the modem had > > set > > current bands to u2100 - I did not catch that band selection is > > "non > > volatile", it is obligatory after boot up/power on. After changing > > current > > bands to any I am able to switch the mode to 2g (the modem shows > > EDGE > > indicator on embedded LCD). > > > > I am not one hundred percent certain if mode 2g|3g with preferred > > none works > > correctly, because modem shows that it uses 4g. I have attached > > logs from > > two steps: > > 1. setting mode to 2g|3g, preferred none > > 2. connecting to the network by single-connect > > > > Thanks for the tips. I really appreciate your help. > Thanks for the logs. Both show that the modem ends up always in 3G, > never in 4G, so I think ModemManager is actually doing the right > thing. No idea why the LCD would say 4G :)
It might depend on the variant; the 340U in the US was primarily an AT&T device. And AT&T is well-known for calling HSPA "4G" and making their devices show the same thing on-screen. They call LTE "4G LTE" to distinguish it from HSPA and DC-HSPA. "4G LTE devices limited to 4G HSPA+" https://www.att.com/esupport/article.html?_escaped_fragment_=/wireless/ KM1008736#!/wireless/KM1008736 Just a possibility. Dan _______________________________________________ ModemManager-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
