Samsung Galaxy 4.2 (Android and USB)

[Scotchman]

I just got a Samsung Galaxy 4.2 as my first android device. I am also switching away from Windows to PCLOS as my primary system.

Problem: A USB driver for the Galaxy 4.2 for Windows and works fine. I can access the  internal SD cards fine.

But not in PCLOS. I tried adding a udev rule according to other Galaxy devices on another distro forums. They do not seem to work in PCLOS though.

#/etc/udev/51-android.rules

SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", ATTRS{idProduct}="6860"

and also this

SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", ATTRS{idProduct}="6860", MODE="0666", GROUP="plugdev"

I get an udev error on booting which flies by too fast to catch.

Any ideas or success by someone else?

[Just17]

You might try the following commands in a terminal  ...

Code: [Select]

dmesg | grep -i error

dmesg | grep -i warn

dmesg | grep -i fail
Those outputs might be useful in finding the problem.

[T6]

what version of android does it have?

is it connecting as a usb mass storage device or as mtp device?

[Scotchman]

Android Version is 2.3.6

I have tried it both as MTP and USB device and both with Debugging on and off. USB+Debugging works in windows with the usb driver so thaat I know the physical aspect is functioning, but I want to have it working in Linux.

My dmesg output is  as follows but fails to show the output of the udev 51-android which occurs right before the EDID errors

I changed the rule to this which is accepted.  It seems that the ProductID and group were both a problem causing an error = "...group unknown."

51-android-rules
#Samsung
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"

Here are the dmesg output. I have an EDID error that is not related and part of my netbook

#dmesg | grep -i error
#dmesg | grep -i warn
#dmesg | grep -i fail
 pci0000:00: ACPI _OSC request failed (AE_NOT_FOUND), returned control mask: 0x1d

So now the rule loads quietly but pluging in my Samsung Galaxy 4.2 does nothing but charge it. The cable is fine as it works in windows and is the OEM that came with it.


Any ideas?

[T6]

the right way to use it on linux is usb mass storage and disable debug mode

if the device is not seen by linux when connected by doing lsusb in konsole then it could be one of those annoying samsung models that needs to be connected to windows by using samsung kies 

[Scotchman]

As always, it is at least good learning. I have finally dropped windows as my primary OS.

Here is lsusb and I don't see it.

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 003: ID 058f:6335 Alcor Micro Corp. SD/MMC Card Reader
Bus 001 Device 004: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129
Bus 001 Device 005: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse

Well, I can always use Wifi and share is. That is what I WAs doing but USB would be faster and not require a network.

Thanks for trying. Maybe a fix will happen later.

[T6]

for file transfer i'm using airdroid to avoid connecting it and mount the sd card on the system

that lsusb was while the device was configured as usb mass storage device and without debugging enabled?

[Just17]

On the Samsung you should be able to go through Settings to USB settings and there select the type of connection you wish .....  I have a Galaxy1 which is slightly different to the later models, but I can choose from the following

Samsung Kies   (Windows connections)
Media Player
Mass Storage

I have it set to ask when a USB cable is inserted.

I recall a friend had a similar problem to yours and eventually he found the correct setting.
He installed nothing to do so ....  but managed to get his card to be seen as Mass Storage by delving into the settings.

Settings - Wireless & Network - USB Utilities - Connect Storage to PC

[Scotchman]

I have done all of the above. And I think it may be a problem unique to this new model. Limited to Windows until someone with this specific Galaxy 4.2 with PCLinuxOS specifically.

It may be a long wait! TNX

now I hate going back to windows....

[Just17]

I have done all of the above. And I think it may be a problem unique to this new model. Limited to Windows until someone with this specific Galaxy 4.2 with PCLinuxOS specifically.

It may be a long wait! TNX

now I hate going back to windows....

Do you mean that you found this setting and used it?

Settings - Wireless & Network - USB Utilities - Connect Storage to PC

...  and it did not do as its name suggests?

[Scotchman]

On this particular model it is:

Settings - Wireless & Network - USB Utilities - Mass Storage.

And NO is is not then recognized in PCLOS. With Debugging-mode on or off.

In windows, with Debugging ON... And the driver installed... simply plugging in the cablee activates it as a Mass Storage Device.

In Linux, nothing happens.

I understand the possibility that with this particular model something different may need to be done as has happened in the past. I already know that rooting this device was different that the 3.6, 40, & 5.0 and took a bit longer (actually it only got rootable this past month! so something is different about it.