Bug 91146

Summary:	Add Franklin Wireless (u600) location support
Product:	ModemManager	Reporter:	Matt Bonnett <Vchat20>
Component:	plugins	Assignee:	ModemManager bug user <modemmanager>
Status:	RESOLVED MOVED	QA Contact:
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	All
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Matt Bonnett 2015-06-29 17:26:58 UTC

I have a Franklin Wireless u600 (Sprint 3G/Wimax combo USB modem) stick that I have been trying to sort out getting GPS to work on. I have it locked to 3G only and making connections via wvdial works great. ttyACM0 is the main modem/AT port and then there are extra ttyUSB0-3 ports. ModemManager seems to be able to communicate with it somewhat using Qualcommon's proprietary protocols but seems like it is very limited thus far on what is offered. Even --time shows unavailable which seems like ANY cellular modem should at least offer that up. I've tried all the numerous AT commands offered to try to enable GPS and none work. Seems like it is a cryptic set of commands sent over the control port.

I am not a coder myself but I am wondering if there is any way I can provide any assistance in trying to at least make the slightest bit of headway on getting GPS support on this. I know it works. In Windows with Sprint's connection manager once enabled the NMEA com port works flawlessly. I even grabbed a free trial of a serial port sniffer and at least managed to grab a snippet of control port traffic but it is all greek to me. I'd be willing to try and offer help where I can.

I'll reply back in a couple hours once I'm back at my test machine with stuff like the mmcli output and my haphazard serial port snippet.

My current test boxes are an RPi2 running Ubuntu armhf and a virtualbox instance running x64 Ubuntu with usb passthrough for the modem.

Comment 1 Aleksander Morgado 2015-07-06 07:38:57 UTC

If I'm not mistaken, Franklin Wireless modems all come with Qualcomm based chipsets, which means that they should be handled using QMI, not using AT commands. Can you give us the output of "lsusb -v" of the specific VID/PID of the device?

Comment 2 Aleksander Morgado 2015-07-06 07:44:09 UTC

Also, full ModemManager debug logs would be nice; see:

http://www.freedesktop.org/wiki/Software/ModemManager/Debugging/

Comment 3 Dan Williams 2016-07-20 17:12:10 UTC

ModemManager should use AT and QCDM for this device, but primarily QCDM.  It's vid/pid is 1fac:0151.

Unfortunately we haven't reverse-engineered the QCDM commands for GPS yet, so that's not available for this device.  The USB sniffer logs would be helpful here, but obviously it would take quite a bit of work to make GPS happen here.

Comment 4 GitLab Migration User 2018-06-10 09:05:39 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/70.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.