Develop Bugs

How to connect Galaxy Nexus to linux pc

Hi all!
I just bought a Galaxy Nexus, and I've already a problem: how to connect it to my linux computer?
You know that ics use MTP protocol to interface with computers. Maybe it's good for windows users, but with ubuntu I can't let the phone be recognized by the pc. I tried this guide http://www.reddit.com/r/Android/comments/ne6ud/mount_your_new_galaxy_nexus_from_the_unity/ but it doesn't work, when i click "mount galaxy nexus" it shows an error message ("the socked is not connected").
Can you help me, please?

Use airdroid or something similar. It will save you many hours of pain
Sent from my Galaxy Nexus using Tapatalk

Evostance said:
Use airdroid or something similar. It will save you many hours of pain
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
You're right if you need to transfer just some files. But I've to transfer all my music (about 4/5 GB) and my photos and videos (about 1 GB). Using something like airdroid, I will die before it ends

try installing mtpfs
i keep meaning to try it on fedora

bleets said:
try installing mtpfs
i keep meaning to try it on fedora
Click to expand...
Click to collapse
I've already installed it, but it doesn't work. Almost, on ubuntu.
When I try to mount the phone it shows an error message.
Another question is: why, if i connect the phone using PTP protocol it works, the pc recognize the phone, but it seems to have just 700 MB of free memory? (realy there are more than 12 gb)

Metallaro said:
Hi all!
I just bought a Galaxy Nexus, and I've already a problem: how to connect it to my linux computer?
You know that ics use MTP protocol to interface with computers. Maybe it's good for windows users, but with ubuntu I can't let the phone be recognized by the pc. I tried this guide http://www.reddit.com/r/Android/comments/ne6ud/mount_your_new_galaxy_nexus_from_the_unity/ but it doesn't work, when i click "mount galaxy nexus" it shows an error message ("the socked is not connected").
Can you help me, please?
Click to expand...
Click to collapse
I ended up installing Windows 7 in virtual box. In the end it was easier to do that then to continue wasting time getting Ubuntu 11.04 to play the MTP game

Just installed mtpfs from source and it works fine...doesnt look like it will auto mount when you plug it in though.
this might help

