Not really, no. What I'm not sure is why CIND is preferred over CSQ by default.
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1060831 Title: Sierra/ZTE LTE modem gives no signal quality in LTE mode (only in 3G/2G mode) Status in “modemmanager” package in Ubuntu: Triaged Status in “network-manager-applet” package in Ubuntu: Invalid Bug description: In LTE mode, the sierra modem (MC7710) gives no indication of signal quality in nm-applet. It looks like icon "gsm-3g-none.svg". I suspect this is caused by this in the modemmanager debug log when connected: modem-manager[25672]: <debug> [1349256755.558392] [mm-at-serial-port.c:334] debug_log(): (ttyUSB3): --> 'AT*CNTI=0<CR>' modem-manager[25672]: <debug> [1349256755.579056] [mm-at-serial-port.c:334] debug_log(): (ttyUSB3): <-- '<CR><LF>*CNTI: 0,LTE<CR><LF><CR><LF>OK<CR><LF>' modem-manager[25672]: <debug> [1349256758.802283] [mm-at-serial-port.c:334] debug_log(): (ttyUSB3): --> 'AT+CIND?<CR>' modem-manager[25672]: <debug> [1349256758.821538] [mm-at-serial-port.c:334] debug_log(): (ttyUSB3): <-- '<CR><LF>+CIND: 5,0,1,1,0,0,1,0<CR><LF><CR><LF>OK<CR><LF>' Seems like the signal quality is the second number: Oct 1 19:23:39 marius-T1005 ModemManager[22170]: <debug> [1349112219.280233] [mm-at-serial-port.c:392] debug_log(): (ttyUSB3): <-- '<CR><LF>+CIND: ("battchg",(0-5)),("signal",(0-5)),("service",(0-1)),("call",(0-1)),("roam",(0-1)),("s msfull",(0-1)),("GPRS coverage",(0-1)),("callsetup",(0-3))<CR><LF><CR><LF>OK<CR><LF>' Oct 1 19:23:39 marius-T1005 ModemManager[22170]: <debug> [1349112219.280871] [mm-broadband-modem.c:1704] cind_format _check_ready(): Modem supports signal quality indications via CIND at index '2'(min: 0, max: 5) which is reported as zero. The signal is good (I measure download rate of 37 mbits/s), and in 3G/2G mode I get the correct signal quality indication. Could it be that MM should not use +CIND but instead +CSQ? ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager-gnome 0.9.6.2-0ubuntu5 Uname: Linux 3.6.0-030600rc6-generic i686 ApportVersion: 2.6.1-0ubuntu1 Architecture: i386 Date: Wed Oct 3 11:19:55 2012 EcryptfsInUse: Yes IpRoute: default via 89.9.192.92 dev wwan0 proto static 89.9.192.0/24 dev wwan0 proto kernel scope link src 89.9.192.92 metric 7 169.254.0.0/16 dev wwan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en TERM=xterm PATH=(custom, no user) LANG=nb_NO.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: network-manager-applet UpgradeStatus: Upgraded to quantal on 2012-08-31 (32 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wwan0 gsm connected /org/freedesktop/NetworkManager/Devices/2 eth0 802-3-ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless unavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.7.0 connected enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1060831/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
