Media Transfer Protocol MTP (SOLVED)
lol...I think tahrpup 6.0 is tooooo fast..lol
which reminds me of a suggestion: it would be helpful to slow down some of the pop-up boxes that present during various installations. Sometimes an error box will pop up and disappear before I can read it. I will also add this to the suggestions thread I saw the other night.
which reminds me of a suggestion: it would be helpful to slow down some of the pop-up boxes that present during various installations. Sometimes an error box will pop up and disappear before I can read it. I will also add this to the suggestions thread I saw the other night.
Do yourself a favor and get a factory cord. Those after-markets are poorly made and anything but reliable.
Firsthand experience tells me it's not the software that's holding your phone back, it's the lousy cord.
Firsthand experience tells me it's not the software that's holding your phone back, it's the lousy cord.
ROX runs displaying /mnt/MTPdevice with a green dot..
>>> Living with the immediacy of death helps you sort out your priorities. It helps you live a life less trivial <<<
Potential aids: updated firmware *or* this dudes mod. Note the FOUR follow-ups.
>>> Living with the immediacy of death helps you sort out your priorities. It helps you live a life less trivial <<<
Since I moved to tahrpup 6.0, I'm getting zero connection.
I'll go ahead and pick up a new cord, but my hunch is that that is not the problem.
The thing about Samsung cables is that the phone connector wire breaks pretty quickly, broke 2 in 6 months. Got electrical tape on this one, but it's just a power cord from an old Samsung phone, not a data cable.
Anyhoo, thanks for the help. I'm not giving up on Puppy, 6.0 is too damn fast. I have a hunch it is more stable than Slacko 5.7 too, I mean, I was surprised that I ever had to reboot Slacko 5.7, but I did have to a couple of times. Not sure what caused that, but I was a little surprised. Might've been screen res though,but it did lock up a few times. So far, no lock ups on 6.0 and none in sight.
I'll go ahead and pick up a new cord, but my hunch is that that is not the problem.
The thing about Samsung cables is that the phone connector wire breaks pretty quickly, broke 2 in 6 months. Got electrical tape on this one, but it's just a power cord from an old Samsung phone, not a data cable.
Anyhoo, thanks for the help. I'm not giving up on Puppy, 6.0 is too damn fast. I have a hunch it is more stable than Slacko 5.7 too, I mean, I was surprised that I ever had to reboot Slacko 5.7, but I did have to a couple of times. Not sure what caused that, but I was a little surprised. Might've been screen res though,but it did lock up a few times. So far, no lock ups on 6.0 and none in sight.
No dice, huh? Both libs grabbed my phone aboard Tahr.
Not that it matters much @ the moment.. I was merely bringing your info to the forefront.
Odd, here you list "e" >> Dev ID [04e8:685e].. Your ss says otherwise.Eventually I got it fixed by inserting a tiny jewelers flat head screw driver into the very narrow side of the micro usb port on the phone and very gently bent the piece in the middle so the contact points would be bent towards the contact points on the usb cable.
Not that it matters much @ the moment.. I was merely bringing your info to the forefront.
- Attachments
-
- sp-pid_mtp.jpg
- (134.82 KiB) Downloaded 746 times
>>> Living with the immediacy of death helps you sort out your priorities. It helps you live a life less trivial <<<
PS >> If your phone's gonna work @ all, the difference between a shoddy cable and good one.
- Attachments
-
- libmtp_connect1.jpg
- (26.48 KiB) Downloaded 752 times
>>> Living with the immediacy of death helps you sort out your priorities. It helps you live a life less trivial <<<
That is a good catch on the Device ID variation. Hmm..maybe cable? I mean, that's a really good catch. I missed that. What would cause that? That number should be the same, no? Could it be caused by switching from PDA to MODEM and back to PDA? I tried various settings in Samsung phone utils. I will look up exactly what those letters and numbers mean.
So I finally installed Airdroid app and it is pretty awesome. Previously I had tried other Wifi-Android-PC file managers, and I wasn't impressed, but this Airdroid is pretty slick. Thanks for that recommendation.
I still would like to get my phone connected to Linux via USB because a few weeks ago I was trying to install custom ROM mods to upgrade Android from ICS to KitKat, etc. Most of that process is best done with a Linux OS from what I can tell. Besides all the web servers and super-computers that run Linux, if you think about it, and you probably have, but I hadn't, the billion or so Android devices are also Linux machines. Pretty incredible.
But I find after several hours of banging my head against the wall and failing to accomplish much, the frustration and fatigue start to produce a lot of errors and unclear thinking in my attempts to troubleshoot. So instead I installed tahrpup 6.0 on another machine and TinyCore on another and went to sleep satisfied that I had accomplished something. lol Actually, I installed that Airdroid after that and went to sleep really satisfied. I even dreamt about it. lol.
Just in a good mood tonight. Patriots won a close one against the Ravens and are now headed to AFC Champ game. So all is well in New England. Also wondering now how many Linux machines are running at your average football game. Including cell phones, it must be close to 100K.
I will definitely pick up a cable, because I did notice improvement when I got rid of the extension I was using to connect to windows. And many people have experienced the same. Also looking at a new phone, probably not Samsung, probably Motorola. I will definitely make sure it MTP/PTP is selectable. By the time I get around to getting it,there will likely be new protocols, though.
Cheers!
So I finally installed Airdroid app and it is pretty awesome. Previously I had tried other Wifi-Android-PC file managers, and I wasn't impressed, but this Airdroid is pretty slick. Thanks for that recommendation.
I still would like to get my phone connected to Linux via USB because a few weeks ago I was trying to install custom ROM mods to upgrade Android from ICS to KitKat, etc. Most of that process is best done with a Linux OS from what I can tell. Besides all the web servers and super-computers that run Linux, if you think about it, and you probably have, but I hadn't, the billion or so Android devices are also Linux machines. Pretty incredible.
But I find after several hours of banging my head against the wall and failing to accomplish much, the frustration and fatigue start to produce a lot of errors and unclear thinking in my attempts to troubleshoot. So instead I installed tahrpup 6.0 on another machine and TinyCore on another and went to sleep satisfied that I had accomplished something. lol Actually, I installed that Airdroid after that and went to sleep really satisfied. I even dreamt about it. lol.
Just in a good mood tonight. Patriots won a close one against the Ravens and are now headed to AFC Champ game. So all is well in New England. Also wondering now how many Linux machines are running at your average football game. Including cell phones, it must be close to 100K.
I will definitely pick up a cable, because I did notice improvement when I got rid of the extension I was using to connect to windows. And many people have experienced the same. Also looking at a new phone, probably not Samsung, probably Motorola. I will definitely make sure it MTP/PTP is selectable. By the time I get around to getting it,there will likely be new protocols, though.
Cheers!
Oh, I missed this last night. Like I said, I was in a bit of a fog after repeated failures.Semme wrote:Potential aids: updated firmware *or* this dudes mod. Note the FOUR follow-ups.
Thanks for the continued suggestions. Let me take a look.
I took it one step at a time, this time.Semme wrote:So, you're running Tahr, correct? What have you installed in trying to mount your phone?
I tried smokeys go-mtpfs first.
Then tried the semi-automatic and full-auto pets by candev I believe.
Then I tried MTPdetect -exper -noarch with MTPstatus.
Pretty much I went through the thread and tried everything again. Not sure that I tried gphotofs though.
At this point, I'm most curious about why that Device ID would vary. You don't think that's crucial at this point?
Last edited by SnoopPup on Sun 11 Jan 2015, 02:29, edited 1 time in total.
Not sure why, in terminal,I am unable to CD from /root to /root/Startup to start MTPdetect, but I can open /Startup and start MTPdetect in ROX?
Yeah, I will try to bend the connectors after I run through this one more time. I wanted to duplicate that varied Device ID. Looking it up it looks like my old phone uses the old ESN 8 digit hex Device ID format (xxxx:xxxx), which ran out of IDs so they created MEID which is 14 digits.
After I installed tahrpup, I did not notice a connection to my phone using lsusb. How else would I know it connected in Tahr natively? It would just show up and show my files?
Yeah, I will try to bend the connectors after I run through this one more time. I wanted to duplicate that varied Device ID. Looking it up it looks like my old phone uses the old ESN 8 digit hex Device ID format (xxxx:xxxx), which ran out of IDs so they created MEID which is 14 digits.
After I installed tahrpup, I did not notice a connection to my phone using lsusb. How else would I know it connected in Tahr natively? It would just show up and show my files?
So I went back to Slacko 5.7 as it seemed like I made more progress there.
I can now proceed to where I get the screen reporting AndroidAndroid with the "d" Device ID variance. It appears that MTPdetect will only recognize the "d" which represents the MODEM setting as opposed to the "e" which represents PDA. lsusb will easily detect either setting, but MTPdetect only recognizes it as MODEM even though it can only detect phone when set as PDA, which should show an "e" at the end of the Device ID.
Still puzzled why the Device ID would not be constant, regardless of PDA/MODEM setting, but that appears to be the case.
So I think MTPdetect is seeing my phone as a MODEM with no files to be mounted.
Samsung has issues with this PDA/MODEM protocol or whatever it is. It is necessary in Samsung Kies to switch from PDA to MODEM and back to PDA to connect to KIES on this particular phone. Somebody randomly figured that out and it is on the net. It is also necessary for me to toggle this to shut off USB Mass Storage so that MTP will be active or dominant. There is very little info on net about PDA/MODEM, little that I could find anyway.
I also note that lsusb detects and reports either "download mode" for MODEM "d" setting or "debugging mode" for PDA "e" selection.
I'm starting to fully appreciate why OpenSource is vital. Samsung could open the books on the various bizarre stuff they do. Not a lot different between Samsung and Microsoft. Next phone will be as Open Source as possible and probably not a Samsung. Like all the code and protocols used and embedded in hardware should be free and open. Then
Could still be the cable though, but I still doubt it.
I can now proceed to where I get the screen reporting AndroidAndroid with the "d" Device ID variance. It appears that MTPdetect will only recognize the "d" which represents the MODEM setting as opposed to the "e" which represents PDA. lsusb will easily detect either setting, but MTPdetect only recognizes it as MODEM even though it can only detect phone when set as PDA, which should show an "e" at the end of the Device ID.
Still puzzled why the Device ID would not be constant, regardless of PDA/MODEM setting, but that appears to be the case.
So I think MTPdetect is seeing my phone as a MODEM with no files to be mounted.
Samsung has issues with this PDA/MODEM protocol or whatever it is. It is necessary in Samsung Kies to switch from PDA to MODEM and back to PDA to connect to KIES on this particular phone. Somebody randomly figured that out and it is on the net. It is also necessary for me to toggle this to shut off USB Mass Storage so that MTP will be active or dominant. There is very little info on net about PDA/MODEM, little that I could find anyway.
I also note that lsusb detects and reports either "download mode" for MODEM "d" setting or "debugging mode" for PDA "e" selection.
I'm starting to fully appreciate why OpenSource is vital. Samsung could open the books on the various bizarre stuff they do. Not a lot different between Samsung and Microsoft. Next phone will be as Open Source as possible and probably not a Samsung. Like all the code and protocols used and embedded in hardware should be free and open. Then
Could still be the cable though, but I still doubt it.
- Attachments
-
- Screenshot_2015-01-11_001648.png
- (160.01 KiB) Downloaded 711 times