Related
The xoom can mount just fine on Linux but it is an MTP not a Mass Storage device.
Disclaimer: I am not responsible for any damage to your device, computer, relationship, etc.... The following is meant as a guideline and worked for me but as always use your head.
I did this on my Kubuntu Maverick laptop, but it should apply to most *buntus plus debian. Other flavors should be similar, post a request and I will help if I can. I am familiar with Suse and RHEL/Centos as well but beyond those it will be guess work.
The first thing I would recommend doing is making the device read/write to normal users.
Code:
sudo touch /etc/udev/rules.d/51-android.rules
echo "SUBSYSTEM==\"usb\", SYSFS{idVendor}==\"22b8\", MODE=\"0666\"" |sudo tee -a /etc/udev/rules.d/51-android.rules
sudo /etc/init.d/udev restart
NOTE: This also "fixes" adb so it is useable with the xoom as a normal user. If that is all you want you can stop here.
NOTE 2: You could also set an OWNER rather than changing MODE but I chose the most common route for this example/
Now install either mtp-tools or mtpfs for mounting using FUSE. Since I went the fuse route that is what I will conver here. (I installed the mtp-tools package but beyond using it to debug getting mtpfs to work I have never used it before.)
Assuming you already have fuse configured, for (k|x)ubuntu or debian :
Code:
sudo apt-get install mtpfs
If you do not have fuse already configured then do that first. Look it up online if you have any questions. If you get stuck I will try and help but this post is not about how to configure FUSE.
After that it is simple. Plugin your xoom and from the command line type:
Code:
mtpfs mountpoint
and to dismount it
Code:
fusermount -u mountpoint
so in my case I mount it in a subdirectory under home called xoom
Code:
mtpfs /home/janetpanic/xoom
fusermount -u /home/janetpanic/xoom
I have confirmed moving files to and from the actual directories but not from the meta "playlists" directory. I hope that helps...
EDIT: Fixed Typo... had "(idVendor)" instead of the correct "{idVendor}"
Thanks for sharing your workaround. Unfortunately, it's no joy here. After following the procedure described, the terminal returned no error, but on trying to open the Xoom directory via Nautilus, I received the following message:
Code:
Error: Error stating file '/home/sog/Xoom': Transport endpoint is not connected
Please select another viewer and try again.
Unmounting proceeds without error.
Distribution: Ubuntu Lucid x64
Did you connect your xoom before or after you mounted? The most likely problem is the undeveloped configuration .
Change the line in 51-android.rules to
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="22b8", SYMLINK+="libmtp-%k", MODE="0666"
[\code]
Restart udev and then do a "ls -lah /dev/libmtp*" with the device attached and list the output. I need to figure out if the problem is the udev rule or elsewhere.
If the ls does not show any files then send the result of "lsusb |grep Motorola" which better list a line or there is something weird going on.
Sent from my Xoom using XDA App
Updated 51-android.rules as directed, then:
[email protected]:~$ ls -lah /dev/libmtp*
lrwxrwxrwx 1 root root 15 2011-02-27 19:59 /dev/libmtp-1-4 -> bus/usb/001/004
[email protected]:~$ lsusb | grep Motorola
Bus 001 Device 004: ID 22b8:70a8 Motorola PCS
Wait, you aren't able to get the Xoom to mount as a mass storage device?
ed. The leaked Xoom manual suggests it support mass storage. Phew. You were scaring me there a bit.
as far as I know, it's been confirmed that the current stack does not support mass storage, only mtp.
sogrady said:
as far as I know, it's been confirmed that the current stack does not support mass storage, only mtp.
Click to expand...
Click to collapse
Which stack, Linux or Honeycomb's? Where is it confirmed?
Non-working mass storage is a potential deal breaker.
honeycomb's. see here or here for details.
Thanks for the links.
This is a real WTF.
Can someone try running this attached apk to see if it enables mass storage? (It just runs enable, it won't run disable, so I don't know what will happen, it might cause apps to crash but rebooting should fix it, standard disclaimers apply, you run this at your own risk, etc., etc., etc.)
I don't have a Xoom, otherwise I'd try this myself.
Relevant code snippet for those interested:
Code:
StorageManager s = (StorageManager)getSystemService(Context.STORAGE_SERVICE);
Class c = s.getClass();
Method m = null;
try
{
m = c.getMethod("enableUsbMassStorage", (Class[]) null);
m.invoke(s);
}
catch(Exception e)
{
// TODO Auto-generated catch block
e.printStackTrace();
}
There may even be an easier way to achieve this -- I can't verify for myself because Honeycomb isn't in AOSP -- it doesn't work in the sim, but it might on a device: run adb shell, then run "am start -n com.android.systemui/.usb.UsbStorageActivity".
ydaraishy said:
Can someone try running this attached apk to see if it enables mass storage? (It just runs enable, it won't run disable, so I don't know what will happen, it might cause apps to crash but rebooting should fix it, standard disclaimers apply, you run this at your own risk, etc., etc., etc.)
I don't have a Xoom, otherwise I'd try this myself.
There may even be an easier way to achieve this -- I can't verify for myself because Honeycomb isn't in AOSP -- it doesn't work in the sim, but it might on a device: run adb shell, then run "am start -n com.android.systemui/.usb.UsbStorageActivity".
Click to expand...
Click to collapse
I ran the activity manager command and it brought up the usb mass storage screen but did not mount on computer. Also ran the apk but did not mount. Awesome job though. keep fighting the good fight
sogrady said:
Updated 51-android.rules as directed, then:
[email protected]:~$ ls -lah /dev/libmtp*
lrwxrwxrwx 1 root root 15 2011-02-27 19:59 /dev/libmtp-1-4 -> bus/usb/001/004
[email protected]:~$ lsusb | grep Motorola
Bus 001 Device 004: ID 22b8:70a8 Motorola PCS
Click to expand...
Click to collapse
Well that is interesting . You have read write privileges on the xoom. Sounds like it is a fuse configuration issue. Do you have any other fuse file systems you run?
Sent from my Xoom using XDA App
bigrushdog said:
I ran the activity manager command and it brought up the usb mass storage screen but did not mount on computer. Also ran the apk but did not mount. Awesome job though. keep fighting the good fight
Click to expand...
Click to collapse
Damn it. Looks like I actually need a device to get it working, and the AOSP drop. It's so moronic why they disabled mass storage.
Hmm. Can someone run, from adb shell, the output from "mount", and "ls /sys/devices/platform" for me?
Never mind. Mass storage has been defined out of the stingray (Xoom) kernel. It's not even in the default kernel.
To get mass storage support, be prepared to build your own kernel and reflash the device (once that's done, the am command above or the enabler app will work properly).
I've founded a working(ish) solution. This Xoom forum post details an approach that permits transfer of video/music/etc to the Xoom via Linux.
Couple of caveats:
1. The gnomad2 application is very unstable. Crashes frequently.
2. It appears to be write-only: I have not been able to delete files from the Xoom using this interface.
Thanks for the instructions to connect to a xoom tablet via Linux! However, I'm using Opensuse 11.3 and 11.4 on two different systems. I did install the mtp-tools with no issues, however, there is NO file by the name of mtpfs. A search on the net does not reveal it either. Where do I get this, or what package is it part of? Thanks again. If I can't get this tablet to connect to my linux box, I will have to take it back, since I do NOT use winbloze or Mac. Pretty short sited of Motorola IMHO.
Personally, I've given up on MTP + Linux Combo. I just use a straigt FTP transfer over wifi ( FTP Server on tablet ). It's about the same speeds.
any headway on this...
i am getting the: Transport endpoint is not connected error still and i have no real experience with FUSE so im stuck to using windows for any transferring.
stlsaint said:
i am getting the: Transport endpoint is not connected error still and i have no real experience with FUSE so im stuck to using windows for any transferring.
Click to expand...
Click to collapse
try following the directions in this thread:
http://forum.xda-developers.com/showthread.php?t=981774
They are basically a superset of what I posted. If you still have trouble after that post in either thread (this one or that one) and I will try and help as best I can.
followed the thread up unto the fstab part as i dont wan to edit my fstab without confirmation that it will work. But i get the exact same error with the endpoint text. I am trying this on Crunchbang linux which is based off debain the same way ubuntu is. I am probably going wrong with FUSE somehow but i have never messed with it so i dont know how to troubleshoot it.
Does anyone use the micro usb port? I have yet to find a use for it. I can't transfer files with it, charge with it nor are there any peripherals (that I know of) that can use it. I searched around but couldn't find much useful stuff on the port. All I found was this useless video:
**Ok I can't post the video because of more stupid forum rules but just go to youtube.com and append this after the url: /watch?v=1xBVu-IatDQ **
Anyway, if someone has ideas on how this port can be used I'm all ears... Thanks.
dq
It is a file transfer port. you plug a cable into it and into your PCs usb port. works like the ones on your phone.
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
don quixada said:
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
Click to expand...
Click to collapse
What OS are you using on your computer, and have you installed the drivers for it?
don quixada said:
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
Click to expand...
Click to collapse
Computer OS? i just plugged it into my Win7 system and it was there instantly. 3.0 shows up as a media device, which allows both the tablet and the computer to talk to the sdcard at the same time. So you won't see a mount prompt on the tablet. BTW my Incredible2 is running 2.3 and also lets me access the SD card on it and the computer at the same time.
I'm still using an old tiny xp and it worked fine for me just plugged it in and there it was
I tried Gentoo Linux and XP and neither worked. What drivers do I need to install?
I also have access to a Win7 system so I'll try that.
dq
Drivers from acer website.
I have adb installed should this not be enough?
You need none installed. ADB if its running in some form might be interfering. its just a basic driver in windows it uses.
I only run adb-server when I need it and not all the time. I thought that any needed drivers would have been installed when I installed adb.
For my Gentoo machine what should I do? It's not detected at all if I plug it in. My x10 mini and Nexus One are detected no problem and I can mount them and everything so what's up? Is there a kernel module that I need to build?
Thanks.
dq
I had to download these drivers for my xp netbook ,,
http://global-download.acer.com/GDF...A Tab&Step3=A500&OS=a05&LC=en&BC=Acer&SC=PA_6
I agree with Nova 5. The Windows drivers for USB come with the SDK and while you might not think you will have use for the SDK you will. It makes the process of installing custom ROM,s and Recovery Kernels a breeze. You download your zip flashes or recovery images to Win 7 and then you adb push your downloads to the tablet. The alternatives, unless soneone was nice enough to compile you an apk, which most advanced system developers don,t bother with, unless their app is destined for the massees throug Andriod market, is to install a terminal emulator and enter native Unix/Linux shell commands manually. If you aren't a shell cmd expert I suggest you immediatly download the latest Android SDK for Windows and start learning what it can do for you with just 2 or 3 adb push commands which can help you advoid 10's of lines of manually entered Linux shell commands that can do some real damage to your system if you are copying someone elses terminal emulator sh install instructions, don't understand what they do and make 1 simple typing mistake. With adb push you don't even have to get involved in Linux's complicated bit based permission changes to install something at the system level.
Sent from my A500 using xda premium
Yes, well I only really use adb in the same capacity as what you describe-- to root a device. After that busybox can be installed and I can either ssh into the device (which I prefer) or use the terminal on the device itself.
But my problem is the detection of the device once it is plugged into my Linux box. I'm not sure if I need a special driver for that and I'd rather not aimlessly search through the kernel config in order to build one (I've done that before and it's painful!). It's good to know that one can mount it on an external device and still use it simultaneously though. That will save me time in trying to fiddle around with settings in the tablet itself...
dq
don quixada said:
I have adb installed should this not be enough?
Click to expand...
Click to collapse
If you are not able to transfer files Try enabling usb debugging before connecting to pc.
If the tab is not in the usb devices list and it doesn't show up as an unknown device, you might want to try another usb cable. Or another port if you have the Windows and Linux on the same machine and you are trying to connect on the same port.
Sent from my A500 using XDA Premium App
gradyzero said:
I agree with Nova 5. The Windows drivers for USB come with the SDK and while you might not think you will have use for the SDK you will. It makes the process of installing custom ROM,s and Recovery Kernels a breeze. You download your zip flashes or recovery images to Win 7 and then you adb push your downloads to the tablet. The alternatives, unless soneone was nice enough to compile you an apk, which most advanced system developers don,t bother with, unless their app is destined for the massees throug Andriod market, is to install a terminal emulator and enter native Unix/Linux shell commands manually. If you aren't a shell cmd expert I suggest you immediatly download the latest Android SDK for Windows and start learning what it can do for you with just 2 or 3 adb push commands which can help you advoid 10's of lines of manually entered Linux shell commands that can do some real damage to your system if you are copying someone elses terminal emulator sh install instructions, don't understand what they do and make 1 simple typing mistake. With adb push you don't even have to get involved in Linux's complicated bit based permission changes to install something at the system level.
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Not nearly what I was saying. Not even close enough that a bomb would touch it.
Simple answer is my vista and win7 systems accessed the iconia as a media player device requiring no drivers as they are a common system driver. My only comment about ADB was that it might be interfering if it somehow was left running in the background.
I'm not sure what the problem is, but I had to play around with the settings and plug it in several times and finally it showed up. Now I plug it in and the dialog for auto play shows up instantly. When I choose to view files, I get a window with two drives. One is the internal storage and the other is the sd card.
sandiegoan said:
I'm not sure what the problem is, but I had to play around with the settings and plug it in several times and finally it showed up. Now I plug it in and the dialog for auto play shows up instantly. When I choose to view files, I get a window with two drives. One is the internal storage and the other is the sd card.
Click to expand...
Click to collapse
Sometimes mine gets a bit wonky as well. Every now and then, I'll plug it in, get the windows dialogue box asking me what I want to do. I open it up and the box is blank, no drives, nothing. Unplug it, wait a few seconds, pop it back in, and everything is OK. No rhyme or reason, and it doesn't happen all the time.
Quick trick for win7 .
Plug in the device.go into device manager delete its entry and the USB controller it resides on.unplug device.install driver from acer web site.then try the device again.
This works on several USB type issues
Good luck if you don't understand don't try
With many devices not supporting mass storage anymore Android seemed to have moved from mass storage to PTP and MTP
With Windows supporting MTP by default and Mac OSX with an application there isn't any native support in Linux.
There are a few work arounds like gMTP but that didn't really work for me.
There also is another work around that requires you to edit some files.
To make it easier for others I wrote a little bash script, that does most for you.
Step 1 : sudo apt-get install mtp-tools mtpfs
Step 2 : Plugin your device
Step 3 : Open up a terminal
Step 4 : Type in : “mtp-detect”
Step 5 : Write the PID and VID down, you will need this later
Step 6 : disconnect your device
Step 7 : Download the script and execute it by sudo ./mtp (don't forget to make it an executable first)
Step 8: Follow the instructions on screen and after it's done reboot and plugin your device
Step 9: Use the command "android-connect" to mount your device and "android-disconnect" to dismount
It's not much, but I hope it helped someone.
Please let me know if it worked for your device/distro.
Original post
Tested and working on the P3110 and P5110.
EDIT 1:
(First) time mount can take up to 1-2 minutes, have had where it would mount in a few seconds, others half a minute. Be patient.
mussieonlinux said:
With many devices not supporting mass storage anymore Android seemed to have moved from mass storage to PTP and MTP
Tested and working on the P3110 and P5110.
Click to expand...
Click to collapse
Thanks for this. I think I have tried all this before and it has not worked, but will try again. A few things come to mind though. First, I think you have to turn USB debugging off, right? There is another thread where several of us are able to see the tablet, but not really get any files. Also there is a way to get the tablet to share PTP or MTP and that changes things too (PTP lets me see the top level but no subdirectories).
Will report back if this works or not.
I think USB debugging has to be on, at least for my phone. Mine is always on on all my devices.
Yeah you can see it in the file manager (1 for each SD card) with MTP but you can't access the files.
I am not sure about the PTP.. However for the MTP I just made a new folder in on my other SD card named extSD since MTP shows all directories of both sdcards in one directory.
mussieonlinux said:
I think USB debugging has to be on, at least for my phone. Mine is always on on all my devices.
Yeah you can see it in the file manager (1 for each SD card) with MTP but you can't access the files.
I am not sure about the PTP.. However for the MTP I just made a new folder in on my other SD card named extSD since MTP shows all directories of both sdcards in one directory.
Click to expand...
Click to collapse
Nope doesn't work with or without USB debug. I think the issue may be due to some problem with mtp-tools on 64 bit Linux. Are you running 32?
The mtpfs mounts but any attempt to list the mounted directory just hangs.
I am using 64bit, did you do the reboot and android-connect? If you are using nautilus you wont see your device under "Devices". You will see it above your filesystem.
Can you tell me what isn't working?
mussieonlinux said:
I am using 64bit, did you do the reboot and android-connect? If you are using nautilus you wont see your device under "Devices". You will see it above your filesystem.
Can you tell me what isn't working?
Click to expand...
Click to collapse
Well I'm using Kubuntu so no Nautilus. And I'm just looking at the mount point. My udev rules already have an entry for the mtd device. I also grabbed the latest libmtd and built it from source.
The fuse mount seems to work but any ls on the mount point just hangs forever.
Very strange.
At times like this I miss ubuntu
On my Arch (+XFCE), I use gMTP (uses mtpfs ofcourse). Most of the times it works, and then there are times when it is a pain in the a##. Gets stuck, does not respond, fails to copy what not.
I find the only reliable way is using adb.
Gosh! I push and pull everytime! :silly:
yeah, after a couple of days I found it not very stable at all, so I too switched over to ADB, it's not the fastest method. But we gotta get around, don't we?
I am also waiting for a permanent fix... Just switched back to Ubuntu from Windows 8 Preview, and I love it!!!
The only issue I have at the moment is the fact that I cannot connect directly to the PC from the Tab, although transfer speeds are better by removing the memory card and inserting it into the computer directly. Would be nice to use Rhythmbox to manage my MP3s.
I've tried a few solutions and nothing seems to work fully. I'll give the ideas mentioned above a try.
I have found my peace finally with qtADB.
By far the fastest, and most efficient app for this job.
qtadb[dot]wordpress[dot]com
Worked on my Galaxy S2 (i9100G) with cm10 nightly TY!
Worked only once! i get this...
Hello, this worked greatly on my ubuntu machine. Would this work on an ArchLinux headless PC? I'm willing to try it out if this doesn't mess anything up.
I can confirm this does not work on virtual box not sure on vmware as i dont have it so idk.
[email protected]:~$ android-connect
fuse: bad mount point `/media/GT-P3100': Transport endpoint is not connected
[email protected]:~$
As you can see above, i tried this for P3100. Can someone tell me what am i doing wrong here? I really want to handle my device from Ubuntu 12.04.
hi there,
in newer kernel - at this thime for example debain testing jessie - is kio-mtp implemented. this compinent load your nexus 4 mtp device autmotically like in windows. can access device via filemenager without doing steps in console before. in long time support distribution - example debian stable wheezy - this is not implemented yet. you can compile own your own to get this working
kio-mtp is for kde
gnome-vfs with mtp is for gnome
Works on Kali Linux with 3.14 kernel - HTC One with 4.4.3. Thanks a lot
So I have my Nexus 7. It ran fine when I was under Windows. Now that I'm back to running linux again (Arch Linux) the mass storage isn't working anymore. After a bit of reading around it's apparently because it using the MTP protocol which is a Microsoft based protocol. I understand that there are hacky libraries that I can install that may or may not make it work properly, but that's not what I want. I just want to be able to go back into mass storage mode like it used to be. I don't want to have to deal with some janky proprietary protocol when it isn't necessary. Is there any way to get back mass storage mode like the way it used to be, or are people over android 3.0 just S.O.L? Is there an option is CyanogenMod or is it something they may be working on at some point? The open standards, flexibility and freedom was the entire reason I chose to use android over ios in the first place.. this is really unfortunate.
Not trying to come off as an entitled twat, but this is really frusterating :/
I've never get it to work in Linux. I've tried updating MTP to the latest subversion/cvs and just couldn't get it to do anything.
I have to use adb to transfer anything!
On Ubuntu, I've managed to get it working with mtpfs and gMTP. Not sure how useful that is for Arch though...
rowanparker said:
I've never get it to work in Linux. I've tried updating MTP to the latest subversion/cvs and just couldn't get it to do anything.
I have to use adb to transfer anything!
Click to expand...
Click to collapse
This is what I do as well.
There are ways to get it working but they (for me) were a pain and for some reason yielded super slow transfers.
Sent from my Nexus 7 using Tapatalk 2
HawkiesZA said:
On Ubuntu, I've managed to get it working with mtpfs and gMTP. Not sure how useful that is for Arch though...
Click to expand...
Click to collapse
I use mtpfs and it works, ish.
The bigger the file, the longer it sits there after I use cp, and then after a bit [maybe 10 secs for 350MB file, much longer for bigger files], it will say something about preserving timestamps not being implemented, and it looks like it finished copying. But it has only just started. So I use du to see how big the file is, and for me I get around 14MB/s once it has started transferring. Not too shabby, but the overhead is ridiculous. I want mass storage mode too!
Hi!
I've made a little solution for mounting Nexus 7 to Linux pc.
Using mtpfs was laggy, don't know why, so I used similar tool, called go-mtpfs for that (project link) with some changes (see here).
Just untar attached archive, and run install.sh.
It uses udev to automatically mount and unmount device on plugging/unplugging. (no non-root unmounting though)
Checked on Ubuntu 12.04, but must work with others versions and distros, i guess.
thanks to everyone for your comments and responses. the way everyone is talking it seems really grim... are we really just stuck with trying to make mtp work? there's no way to have it go back into mass storage mode?
i even tried to mount my sd card in cwm and that didn't even work. later on i'm going to try installing twrp to see if that'll allow me to mount my drive properly.
well, neither cwm nor twrp allow me to mount the sdcard. i did a lot of scouring around and i think I may have found why it won't work in recovery either.
It's true that Galaxy Nexus doesn't support UMC because the sdcard is a subfolder of the data partition instead of independent, like in the Galaxy S2. But I was talking about OTG, it is mounting an usb pendrive to save cwm backups there.
Click to expand...
Click to collapse
http://forum.xda-developers.com/archive/index.php/t-1500008.html
i know this is a different device, but i don't see why it would be any different. i'm gunna start mixing and matching kernels with recoveries to see if i can make that work. and if i truly and honestly can't get it working in mass storage mode i'll just stick with adb push.
vpupkin said:
Hi!
I've made a little solution for mounting Nexus 7 to Linux pc.
Using mtpfs was laggy, don't know why, so I used similar tool, called go-mtpfs for that (project link) with some changes (see here).
Just untar attached archive, and run install.sh.
It uses udev to automatically mount and unmount device on plugging/unplugging. (no non-root unmounting though)
Checked on Ubuntu 12.04, but must work with others versions and distros, i guess.
Click to expand...
Click to collapse
Forgot to mention that you have to restart udev
I am finding it's just less hassle to use Airdroid.
gMTP is the only acceptable method I have found in linux but it seems to hang a lot for me.
I found gMTP to be very slow, appearing to hang at times. So I set up Samba and use ES File Explorer on the tablet to access my shared mount points. It's possibly not as fast as AirDroid but is an easy solution, though it means controlling everything from the Nexus 7.
--
Sent from my Nexus 7 using Tapatalk 2
I simply use adb. I was recently turned onto QtADB which is adb with a gui and some other cool features. I would highly recommended it.
I haz no sig
I use gMTP on ubuntu. I really don't have any complaints about it. It does act like it's hanging at times but I've always found it to recover just fine without any additional issues. It's not wicked fast but it does what I need. I often utilize samba and airdroid for specific uses but sometimes I find gMTP to be an easy wired based solution.
mentose457 said:
I simply use adb. I was recently turned onto QtADB which is adb with a gui and some other cool features. I would highly recommended it.
I haz no sig
Click to expand...
Click to collapse
+1000 for you. That solved all my problems working with my files and my android devices.
adb worked perfectly for me! Download the android SDK and then under platform-tools directory,
./adb push <local> <remote>
fgoyti said:
adb worked perfectly for me! Download the android SDK and then under platform-tools directory,
./adb push <local> <remote>
Click to expand...
Click to collapse
Yes but how fast (slow) does it transfer? 1MB/s?
Sent from my SCH-I500 using xda app-developers app
I transferred 500MB in 1-2 minutes. Sorry, didn't record anything more specific but even at 2 min, that works out to 4MB/s which ain't bad
As many have suggested, just read up on adb and use that. If you need to get something off the N7 and dont quite remember were it went to.. adb shell and cd to the sdcard and ls the dir. It'll print everything cd in to the next folder you think it may be in ls.. it'll show the contents. If you dont like having to put things into the android-sdk-linux/platform-tools and then having to cd into that dir everytime. Just add the platform-tools to your PATH and you can issue commands through any directory. It is very unfortunate that MTP leaves us Linux users in the dark.
Also, if you have a rooted kernel such as Siyah for the Galaxy S2, it lets you force mass storage mode. I haven't tested this but it looks like it should work for linux
ÜBER™ said:
As many have suggested, just read up on adb and use that. If you need to get something off the N7 and dont quite remember were it went to.. adb shell and cd to the sdcard and ls the dir. It'll print everything cd in to the next folder you think it may be in ls.. it'll show the contents. If you dont like having to put things into the android-sdk-linux/platform-tools and then having to cd into that dir everytime. Just add the platform-tools to your PATH and you can issue commands through any directory. It is very unfortunate that MTP leaves us Linux users in the dark.
Click to expand...
Click to collapse
Well, with some little configuration, it's not a big thing to configure MTP or even automount-MTP on Linux systems. A small introduction you can find in my blog http://anddisa.blogspot.de
Sent from my Nexus 7 using xda app-developers app
Hello, nookies!
Today I have decided to make an easy-to-follow guide on mounting USB devices (cameras, USB sticks) on your Nooks! Hooray! :good:
DISCLAIMER - I am not responsible if you brick your Nook, break your USB device, the current state of the economy, or why Obama is the president. Please do research on these topics if you would like to know more.
DISCLAIMER 2 - I did not make either of the apps attached, I have merely posted them here for easy access.
So let's get started with some prerequisites!
Prerequisites:
A rooted Nook Touch or Nook Touch Glow with software 1.2.1 installed, as well as Superuser and su binary installed
A terminal app (attached below)
Renate NST's UsbMode.apk (attached below)
A USB host-enabled kernel correctly installed and working (see my signature for a Nook Touch Glow one)
A USB OTG cable
Steps:
Make sure that your Nook is completely charged before continuing!
Make sure that your kernel is definitely working and that USB mode is properly working, too!
1. Open up Renate NST's UsbMode.apk app. Tap the "Off" button. (This will stop your Nook from trying to charge itself from the USB device by turning off the current.)
2. Plug your USB OTG cable (without anything attached to it) into your Nook's USB port.
3. Tap "Host" in the UsbMode app. (This turns on Host mode.)
If the LED beside your Nook's USB port has turned solid green at this point, you are doing well!
4a. For USB devices that have a separate cord (cameras): Turn on the USB device. Plug its cord into its USB port. Now, connect both the device's cord and the device into the open end of the OTG cable that is attached to your Nook.
4b. For USB sticks/drives: Plug the drive directly into the open end of the OTG cable that is attached to your Nook.
5. Tap "View USB" in the UsbMode app. You should see the Nook's main listing at the top, as well as the plugged-in device's listing under it. The device's listing should have a black dot next to it.
Good job! You're doing well so far! :laugh:
6. Now, open up the Terminal Emulator app I attached below. You should have installed it already. When it opens, you should see a dollar sign ($) at the far left of each line.
7. Type in
Code:
su
. Now, instead of a $, there should be a # at the far left of each line.
8. Type in
Code:
mount -o rw,remount rootfs /
. This remounts /system as read-writable.
9. Type in
Code:
mkdir /usb
. This creates a directory called /usb in the root of your Nook's filesystem; it will be used to mount your USB device in.
10a. For USB devices (cameras, etc.), first type in
Code:
mount -t vfat /dev/block/uba /usb
. You will get some sort of error message, that's okay. Now, after typing that, type in
Code:
mount -t fvat /dev/block/uba1 /usb
.
10b. For USB sticks/drives. just type in
Code:
mount -t vfat /dev/block/uba1 /usb
.
11. If the above commands worked properly, you should now be able to go into a file explorer, navigate to the /usb directory, and boom! You can now manage your USB device's filesystem straight from your Nook!
Unmounting your USB drive
It is important that you unmount your USB device/drive properly before physically taking it out of your Nook. Here's how to do that.
1. Open up your Terminal Emulator app again.
2. Type
Code:
su
.
3. Type
Code:
mount -o rw,remount rootfs /
.
4. Type
Code:
umount /usb
.
5. Type
Code:
rmdir /usb
.
6. Take the whole cord/USB drive out of your Nook with the OTG cable.
7. Open up the UsbMode app again.
8. Tap "Auto". (This turns your Nook's current back to being automatically determined, instead of being off.)
9. Tap "Peripheral". (This makes your Nook return to having the ability to charge from an AC outlet (or whatever).)
10. You have successfully unmounted your device!
Hope this helps all of you guys who want to manage your USB devices on your Nooks! :good:
Reserved
Reserved for future use/expansion.
I hate to do this, but...
Bump.
I'm sure that someone can profit from this tutorial, right?
There was a whole thread on using my modified volume daemon to do this all automatically.
I've pretty much abandoned that train of thought.
I'm not really sure that anyone really wants to mount USB drives.
It's really a pretty current-intensive way to get data.
It's better to just use a 32 GB SD card in the Nook, formatted with something better than vfat.
Renate NST said:
There was a whole thread on using my modified volume daemon to do this all automatically.
I've pretty much abandoned that train of thought.
I'm not really sure that anyone really wants to mount USB drives.
It's really a pretty current-intensive way to get data.
It's better to just use a 32 GB SD card in the Nook, formatted with something better than vfat.
Click to expand...
Click to collapse
thanks for the efforts @Renate NST in creating the USB mode app, I really envy you guys for the knowledge and understanding you have of the tech involved.
I agree with you on the practicality of the application.
At the same time and more we can never let go off the THRILL in trying the invaluable efforts you manage to put in.
Kudos.
Coming back to the thrill of it all ...
@NoogiE ... thanks for the link to this thread ...
i am on 1.3.4 version of your 1337 ROM, assuming the USB kernel is in place, i opened @Renate NST's USBMode app and pressed Off, then i connected the OTG cable and pressed Host ... no action no led action ... if you can help ... thanks.
thanks,
aiamuzz said:
no action no led action ...
Click to expand...
Click to collapse
Hmm. You have this rooted and the UsbMode is not showing any "<errors>"?
You're sure that it's an OTG cable? (I've never seen one over 6" long. If you know of a longer molded cable, please tell me!)
You're sure that your kernel has the OTG fix?
You should get a quick flash (50 mS or so) out of the LED just pushing the host button on UsbMode even with nothing connected at all (no adapter).
With an adapter connected you should get a solid LED.
I've never gotten into writing/patching kernel drivers, but I always thought that someone would fix the buggy USB driver so that UsbMode would not be needed for regular OTG operation.
Renate NST said:
Hmm. You have this rooted and the UsbMode is not showing any "<errors>"?
You're sure that it's an OTG cable? (I've never seen one over 6" long. If you know of a longer molded cable, please tell me!)
You're sure that your kernel has the OTG fix?
You should get a quick flash (50 mS or so) out of the LED just pushing the host button on UsbMode even with nothing connected at all (no adapter).
With an adapter connected you should get a solid LED.
I've never gotten into writing/patching kernel drivers, but I always thought that someone would fix the buggy USB driver so that UsbMode would not be needed for regular OTG operation.
Click to expand...
Click to collapse
Hey thanks for looking into it @Renate NST ...
I am using the small 4-5 inch cable ... had a spare lying around.
I am not getting the quick flash you talk about while a press the Host button.
However when i open the USB Mode app the first line 'Request' shows empty, when i press the Host button it says <write error>
when i engage the buttons (off, 100mA, 500mA, 1.5A & Auto) the Max Current line blinks between <write error> and Auto ...
If that helps !!!
and the kernel part, I am running a copy of Yattaro and Nookie's 1337 ROM(the latest 1.3.4) which claims it supports USB host capability.
Is there any way i can run a command to check if the kernel supports ? Not that i doubt/question this ROM developers efforts/claims.
aiamuzz said:
Hey thanks for looking into it @Renate NST ...
I am using the small 4-5 inch cable ... had a spare lying around.
I am not getting the quick flash you talk about while a press the Host button.
However when i open the USB Mode app the first line 'Request' shows empty, when i press the Host button it says <write error>
when i engage the buttons (off, 100mA, 500mA, 1.5A & Auto) the Max Current line blinks between <write error> and Auto ...
If that helps !!!
and the kernel part, I am running a copy of Yattaro and Nookie's 1337 ROM(the latest 1.3.4) which claims it supports USB host capability.
Is there any way i can run a command to check if the kernel supports ? Not that i doubt/question this ROM developers efforts/claims.
Click to expand...
Click to collapse
You seem to be having a an su binary issue. Check and see if the su binaries are in /system/bin; if they aren't, copy them there from /system/xbin and reboot. Should work like a charm.
ИΘΘK¡€ said:
You seem to be having a an su binary issue. Check and see if the su binaries are in /system/bin; if they aren't, copy them there from /system/xbin and reboot. Should work like a charm.
Click to expand...
Click to collapse
hey Nookie ... copied the su to to /system/bin and the led came up ... but i can't see the connected device under 'View USB', could it be bcos i am using a Micro SD card on in USB adapter ?
PS: and hey i saw swapon and swapoff files(binaries?) in /system/xbin, does it mean your ROM supports SWAP ? With swap and hopefully NookKat the RAM deficit could be manageable ? My first Android Device was LG Optimus Pro, C660 which had 256 MB RAM & 140-160 MB internal storage for apps, The stock ROM used to keep popping the close any programs popups every now and then rather freqeuntly, On a custom CM7 official port ROM with swap support & dark tremors ap2sd scripts, i was able to get rid of the annoying pop up and install 60-70 user apps to SD card and still have a daily ROM. Do you think our device supports a similar setup with swap and darktremors aap2sd scripts ?
thanks
Quick N00b question- I am trying to get a GPS signal into my rooted NST. It has a micro USB. Do I need to do this in order for an app to get my serial signals?
I will paypal someone to help me get GPS signals into my NST using an app called Simple Sailor! Thx
lolokai said:
Quick N00b question- I am trying to get a GPS signal into my rooted NST. It has a micro USB. Do I need to do this in order for an app to get my serial signals?
I will paypal someone to help me get GPS signals into my NST using an app called Simple Sailor! Thx
Click to expand...
Click to collapse
Maybe. I'd have to look into your quest more to know for sure.
ИΘΘK¡€ said:
Maybe. I'd have to look into your quest more to know for sure.
Click to expand...
Click to collapse
Thx Nookie.
Is an app that can see what serial data is being provided via USB? Or, a GPS testing app that grabs data from the USB. Do apps always look for GPS data to come in via USB or is there another place that an app would look for GPS data?
lolokai said:
Thx Nookie.
Is an app that can see what serial data is being provided via USB? Or, a GPS testing app that grabs data from the USB. Do apps always look for GPS data to come in via USB or is there another place that an app would look for GPS data?
Click to expand...
Click to collapse
To tell you the truth, I don't think either of those exist. I could be wrong, though - @Renate NST has done some stuff using an old GPS puck on her Nook, so you can ask her.
ИΘΘK¡€ said:
To tell you the truth, I don't think either of those exist. I could be wrong, though - @Renate NST has done some stuff using an old GPS puck on her Nook, so you can ask her.
Click to expand...
Click to collapse
Hey thanks Nookie. I have found some info from both Top hat Soaring (glider people who needs daytime screen visibility as well as ADV riders - motorcycle navigation with again, daytime visibility) so I'll be pursuing those. Thanks again.
I looked into all this a while ago.
You should be able to go right from serial into the LocationProvider.
Strangely enough, most of the stuff I saw back then was using the mock location to handle the data.
This seemed like a detour to me.
I really should follow this up.
Using USB host mode and serial USB is not optimum due to the wackiness in the USB driver and the current draw.
This is a 1.8V GPS module: https://www.sparkfun.com/products/10890
Besides the advantage of low voltage/low power, the 1.8V serial can interface internally and directly to the Nook.
I think that I'll be ordering one of these.
I do not know anything about programming.
But I can do all the manual. ))
What am i doing wrong?
Excuse me. Forum does not post a link to the picture. I'm new here ... It is necessary to dial 10 messages.
You must manually copy the link in Internet Explorer.
http:
//i5.imageban.ru/out/2015/08/27/
1dcc71f5ed606d4e51a1c7ed10cec568.png
Nik782 said:
I do not know anything about programming.
But I can do all the manual. ))
What am i doing wrong?
Excuse me. Forum does not post a link to the picture. I'm new here ... It is necessary to dial 10 messages.
You must manually copy the link in Internet Explorer.
http:
//i5.imageban.ru/out/2015/08/27/
1dcc71f5ed606d4e51a1c7ed10cec568.png
Click to expand...
Click to collapse
It looks like your Nook is not recognizing any drives being plugged into it.
Can you give me some more details on your progress thus far?
NOOK!E said:
It looks like your Nook is not recognizing any drives being plugged into it.
Can you give me some more details on your progress thus far?
Click to expand...
Click to collapse
Here is my story in detailed illustrations.
https:
//ww
w.dropbox.com/sh/47n1bhgd3usq15q/
AAAh5uIrxWnVWbbgoXY7PQy3a?dl=0