I am posting here because this issue does not occur from my Windows machine on the same LAN.
When I use Ubuntu to connect to my Android device (all on the same LAN), both sides show the connection being made. After the connection negotation, the Android device shows that I'm connected ("connected to kevin"), but no control window appears on Ubuntu. Then, after about 5 seconds, the connection closes, and it just shows that I'm ready to connect again.
Here's the last part of the log:
*Logs Removed by Moderator*
Let me know if more of the log is needed.
I've also tried using my mobile data connection instead of wifi on the Android device - same result.
This is Ubuntu 16.04 running TeamViewer 13.0.6634. Android device is ZTE Axon 7 running TeamViewer Host and QuickSupport 13.0.7847. I also have the ZTE plugin for TeamViewer.
PS: I can connect from Ubuntu to Windows without issue.
Solved! Go to Solution.
Is there a way to tell why my post got rejected? It is showing up in my rejected posts.
I thought maybe it was because I included a pastebin link (it was just a TV log), so I removed that link. But I don't think it made a difference.
Sorry about that. Your post wasn't so much "Rejected" as it was "Spam Filtered".
There are a lot of not so friendly people posting junk to the community, so we have a bot battling them, unfortunately you got caught in the crossfire.
But, not to worry, we do check through the filtered stuff and pull back out stuff that is legitimate when they are occasionally caught. I pulled yours back out just now. And, yes, it was probably the logfiles that got you recognised as spam.
Also, we do ask all users not to post logfiles as they can inadvertently give away to much info.
Hope this helps!
The last two lines of the log, which have no personally identifiable data, are:
2018/02/04 09:51:15.690 6563 S! UdpConnection: UDP statistics: nb=25 2018/02/04 09:51:15.725 6563 S IProcessCommandHandler::CmdEndSession(): Received CMD_ENDSESSION with reason: 1
I tried searching for "reason 1" but didn't find anything. Does anyone know what that means?
I have a same issue. Unable to connect from ubuntu to android phone.
I am also seeing the same behavior trying to connect from Linux client 14.0.14470 to QuickSupport on Android 7.1.
Carrier::CmdEndSession(): Received CMD_ENDSESSION with reason: 1
I found competing product to work in this application instead. It would be great if TeamViewer restored this functionality that has been dropped for over a year.
It's been over a year since this problem was posted here. Can we get an update on when we may expect to see this functionality return to the Linux client?
Using Windows machines or TV12 isn't really feasible in a Linux shop running corporate licensed TV14.
TV team! We, Linux users realy need to get working TV with Android devices. We paid for licenses but din't got working solution!
Actually, for me TV12 is working.
The following constellation works: TV12 (.deb, i386, 18.04 Bionic Ubuntu) connects to my DotOS Android (8.1 Oreo, latest host apk running) via TV login.
After installation of the .deb, I needed to resolve the missing dependencies ("sudo apt -f install") and then also restart the teamviewer daemon ("sudo service teamviewerd restart").
Good luck ...
Actually, for me TV12 is working.
Of course that feature is working in TV12. TV12 is essentially the Windows application packaged with its own bundled WINE libraries. This thread is about the feature not working on the Linux native clients, which start at TV13. For those of us who have kept our TV host deployments up to date, using obsolete TV12 is not an option since it cannot connect to TV hosts newer than TV12.
Of course that feature is working in TV12.
Would you have read the full thread, you would have noted that users are trying to overcome the problem that TV13 and V14 does not work on Ubuntu with an Android running the host apk, and that at least one person had the issue that the suggested workaround of using TV12 instead was not working. I was merely assuring that person that the workaround is indeed a solution and working.
If TV would fix the incompatability issues with TV14, we surely would not have that discussion. But for now, the TV14 on Ubuntu cannot access a TV host running on an Android phone as descriped in the initial posting.
Btw. for the rest, I am running 18.04 64bit but used the TV12 i368 .deb ... amd64 was not working. Maybe this was the original issue of user @Mark_F ...?
Good luck and have fun with controlling your Android devices from Ubuntu ... OpenSource, the only way to go!