Android "Smart"phone as external drive with Porteus?

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Android "Smart"phone as external drive with Porteus?

Post#1 by Rava » 03 Oct 2015, 16:01

I need to get some data from my Samsung Galaxy S4 to my main PC, Porteus recognizes it. This is from /var/log/messages:

Code: Select all

Oct  3 17:46:09 porteus kernel: [77019.061039] usb 4-2: new full-speed USB device number 2 using uhci_hcd
Oct  3 17:46:12 porteus kernel: [77021.204096] usb 4-2: USB disconnect, device number 2
Oct  3 17:46:12 porteus kernel: [77021.411052] usb 4-2: new full-speed USB device number 3 using uhci_hcd
The only running disk is a fixed hard disk, sda.

Porteus not gives me and icons for the " full-speed USB device ", while Android complains the host PC it got connected to misses the software for synchronising, telling me how to fix that issue for Witless OS, or for mac OS. quite ironically, of course, considering Android itself is a Linux...

Any ideas how to "convince" stupid android to just let it behave like an external disk to my host OS?
Cheers!
Yours Rava

beny
Full of knowledge
Full of knowledge
Posts: 720
Joined: 02 Jan 2011, 11:33
Location: italy

Re: Android "Smart"phone as external drive with Porteus?

Post#2 by beny » 03 Oct 2015, 16:07

hi lsusb i think is better,don't seem connected,you have to see the uri or so.

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: Android "Smart"phone as external drive with Porteus?

Post#3 by Rava » 03 Oct 2015, 18:38

^

Code: Select all

# lsusb
Bus 002 Device 002: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse (M-BT58)
Bus 002 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 004 Device 003: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II], GT-I9300 Phone Galaxy S III], GT-P7500 [Galaxy Tab 10.1] , GT-I9500 [Galaxy S 4]
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 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
BTW, it's not a GT-I9100 nor a GT-I9500 :crazy:


Aaaanyhow, here is the part from lsusb -v about the Samsung Galaxy:

Code: Select all

# lsusb -v
[...]

Bus 004 Device 003: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II], GT-I9300 Phone [Galaxy S III], GT-P7500 [Galaxy Tab 10.1] , GT-I9500 [Galaxy S 4]
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x04e8 Samsung Electronics Co., Ltd
  idProduct          0x6860 GT-I9100 Phone [Galaxy S II], GT-I9300 Phone [Galaxy S III], GT-P7500 [Galaxy Tab 10.1] , GT-I9500 [Galaxy S 4]
  bcdDevice            4.00
  iManufacturer           1 SAMSUNG
  iProduct                2 SAMSUNG_Android
  iSerial                 3 5fe026ad
  bNumConfigurations      2
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           39
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xc0
      Self Powered
    MaxPower               96mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass         6 Imaging
      bInterfaceSubClass      1 Still Image Capture
      bInterfaceProtocol      1 Picture Transfer Protocol (PIMA 15470)
      iInterface              5 MTP
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x001c  1x 28 bytes
        bInterval               6
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength          105
    bNumInterfaces          3
    bConfigurationValue     2
    iConfiguration          0 
    bmAttributes         0xc0
      Self Powered
    MaxPower               96mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass         6 Imaging
      bInterfaceSubClass      1 Still Image Capture
      bInterfaceProtocol      1 Picture Transfer Protocol (PIMA 15470)
      iInterface              5 MTP
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x001c  1x 28 bytes
        bInterval               6
    Interface Association:
      bLength                 8
      bDescriptorType        11
      bFirstInterface         1
      bInterfaceCount         2
      bFunctionClass          2 Communications
      bFunctionSubClass       2 Abstract (modem)
      bFunctionProtocol       1 AT-commands (v.25ter)
      iFunction               8 CDC Serial
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         2 Communications
      bInterfaceSubClass      2 Abstract (modem)
      bInterfaceProtocol      1 AT-commands (v.25ter)
      iInterface              6 CDC Abstract Control Model (ACM)
      CDC Header:
        bcdCDC               1.10
      CDC Call Management:
        bmCapabilities       0x00
        bDataInterface          2
      CDC ACM:
        bmCapabilities       0x02
          line coding and serial state
      CDC Union:
        bMasterInterface        1
        bSlaveInterface         2 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval              32
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        2
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass        10 CDC Data
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0 
      iInterface              7 CDC ACM Data
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  bNumConfigurations      2
Device Status:     0x0000
  (Bus Powered)


