Vnc Viewer Kali Linux Android
Thora Buckner
UPDATE: There are several, better alternatives to Airdroid now. However, it seems most Linux distros are now working with MTP fairly well. I know in my experience, Mint (Ubuntu based) works out of the box, as does Manjaro (Arch based). If it doesn't work out of the box or natively, then be sure to search your package manager for an MTP solution.
Newer versions of Android mount storage as an MTP device instead of mass storage. The benefit to this is simultaneous access on the Android device and the PC. Unfortunately, while Windows supports it natively just fine, linux solutions are fairly buggy as of right now.
Currently, the most reliable (and it still is a little flaky to get going, but once connected is fine) that I have found is go-mtpfs. Here is a link to help you get it set up. You have to mount/dismount from command line. There is also a unity launcher in that thread if you're on Ubuntu unity, however.
The best option, though, unless you are transferring a lot of data, is to use something like AirDroid. It is a free app in the play store for local network transfers, and provides a web interface to use with your computer's browser. It even provides a drag and drop file interface, as well as even allowing access for sms messaging, call logs, app installs, and many other things.
Among a lot of functionality, it has an FTP server. So, if you can network your phone and your computer, you can easily transfer files both ways from your computer. I do it all the time from Ubuntu and Fedora machines (via Thunar).
Linux doesn't have a reliably working hassle free fast native (directly mountable via the kernel; FUSE doesn't cut it) MTP implementation. In order to work with your MTP devices, like ... Linux based Android phones you'd better use ... Windows or MacOS X. Update: a Russian programmer was so irked by libMTP he wrote his own complete Qt based application which talks to the Linux kernel directly using libusb. Meet Android-File-Transfer-Linux.
NB: You have to tell the phone to use USB for file transfer or PTP so that thunar can see it. On my OnePlus5 android 9, there's a notification when I plug in the USB cable that allows me to choose connection options.
I used this free and open source Android FTP server and found it straightforward. You specify a username and password, then run the FTP server (it's very clear whether the server is running, and easy to enable/disable).
The only downsides are that it's probably a little slower than it would be with an efficient USB protocol, and that FTP is not secure (everything is in cleartext). It should be possible to do the same thing, but with an Android SFTP server; I just haven't personally found one yet.
I've found that it only works for USB if I use the cable supplied with that device or a similar device. The USB cable from my defunct Samsung tablet works fine with my Android Onix replacement. The only thing that works for my phone is that cable that came with it. Other USB charging / transfer cables don't work or not fully: won't copy .mp3 files for example. No idea why this is. But non device cables often don't show up as a USB device attachment.
An sdcard is normally an exfat file system, which is by default not recognized by Ubuntu by default -- I do not know if this is the case with other distributions. To make my Ubuntu 16.04 LTS to be able to write to an exfat file system I did:
In Linux Mint 19.1 transferring large numbers of photos can easily be done by activating Developer Options, and the going into the Android phone 'Settings' 'Developer Options,' 'USB Configuration." Then choose PTP (Picture Transfer Protocol) instead of MTP.Now photos will transfer at lightning speed just using the file explorer.
I am running Mint 19.2. My phone is a Pixel 1st Gen running Android 10. After google'ing for a solution and trying the MTP options suggested by many without success, I found that if you go to Settings -> Connect devices -> USB and change "USE USB FOR File transfer/Android Auto", Nemo mounts the phone's storage and gives access to the devices files. My phone was set the "No data transfer". Now had I checked the USB settings first the MTP solutions may have probably worked. As a side note, none of the suggested solutions on StackExchange, HowToForge or OMG! mentioned checking the USB settings on the phone first. I did read a few posts that MTP on Mint "works out of the box". But again, no mention of checking your phones settings. Hope this helps.
Please bear in mind that I can connect from my home to this ubuntu computer, and can connect from ubuntu to my home as well, and can connect on my home to my phone as well(over wifi on same network or 4g).
I have the same issue on the 18.04. I did notice that if I called up the properties dialogue for the phone it displays a password box which appears to be able to accept input. The Windows version of teamviewer connects without any password for the phone so maybe the linux version is configured differently with respect to secuity?
As a corporate customer we also have this issue. I can't see an obvious way of opening a support case with this corporate account, so I can escalate this issue. Is this the only support mechanism with TeamViewer (this forum)?
Also why does this just fail silently, shouldn't it say you can't connect your Linux box to Andorid when you try? Also shouldn't any client connection to any other client, seems pretty shoddy that this isn't the case!
Is there still no solution for linux to use the remote mobile supprt? having this same problem right now... Most of our developers (at least our android developers) use linux (ubuntu), so quit a missing link for us.
Using TeamViewer for Linux 15.4.4445 was trying to connect to QuickSupport 15.4.61 QS, the host was connected and prompted for approval of connection and when confirmed the viewer would disconnect. On another attempt viewer has stated that another session is already opened, and refuse connection.
Given the fact that this statement is over a year old right now, shouldn't there be any progress? I spent a couple hours trying to find the reason why the connection to my android device just failed silently. When the desktop app shows "ready to connect" I do indeed expect it to be ready to connect... Would it really be so hard to at least provide a message saying "Sorry, we don't fully support the OS that you're on."?
If it is that they don't want to expend resources to include what they apparently believe is an inconsequential environment (Linux), perhaps they can share the program requirements for so doing to the community, select the best piece of code as a template, and refine the requirements. Iterate until the module meets internal QC requirements, incorporate into code base. Does this help?
This is getting ridiculous. I asked support over a year ago and they said they'd fix this issue in a future version. How long do we have to wait? I'm using a supported version of Linux and a Samsung Tab Active3. I'm a paying corporate customer. Doesn't seem like they are working on this at all. It used to work in previous versions of Teamviewer but they evidently broke something. Our support staff use a mix of Windows and Linux. What? I'm meant to scrap our Linux systems because of this app? I'm using Teamviewer because they're partnered with IBM and this is what IBM uses for remote support in MaaS360.
Again I suffered from this! Wanted to help a person with android. And the behavior was exactly the same as in first message. After several hours I remembered that I already found that bug several years ago. And yes, from Windows virtual machine to Android it works as expected.
When I wanted to report that when I first found it, I did not commented here, because I though "me too" comments do not add much value. However, after the problem hangs for so long, probably this at least will help them to realize that problem does really exist.
I had the same problem and spent hours to debug this due to no error and warning message by the App. Eventually I realized that TeamViewer don't support Andriod mobile connection to Linux PC when I tried to connect Android mobile to Windows PC.