Bug 748250

Summary: USB thethering to an Samsung Galaxy S phone doesn't work
Product: [Fedora] Fedora Reporter: Horst H. von Brand <vonbrand>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 16CC: dcbw, samuel-rhbugs
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 13:47:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Horst H. von Brand 2011-10-23 14:59:46 UTC
Description of problem:
I configured my Samsung Galaxy S (Android 2.3.3) for USB thethering, and the icon on the phone show it as active. But this Samsung N210 netbook just shuts down WiFi (that is OK), but NM shows no way to conncto through the pnone, and the network icon shows there is no network.

Version-Release number of selected component (if applicable):
NetworkManager-0.9.1.90-4.git20110927.fc16.x86_64

How reproducible:
Each time, also with my Toshiba notebook with Fedora 15.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Samuel Sieb 2012-02-08 18:13:53 UTC
This appears to be a problem with phone itself or less likely a kernel issue.  Just use the AP mode instead.
I have seen instructions that suggest that if you have the phone in Kies mode and don't activate USB tethering, then you can use it as a modem.  However, you would have to set this up manually as the phone sabotages that option too, so it won't work automatically:

Feb  8 09:59:34 laptop kernel: [71966.182910] usb 2-1: New USB device found, idVendor=04e8, idProduct=6877
Feb  8 09:59:34 laptop kernel: [71966.182915] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb  8 09:59:34 laptop kernel: [71966.182918] usb 2-1: Product: SAMSUNG_Android
Feb  8 09:59:34 laptop kernel: [71966.182921] usb 2-1: Manufacturer: SAMSUNG
Feb  8 09:59:34 laptop kernel: [71966.182924] usb 2-1: SerialNumber: [...]
Feb  8 09:59:34 laptop kernel: [71966.183447] cdc_acm 2-1:1.0: This device cannot do calls on its own. It is not a modem.
Feb  8 09:59:34 laptop kernel: [71966.183553] cdc_acm 2-1:1.0: ttyACM0: USB ACM device

Note the second to last line.  This same output shows up when the phone is in USB storage mode as well.

Although modem-manager does seem to do something with it:
Feb  8 09:24:38 laptop modem-manager[1057]: <info>  (ttyACM0) opening serial port...
Feb  8 09:24:38 laptop dbus-daemon[1003]: modem-manager[1057]: <info>  (ttyACM0) opening serial port...

As for USB tethering, this is what happens:

Feb  8 09:24:42 laptop kernel: [69873.325014] usb 2-1: New USB device found, idVendor=04e8, idProduct=6881
Feb  8 09:24:42 laptop kernel: [69873.325018] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb  8 09:24:42 laptop kernel: [69873.325020] usb 2-1: Product: SAMSUNG_Android
Feb  8 09:24:42 laptop kernel: [69873.325022] usb 2-1: Manufacturer: SAMSUNG
Feb  8 09:24:42 laptop kernel: [69873.325024] usb 2-1: SerialNumber: [...]
Feb  8 09:24:42 laptop mtp-probe: checking bus 2, device 4: "/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-1"
Feb  8 09:24:42 laptop mtp-probe: bus: 2, device: 4 was not an MTP device
Feb  8 09:24:42 laptop kernel: [69873.634063] usbcore: registered new interface driver cdc_ether
Feb  8 09:24:42 laptop kernel: [69873.640331] usb 2-1: bad CDC descriptors
Feb  8 09:24:42 laptop kernel: [69873.640637] usbcore: registered new interface driver rndis_host
Feb  8 09:24:42 laptop kernel: [69873.654846] usb 2-1: bad CDC descriptors
Feb  8 09:24:42 laptop kernel: [69873.654879] usbcore: registered new interface driver rndis_wlan

No devices get created.

Comment 2 Samuel Sieb 2012-02-08 18:19:17 UTC
If you really want to use the ACM modem mode, here are the instructions:
http://technomagus.wordpress.com/2011/07/16/samsung-galaxy-s-i9000-android-2-3-3-and-usb-tethering-on-ubuntu/

Comment 3 Samuel Sieb 2013-01-08 22:31:46 UTC
I've since upgraded my phone to Android 4.x and now it shows up as a USB ethernet port, so there's no longer a problem.

Comment 4 Fedora End Of Life 2013-01-16 13:07:20 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Fedora End Of Life 2013-02-13 13:47:09 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.