[...]
Cheers!
Yours Rava

User avatar
brokenman
Site Admin
Site Admin
Posts: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Android "Smart"phone as external drive with Porteus?

Post#4 by brokenman » 03 Oct 2015, 21:45

Does the phone have a setting 'Mass storage mode' ?
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: Android "Smart"phone as external drive with Porteus?

Post#5 by Rava » 03 Oct 2015, 23:45

brokenman wrote:Does the phone have a setting 'Mass storage mode' ?
Good question, as "fluently" I am with lots of Linux'es, as clumsy I am with a Linux when it's Android and a "Smart"phone... :oops:

Too late for now cause tired (01:45 already here, meaning "a.m."), I look into that tomorrow and post an update ASAP.
Cheers!
Yours Rava

User avatar
brokenman
Site Admin
Site Admin
Posts: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Android "Smart"phone as external drive with Porteus?

Post#6 by brokenman » 04 Oct 2015, 01:44

I hear you. I have a cell phone, but I use it only to wake me up and the occasional text message.
How do i become super user?
Wear your underpants on the outside and put on a cape.

cttan
Shogun
Shogun
Posts: 332
Joined: 26 Jan 2011, 16:15
Distribution: Porteus 3.2 64bit KDE
Location: Malaysia

Re: Android "Smart"phone as external drive with Porteus?

Post#7 by cttan » 04 Oct 2015, 02:56

Hi Rava,

From the S4 pull down menu select "Connected device..." when you are connected to the Porteus PC and then select MTP

Image

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: Android "Smart"phone as external drive with Porteus?

Post#8 by Rava » 04 Oct 2015, 08:41

@cttan

I try that in a moment. Image