bleets said:
Just installed mtpfs from source and it works fine...doesnt look like it will auto mount when you plug it in though.
this might help
Click to expand...
Click to collapse
I used this guide some month ago when I had a motorola xoom. Now if I try to mount my phone, it shows an icon named "xoom", but if I try to open it it shows this error message
(the message was in italian, i tryed to translate it in english but it's difficult)
Code:
[B]Impossible to show «/home/marco/Galaxy Nexus».[/B]
Error: Error in executing the file stat "/home/marco/Galaxy Nexus": the destination socket is not connected. Please chose another viewer (??) and try again
Edit: no, wait. I used another guide to connect the xoom to the computer, but I can't find it again. Anyway, if i try to follow the guide you linked, when I write
mtpfs mountpoint
the console shows this error message
fuse: bad mount point `mountpoint': No such file or directory

mtpfs mountpoint = mtpfs /whereyouwanttomount to
for instance i do
Code:
mtpfs Mounts/nexus
so you have to make the folder where you want to mount to
for instance in your shell, in your home folder
Code:
mkdir nexus
(by the way, it's best to avoid folder names that include spaces)
then to mount to that folder you'd do
Code:
mtpfs nexus
or if you're currently cd'd in a different folder
Code:
mtpfs /home/marco/nexus
simples
the guy in that post even did an example to show you a bit furthery down :|

I found gMTP works quite well, though I just recently switched from Gentoo to Arch and unfortunately gMTP isn't as stable as it was in Gentoo.

Grr...I don't have enough posts yet to post links but if you do a google search for:
omgubuntu galaxy mtp
The first link in the list is the guide I used and it works great.

http://www.omgubuntu.co.uk/2011/12/...eam-sandwich-phone-to-ubuntu-for-file-access/
this is what i used, because i like to do stuff myself. there is also a script if you like automated stuff. good luck

If anyone knows how to get it working on 10.04 let me know ;-)
Sent from my Galaxy Nexus using Tapatalk

I followed the instructions on the websites. It connects using MTP but only allows music playlists. Change the USB setting on the phone to Camera (PTP) and Ubuntu recognises the file system on the internal sd card.

I will try this
Sent from my Galaxy Nexus using Tapatalk 2

[5/4/2013] Running real linux on your Kindle

---
DISCLAIMER: THIS IS A REALLY GOOD WAY TO EFF UP YOUR KINDLE IF YOU DON'T KNOW WHAT YOU ARE DOING!!!
IF YOU DON'T KNOW WHAT ADB, PARTED, OR WHAT LINUX IS, YOU MIGHT WANT TO JUST CLICK THE BACK BUTTON!
---
Most that know Android, knows that it's just fancy UI and API on top of Linux, but it's still not quite Linux... But what if you want to run real Linux on your tablet?
Well, it's actually not that hard to do, but certainly not for n00bs...
Need to know: Linux, fastboot, adb, parted, etc.
You will also need the mkbootimg program, fastboot, working ADB, etc.
And a USB OTG adapter and working USB keyboard.
(this is assuming you already have modded your kindle with the usual FFF+TWRP 2.1+CM9)
The first step is to do a little repartitioning, so boot the Kindle into recovery, and run an 'adb shell'.
Then run 'parted'.
The idea here is to basically maintain the stock layout, while making room for linux...
Which can be done a few ways, the easy way would to just delete 'media', then recreate it much smaller (I did 1GB).
Then make one more new partition, using the remaining flash memory (should be a little over 4GB).
Making sure to reassign the name 'media' to partition 12, you can also name the new linux partition 'linux' or whatever, if you like.
After that, quit parted, and create the new FS on the new linux partition (mke2fs -Text4 /dev/block/mmcblk0p13, but you should know that already ).
Then reboot the tablet, get back into Android, it may or may not complain about the 'SDCARD' needing to be formatted, which should be done anyway, since it changed in size.
Do another 'adb shell', mount the new linux partition to a useful place, you can just mount over '/mnt' if you like, it won't hurt anything. Exit out of the shell.
Download this pre-built Debian rootfs I found:
http://rcn-ee.net/deb/rootfs/wheezy/
Unpack that file on your host machine, then use 'adb push' to copy the armel-rootfs tar to the Kindle's '/mnt'.
'adb shell' back into the kindle, and change to '/mnt' and untar the armel rootfs tar file... Maybe go to the bathroom, get a drink, get some fresh air or something, it'll take a little time to do it's thing.
After that's done, download my rc.local and 'adb push' that to '/mnt/etc' and make sure to ungzip it, and chmod is 0777 (or is it 0766, either should work lol).
http://www.mediafire.com/?gx46xxb4813n5ob
Then you can delete the rootfs tar file if you like, get out of '/mnt', and unmount it.
Linux is now installed, easy eh?
Now, download my kernel (acutally it's Hashcode's kernel, but with needed changes):
http://www.mediafire.com/?2lqex9j5bgws0b1 (Updated 6/11/2012)
Using mkbootimg:
'mkbootimg --kernel zImage --ramdisk /dev/zero --cmdline "root=179:XX" --base 0x80000000 -o boot.img'
Where XX is the partition that you put linux on (if following this exactly, should be 13), you should now be able to use /dev/mmcblk0pXX as well, if that doesn't work just use 179:XX.
Then using fastboot, boot the kernel package:
'fastboot boot boot.img'
While it says 'waiting for device...", reboot the Kindle and wait for it to download and boot the package.
Then wait for the linux login!
Plug in your favorite USB keyboard, a USB 1.1 one works best I've found.
The root password for that rootfs package is just 'root'.
-------------
Now, the fun part: Internet access, the hard way.
I'm still working out getting the WIFI modules working, so you'll have to use it tethered via USB... Which means no keyboard, but you can still log in by SSH.
In my kernel, instead of being an 'android' USB devices, it's a multifunction USB gadget with ethernet, serial port, and mass storage.
Mass storage works, but a little buggy sometimes.
Serial port seems broken for some reason.
Ethernet is what we're after.
Now the rc.local I made, in addition to enabling the video overlay (so there's a framebuffer console on the LCD), it also sets up the ethernet USB gadget.
I set the IP address to 192.168.5.1, which really should be out of the common IP range that most people use, but if it conflicts, then you can edit rc.local before you push it over above.
On your Linux host, with the Kindle plugged in, bring up the USB ethernet interface:
'ifconfig usb0 192.168.5.2 netmask 255.255.255.0'
After that, maybe try pinging the kindle (192.168.5.1), to make sure everything is working... If it is, you should have no problems connecting with SSH and logging in.
Once you can connect/login by SSH, you'll need to add your host machine as the default gateway ('route add default gw 192.168.5.2'), then edit '/etc/resolve.conf' and add a DNS server (add your ISP's DNS, or use 4.2.2.1).
After that, you should have internet access on the kindle side via SSH, and should be able to download/install your favorite Debian packages.
Oh, did I mention that you'll need a IP forwarding/NAT service running on your linux host too? I'll have to refer to linux manuals on how to do that, but if you can do all this, you should have no problems doing that.
I should also say that this CAN technically be done in windows as well, since all the needed programs are available in WIN32 bins, but you won't be able to get tethered network access working, because Microsoft doesn't support CDC ethernet devices.
Have fun!
OH! And X works fairly well with the omap3 video driver, just so long as you DON'T touch the screen, the touch screen driver currently crashes X on input.
So fair warning, make sure you know how to navigate X with just a keyboard, unless you have a OTG working hub and can use a keyboard and mouse, or have a wireless keyboard/mouse combo of some kind.
Update 6/11/2012:
Uploaded new kernel (link above), touch screen is now working, though no multitouch.
I have a boot loader with multiple boot options, http://www.mediafire.com/?l6aaqgsdkiksfw0
To use it, make a partition named "linuxboot", and flash your linux's boot.img created with the above instructions.
Still working on wifi.
Update 6/11/2012:
Ok, WIFI is working... Not sure why it wasn't before.
Here are the modules: http://www.mediafire.com/?139hold2a2l9vbl
Don't forget to run depmod.
You'll also have to copy the firmware from android system partition in /etc/firmware and copy it to Linux /lib/firmware

In case no one believes me, here's a console dump (typing blind of course, this was an early attempt with no LCD):
Code:
d.
.
Starting periodic command scheduler: crond.
FATAL: Could not load /lib/modules/3.0.21+/modules.dep: No such file or directory
Debian GNU/Linux 5.0 carrier tty1
carrier login: usb 1-1: new low speed USB device number 2 using musb-hdrc
usb 1-1: device v0b38 p0010 is not supported
input: HID 0b38:0010 as /devices/platform/omap/musb-omap2430/musb-hdrc/usb1/1-1/1-1:1.0/input/input4
generic-usb 0003:0B38:0010.0001: input: USB HID v1.10 Keyboard [HID 0b38:0010] on usb-musb-hdrc-1/input0
input: HID 0b38:0010 as /devices/platform/omap/musb-omap2430/musb-hdrc/usb1/1-1/1-1:1.1/input/input5
generic-usb 0003:0B38:0010.0002: input: USB HID v1.10 Device [HID 0b38:0010] on usb-musb-hdrc-1/input1
root
Password:
Last login: Sun May 27 21:55:28 UTC 2012 on tty1
Linux carrier 3.0.21+ #40 SMP PREEMPT Sun May 27 16:59:27 CDT 2012 armv7l
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
carrier:~# echo skdjfhnsdkjfshdsummit_bat_notifier_call val=41
summit_smb347 4-0006: summit_fsm_stateTransform:state : suspend(0) -> suspend(0) ; event : EVENT_BATTERY_NTC_NORMAL
kfjshdkjfshdfkjshdfkjsdhfkjsdhfkjsdhfkjshksdjfhskjdhfskjdhfsdkjfhsdkjfh > /dev/fb0
carrier:~# echo skdjfhnsdkjfshdkfjshdkjfshdfkjshdfkjsdhfkjsdhfkjsdhfkjshksdjfhskjdhfskjdhfsdkjfhsdkjfh > /dev/fb1
-bash: echo: write error: No such device
carrier:~# omap-rproc omap-rproc.1: rproc_loader_cont: failed to load ducati-m3.bin
cat /dev/vcs1 > /dumpp.txt
I was trying to get something to come up on the framebuffer, to no avail of course.
The backlight comes on, and it seems like it want to work, but there's nothing.

Are you talking about a true Debian dual-boot on our tablet? That could be really awesome .
Envoyé depuis mon Amazon Kindle Fire avec Tapatalk

Actually, yes.
It's mostly a matter of having a proper framebuffer console and telling the kernel to use a root instead of using the initrd to setup android.
If we could get a scripted bootloader, one that would give a customizable boot menu, you could easily boot whatever you wanted.

And what about it : http://thomaspolasek.blogspot.fr/2012/04/arch-linux-lxde-w-xorg-mouse-keyboard_16.html?m=1 ?
Envoyé depuis mon Amazon Kindle Fire avec Tapatalk

Well, I already got most of that working, chroot environment is easy.
I got the full Linux init going, no android at all... just no display.

seishuku said:
Well, I already got most of that working, chroot environment is easy.
I got the full Linux init going, no android at all... just no display.
Click to expand...
Click to collapse
Display might be tricky, as we are currently using the very latest graphics modules from TI. I'm not sure if you can use those in our current build.
That being said you could send a cat /proc/msg to a file during boot and that might contain your error.
Sent from my Amazon Kindle Fire using Tapatalk 2

Well I already have a working fbcon in android, but it seems the display just isn't being enabled in Linux.
I've tried "echo 1 > /sys/devices/omapdss/display0/enabled" to force it on, but nothing.
The back light is already on though...

I thought EXT2 was for really old linux distros.
Sent from my Kindle Fire using XDA

Not really, its just more compatible.
I could have made pretty much anything...

I read somewhere that SSDs should use EXT4.

i am really anxios to see this even though is only cmd line.
will the steps to get this going available even for SSH commands?

I really should hack together a wifi script to get some kind of network connection, would make working on it a little (lot) easier.
The idea here though is to basically have a full linux, to operate exactly like it would on a PC.
With a working framebuffer console, an X.org config can be made and X should work just fine with the touch screen too.
The end result, with just keyboard, should be a full blown linux system.

The real question is how long it would take to compile android for.. itself.
Sent from my Amazon Kindle Fire using Tapatalk 2

Hashcode said:
The real question is how long it would take to compile android for.. itself.
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
They can start reproducing them selves, isn't this how terminator started?
Sent from my LG-VM670 using Tapatalk

Hashcode said:
The real question is how long it would take to compile android for.. itself.
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
pbailey212 said:
They can start reproducing them selves, isn't this how terminator started?
Sent from my LG-VM670 using Tapatalk
Click to expand...
Click to collapse
This is really off topic but Hashcode's comment and pbaileys phone reminded me of a test project Drew (of Team Hydro) did where he chrooted ubuntu onto an LG-LS670 and compiled a kernel for it natively, took just under 3 hours.

I'm at a bit of a loss here... if I disable surfaceflinger, so I keep my android fb console, then if I disable the display and reenable it, I lose the console.
Also, in my initrd, I can remove everything except ueventd and still keep the console... so something ueventd (init) is doing to enable the console.
In Linux I can play with enabling/disabling the display, but nothing seems to provoke Linux to give me an actual console.

Sblood86 said:
This is really off topic but Hashcode's comment and pbaileys phone reminded me of a test project Drew (of Team Hydro) did where he chrooted ubuntu onto an LG-LS670 and compiled a kernel for it natively, took just under 3 hours.
Click to expand...
Click to collapse
On the vm670 legend has it, people have compliled whole roms in 30 minutes, with an optimus v, and Leslie Ann's build server
sent from my Nokia 5110

Aha! Got it!
http://www.youtube.com/watch?v=PXhnVP3lWLU
For whatever reason sysfs wasn't taking my commands.
Now I can work out some bugs and get X working.
I also switched the USB gadget from android to an Ethernet CDC, so I can SSH via USB while I get wifi working.
Edit-
Sorry about the super blurry video, my phone's camera is having "issues".

Ok, I've switched to the official Debian armel wheezy distro (basically just formatting my linux partition and untaring the distro), seems to have fixed a lot of problems... One being aptitude not working correctly (seen in the video).
I need to enable some kind of ip forwarding on my local linux install, so I can get a temp internet connection on the kindle via USB gadget ethernet cdc (ssh and http already works).

[Guide] ADB connection between two Android devices

Probably not breaking any ground here (since in hindsight it was blatantly obvious), but I thought I would share anyways...
I own several Android devices, and I'm always playing. well, tonight I was tweaking a few things over adb and got to wondering if I could use adb to connect from one Android device to another. Well, turns out it's pretty easy, if you're rooted...
Both devices need to be connected to the same wireless network.
Install adbWireless from the Playground (sorry, Play Store): https://play.google.com/store/apps/...251bGwsMSwyLDEsInNpaXIuZXMuYWRiV2lyZWxlc3MiXQ..
You only really need it on the receiving device, but I have it on everything anyway.
Copy the Linux adb binary into /system/xbin/ and set the permissions to 755 (rwxr_xr_x), and reboot.
You only really need to do this on the controlling device, but may as well do it on all.
Fire up adbWireless on the receiving device, grant root privileges, and note the IP address
Fire up a Terminal Emulator on the other device, and enter: adb connect <IP address from other device> (you typically don't need to add the :5555 on the end.
Job done! Pretty handy when working from a slate!
I also run dd-wrt firmware on my router, which let's me assign static IPs by MAC address, so the IP for the devices are always the same.
Regards - dr

adb binary is already built in, /system/bin/adb.
besides that, all that's left is get adbd running, and that can be achieved either by an app (like you suggest) or edit init.rc to have adbd as one shot service to allow manual start (doesn't boot with the system). cyanogenmod also has adbd over wireless done like this.
also, one could use an OTG cable to connect devices directly, while i agree adb over wireless is good, adb over ssh would be best.

Valid points.
The adb in /system/bin is a less functional version than the standard Linux binary (94kb versus 156kb); kinda similar to the chown binary, where the recursive function doesn't work...
I'll concede to the rest though...

danger-rat said:
Valid points.
The adb in /system/bin is a less functional version than the standard Linux binary (94kb versus 156kb); kinda similar to the chown binary, where the recursive function doesn't work...
I'll concede to the rest though...
Click to expand...
Click to collapse
Agreed.
Sent from my i9250
edit: checkout this commit @aosp-master: https://android-review.googlesource.com/#/c/41846/
i'll be cherry-picking this one today

danger-rat said:
Valid points.
The adb in /system/bin is a less functional version than the standard Linux binary (94kb versus 156kb); kinda similar to the chown binary, where the recursive function doesn't work...
I'll concede to the rest though...
Click to expand...
Click to collapse
Hi - Where can I get this more functional binary that's half the size of a standard linux binary? I've tried two, they are both around 330Kb, and they fail to run with error "non executable: magic 7F45" because they were not compiled for my ARMV71 processor. I ran chmod 755 on it and when I check the permissions it is executable (-rwxr-xr-x). Can you post a link to the one that's 156kb - I can't find it.

elfaure said:
Hi - Where can I get this more functional binary that's half the size of a standard linux binary? I've tried two, they are both around 330Kb, and they fail to run with error "non executable: magic 7F45" because they were not compiled for my ARMV71 processor. I ran chmod 755 on it and when I check the permissions it is executable (-rwxr-xr-x). Can you post a link to the one that's 156kb - I can't find it.
Click to expand...
Click to collapse
Bumb. Anyone home? Shoot me a link please.

Hey guys,
Now, I have a tablet (running android) and is rooted already (so, I'm ready to get any needed binary on my device). It supports OTG. When I plug in my phone (rooted) using OTG to my tablet, my phone says 'Android debugging enabled' in notifications, is also charging. When I go to TE (Terminal Emulator) of my tab and type: 'adb devices', it displays no device in the list of attached devices (obvious).
And yes, my tab has got OTG host modules in kernel because when I turn on USB mass storage on (in my phone), my tab detects it and I can use it.
Now, my question:
Can I actually do this? i.e., using adb in my tablet (for my phone) via OTG?

Can we run adb from the device to detect itself?
I'm sure you can see why this would be amazing and powerful.. possibly giving root to apps on non-rooted devices with adb's run-as com.package.apk and such?
Is this possible? To have adb run on the Android device and connect to itself? If it is, can you guide me to where to learn it?
Dave :cyclops:

[HOW-TO] Working MTP in Ubuntu

I got ubuntu working with MTP on my Galaxy Nexus (and A500) using instructions for the Nexus 7. I have documented these at my website.
http://www.winters.org.nz/android-hints-tips-stuff/working-mtp-on-ubuntu
This setup is the only one I have managed to get working, I am using Ubuntu 12.10, and it should work for earlier versions.

Thanks mate, I'll have a look. Also got Gnex, A501 and Ubuntu 12.10 :laugh:

j3r3myp said:
Thanks mate, I'll have a look. Also got Gnex, A501 and Ubuntu 12.10 :laugh:
Click to expand...
Click to collapse
I found that connecting more than one device at a time didnt work - could be something in how the udev config is..
If you post the device ids for the 501 (i guess they are different), then I can add that to my page..

I'll have to give this a try as well, as I've had no luck connecting my gnex to Windows XP, Windows 7, Ubuntu or Linux Mint. I'll be trying it out today on Ubuntu 12.10, and will report back later. Fingers crossed!
Sent from my Galaxy Nexus

dustrho said:
I'll have to give this a try as well, as I've had no luck connecting my gnex to Windows XP, Windows 7, Ubuntu or Linux Mint. I'll be trying it out today on Ubuntu 12.10, and will report back later. Fingers crossed!
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
It automatically works in windows
Sent from my Galaxy Nexus using Tapatalk 2

Dri94 said:
It automatically works in windows
Click to expand...
Click to collapse
Well, it may work for you, but it has never worked for me in XP or 7. Others have experienced this as well.
Sent from my Galaxy Nexus

Use web based few manager...
Sent from my Galaxy Nexus using Tapatalk 2

This method works great on Ubuntu 12.04.
Works for me in Windows XP and Windows 7 as long as I turn off USB Debugging

kiwi_mat said:
I got ubuntu working with MTP on my Galaxy Nexus (and A500) using instructions for the Nexus 7. I have documented these at my website.
http://www.winters.org.nz/android-apps/working-mtp-on-ubuntu
This setup is the only one I have managed to get working, I am using Ubuntu 12.10, and it should work for earlier versions.
Click to expand...
Click to collapse
First of all thanks a lot for solving this long pending issue.
Everything worked for me mounting, data transfer through MTP, but while unmounting I am getting an error saying that "umount: /media/Nexus mount disagrees with the fstab"
I am using Ubuntu 12.04, Nexus 4.1.2

use wifi explorer pro its web based....
https://play.google.com/store/apps/details?id=com.dooblou.WiFiFileExplorerPRO&hl=en

techie.raj said:
First of all thanks a lot for solving this long pending issue.
Everything worked for me mounting, data transfer through MTP, but while unmounting I am getting an error saying that "umount: /media/Nexus mount disagrees with the fstab"
I am using Ubuntu 12.04, Nexus 4.1.2
Click to expand...
Click to collapse
when the nexus is connected issue the mount command in a terminal, you should see something like..
Code:
DeviceFs(Galaxy Nexu on /media/GalaxyNexus type fuse.DeviceFs(Galaxy Nexu (rw,nosuid,nodev,allow_other,user=username)
its possable your device name is different, so check the fstab line,
Code:
DeviceFs(Galaxy\040Nexu) /media/GalaxyNexus fuse.DeviceFs(Galaxy\040Nexu) allow_other,rw,user,noauto 0 0
the DeviceFS (both) must match above except the space in the mount listing has to be replaced with \040 as space is the field separator in fstab..

zac68 said:
Works for me in Windows XP and Windows 7 as long as I turn off USB Debugging
Click to expand...
Click to collapse
Does USB Debugging have to be turned off in order for this to work in XP and 7? I haven't tried that before, so that's something else I'll have to try.

dustrho said:
Does USB Debugging have to be turned off in order for this to work in XP and 7? I haven't tried that before, so that's something else I'll have to try.
Click to expand...
Click to collapse
In XP I have to do it. Windows 7 with Service Pack 1, from memory might not of be as fussy. I could be wrong though. I use Ubuntu these days.

Am I misssing something here? It connects automatically with my Ubuntu 12.10 without having to configure anything. It does not in fastboot state though.
Sent from my Galaxy Nexus using Tapatalk 2

Sucks... between myself and my room mate, we've tried this on three different systems (lubuntu, xubuntu, ubuntu - 12.10 in each case) and had no luck with it. Neither with the Nexus 7 or the G Nex.

Works perfectly -- EXCEPT when multiple devices are connected. Is it possible to make go-mtpfs recognise the devices and mount them correctly? Right now when there are multiple devices it just gives up.

kiwi_mat said:
when the nexus is connected issue the mount command in a terminal, you should see something like..
Code:
DeviceFs(Galaxy Nexu on /media/GalaxyNexus type fuse.DeviceFs(Galaxy Nexu (rw,nosuid,nodev,allow_other,user=username)
its possable your device name is different, so check the fstab line,
Code:
DeviceFs(Galaxy\040Nexu) /media/GalaxyNexus fuse.DeviceFs(Galaxy\040Nexu) allow_other,rw,user,noauto 0 0
the DeviceFS (both) must match above except the space in the mount listing has to be replaced with \040 as space is the field separator in fstab..
Click to expand...
Click to collapse
Hi Thanks for your reply. Sorry for the delay in replying....
Your suggestion couldn't solve my problem.
My fstab entry is as follows
DeviceFs(Galaxy\040Nexu) /media/Nexus/ fuse.DeviceFs(Galaxy\040Nexu) allow_other,rw,user,noauto 0 0
Click to expand...
Click to collapse
and the mount command that I executed are (command and corresponding output are )
DeviceFs(Galaxy Nexu on /media/Nexus type fuse.DeviceFs(Galaxy Nexu (rw,nosuid,nodev,allow_other,user=raj)
bash: syntax error near unexpected token `Galaxy'
Click to expand...
Click to collapse
Second attempt
DeviceFs(Galaxy\040Nexu on /media/Nexus type fuse.DeviceFs(Galaxy\040Nexu (rw,nosuid,nodev,allow_other,user=raj)
bash: syntax error near unexpected token `Galaxy\040Nexu'
Click to expand...
Click to collapse
Could you understand where the problem lies.
Am I doing any thing wrong....
Thanks a lot for your efforts...

Error in /etc/fstab
1st: thanks for your work doing it for all
2nd: I use an Acer Iconia Tab A501 running Android 4.xy
I followed the instruction. I did the following line in my /etc/fstab
DeviceFs(A501) /media/A501 fuse.DeviceFs(A501) allow_other,rw,user,noauto 0 0
-----------> it comes an error message "/bin/sh: 1: DeviceFs(A501): not found"
(The id_modell=Acer_Iconia_Tab_A501. I tried, but the same error.)
------- snip ---(28.12.2012-thk)------> usb-devices:
T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 14 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0502 ProdID=3345 Rev=99.99
S: Manufacturer=Acer
S: Product=Acer Iconia Tab A501
S: SerialNumber=1234567890
C: #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=00 Driver=usbfs
------- snap ---------
Where is my fault?

Next step
emmerich1234 said:
1st: thanks for your work doing it for all
2nd: I use an Acer Iconia Tab A501 running Android 4.xy
I followed the instruction. I did the following line in my /etc/fstab
DeviceFs(A501) /media/A501 fuse.DeviceFs(A501) allow_other,rw,user,noauto 0 0
-----------> it comes an error message "/bin/sh: 1: DeviceFs(A501): not found"
(The id_modell=Acer_Iconia_Tab_A501. I tried, but the same error.)
------- snip ---(28.12.2012-thk)------> usb-devices:
T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 14 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0502 ProdID=3345 Rev=99.99
S: Manufacturer=Acer
S: Product=Acer Iconia Tab A501
S: SerialNumber=1234567890
C: #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=00 Driver=usbfs
------- snap ---------
Where is my fault?
Click to expand...
Click to collapse
Try to understand the source code (go langualge) and may be append the A501?

Has anyone had an issue accessing it?
Could not display "/media/GalaxyNexus".
Error: Error when getting information for file '/media/GalaxyNexus': Transport endpoint is not connected
Please select another viewer and try again.
I know the udev configuration looks fine and adb works fine and it tries to mount the device for MTP but I get the above error. I'm not using Ubuntu but my go-mtps install has been updated on git and I have the latest version of fuse and followed the instructions.

Ubuntu Newbie - Cant connect via Terminal

Hi. I mistakenly spilled a glass of water over my MacBook and it is now destroyed (No Aple Care). While I am saving up for a new machine I am using Ubuntu 16.04 on a QNAP 453 Pro.
Everything work fine but i cant get it to recognise my phone in Terminal. When I connect the phone it shows the phone icon but i cant connect. It hasnt asked for authorisation on the phone to use the QNAP so
I can understand why its not showing up when i go into terminal and its not showing up as an attached device.
I tried this -
[email protected]_1604:~/Downloads/platform-tools$ sudo jmtpfs /home/admin/media/myphone
Device 0 (VID=18d1 and PID=4ee2) is a Google Inc (for LG Electronics/Samsung) Nexus 4/5/7/10 (MTP+ADB).
libusb_open() failed!: No such file or directory
LIBMTP PANIC: Unable to initialize device
terminate called after throwing an instance of 'MtpErrorCantOpenDevice'
what(): Can't open device
Aborted
As the title says I dont know much about Ubuntu. Any help would be most appreciated. Thanks.

edit - I am running Stock 7.1.2 beta with an unlocked bootloader.

Do you have debugging enabled in Developer Options on the Pixel?

CZ Eddie said:
Do you have debugging enabled in Developer Options on the Pixel?
Click to expand...
Click to collapse
Yeah and when connected its set to transfer files.