For now, your font looks custom set. How did you do this? Image
(Don't tell me it can be done without tweaking the system by a build in menu... Image; would be, once again, proof of my still fail with Android.)
Cheers!
Yours Rava

tome
Contributor
Contributor
Posts: 561
Joined: 26 Jun 2013, 14:03
Distribution: x64 Openbox
Location: Poland
Contact:

Re: Android "Smart"phone as external drive with Porteus?

Post#9 by tome » 04 Oct 2015, 18:32

The quickest way is to remove your sdcard and connect to PC, or see: viewtopic.php?f=39&t=2764&p=19090

cttan
Shogun
Shogun
Posts: 332
Joined: 26 Jan 2011, 16:15
Distribution: Porteus 3.2 64bit KDE
Location: Malaysia

Re: Android "Smart"phone as external drive with Porteus?

Post#10 by cttan » 05 Oct 2015, 00:20

tome wrote:The quickest way is to remove your sdcard and connect to PC, or see: viewtopic.php?f=39&t=2764&p=19090
MTP is included in the latest 3.1 KDE version.
Rava wrote: For now, your font looks custom set. How did you do this? Image
(Don't tell me it can be done without tweaking the system by a build in menu... Image; would be, once again, proof of my still fail with Android.)
It's built in font. Choose Handwriting in Display/Fonts.

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: Android "Smart"phone as external drive with Porteus?

Post#11 by Rava » 05 Oct 2015, 01:12

cttan wrote:MTP is included in the latest 3.1 KDE version.
Then, I really have to install/load all that is named in the linked article?

...

Well, no, thanks, I am sure I try cttan's "select MTP" solution first, hopefully not needing to install anything on my XFCe Porteus...
cttan wrote:
Rava wrote: For now, your font looks custom set. How did you do this? Image
(Don't tell me it can be done without tweaking the system by a build in menu... Image; would be, once again, proof of my still fail with Android.)
It's built in font. Choose Handwriting in Display/Fonts.
Yeah, kinda thought so that it was a already build-in-function.

But .... kinda good e.g. less embarrassing that one being a better programmer than me, like brokenman aka Jay Flood, is also not that fit in Android, but still a real hacker when it comes to non Android Linux. :D
Cheers!
Yours Rava

User avatar
francois
Contributor
Contributor
Posts: 4902
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Android "Smart"phone as external drive with Porteus?

Post#12 by francois » 05 Oct 2015, 02:16

@rava:
Under kde: there is the device notifier which comes up anytime that you plug a usb key. Just click on it. Then you will see your android device, in my case portable media player called xt1032. Click on it will open thru file manager as mtp:/XT1032 or the like. Browse into your files. :)
Voltaire: Le mieux est l'ennemi du bien.

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: Android "Smart"phone as external drive with Porteus?

Post#13 by Rava » 05 Oct 2015, 02:40

@francois

*points to Distribution info below his own username*
Distribution: Porteus 3.1.0 x86-64 XFCe
Nope, no KDE here, just "plain old XFCe..." Image

Does that all really mean, mounting / accessing files from a Porteus XFCe Linux to/from an android out of the box without tweaking the XFCe Porteus somehow has zero chance in working?
Image
Cheers!
Yours Rava

cttan
Shogun
Shogun
Posts: 332
Joined: 26 Jan 2011, 16:15
Distribution: Porteus 3.2 64bit KDE
Location: Malaysia

Re: Android "Smart"phone as external drive with Porteus?

Post#14 by cttan » 05 Oct 2015, 03:51

Rava wrote:
cttan wrote:MTP is included in the latest 3.1 KDE version.
Then, I really have to install/load all that is named in the linked article?

...

Well, no, thanks, I am sure I try cttan's "select MTP" solution first, hopefully not needing to install anything on my XFCe Porteus...
If you are on 3.1 most likely is you do not have to follow the instructions on the given link.
I can only speak for KDE as I'm using it. Not sure about XFCe

aus9

Re: Android "Smart"phone as external drive with Porteus?

Post#15 by aus9 » 29 Oct 2015, 02:43

Hi
Does that all really mean, mounting / accessing files from a Porteus XFCe Linux to/from an android out of the box without tweaking the XFCe Porteus somehow has zero chance in working?
I am not rich enough to afford Samsungs, I tend to buy Mediatek chipset phones from China.

Also its not clear to me, if you mean just your removeable sdcard or your internal storage (balance of ROM after system)

1) Go to Thunar and check you have in Preferences setup mount removable media either automatic as prompt
---I am on LXQt but the file manager preferences are similar

2) In your phone, watch your notifications please. My phone allows swipe down from the top to re-visit any you have missed.
The phone may have timed out on giving you MTP. In which case simply pull the USB cable and re-insert.

3) Forgive this bit, some phones expect USB Debugging to be turned on....and have set it to default OFF.
So if you see the notification that your device offers MTP, camera etc then ignore this advice
---Otherwise you need to turn it on. Most phones require admin rights to do that.
Go into system settings and look for "Developer Options"

If already there, Go to the section called Debugging and touch it to enable it please.

(b) If you can't see Developer options in settings you need to turn it on.
some phones allow this by touching the about phone about 7 times, and often give a warning that you are about to enter developer mode or admin mode etc etc.

4) the other option, without removing your sdcard, is to look at adb in Linux thru android-tools XZM and setting up an udev rule
but that is a much longer process and may be beyond your time needs?
I have done it on another distro but not yet done it on Porteus.

adb is mainly used to interact with naughty system settings and can access the system not the removeable sdcard

I am too lazy to duckduckgo your make and model to see if there are any issues, I shall wait to see if above is of any help

Post Reply