Can't connect to Android device from Linux

[mandrivnyk]

Can't connect for remoteControl/Sharescreen from Linux to my Android Phone.

From Mac/Windows it works as expected.

Steps: 

1. Open TeamViewer on Ubuntu desktop.

2. OPen QuickSupport on Android device

3. Entering ID to Partner ID field on TeamViewer.

4. Press Connect

5. On Android device new dialog appearing: "Would you like to allow <name> to remote support your Android device?". Press "Allow" button

6. On Android device showing spinner for 5-10 seconds

7. Android device show main screen with my ID and status at the bottom: "Ready to connect"

What is wrong? Need assist, Let me know if you need additional details

Host:

OS: Ubuntu 17.10

TeamViewer version: 13.0.9865

Date: Feb 12 2018 15:30:36

Client device:

Android: 8.1.0

Device: Nexus 6P

QuickSupport version: 13.1.8602 QS

Host version: 13.1.8602 HM

[RalphFox]

Had this problem as well.

Host:

OS: Ubuntu 16.04
TeamViewer version: latest as of 16/07/2018: 13.1.8286
Date: May 30 2018 15:56:29

Client device:

Android: 8.0.0
Device: Samsung Galaxy Note 8
QuickSupport Samsung version:  latest as of 16/07/2018: 11.0.4766 QS
Host version: latest as of 16/07/2018: 13.1.8752 HM

Tried using same network and different networks. (pc and phone on same wifi network, pc on cable or wifi, and phone on 4G.)

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).

More info:

Using my Wifi and 4G:

Connecting through "HOST" app on phone(replaced possible private info with XXXXXXXXX):

Spoiler

018/07/16 08:46:44.712 27585 140149928273664 S Activating Router carrier
2018/07/16 08:46:44.712 27585 140149928273664 S CProcessCommandHandlerMasterConnect[20]::CreateMasterConnect(): master3.teamviewer.com:5938, Connection 26, proxy=''
2018/07/16 08:46:44.946 27585 140149919880960 S CProcessCommandHandlerMasterConnect[20]::HandleMasterConnect(): Sending MasterCommand client=TV&connectionmode=1&f=RequestRoute2&homeserver=&ic=XXXXXXXXX&id=XXXXXXXXX&id1=XXXXXXXXX&id2=XXXXXXXXX&licensedremoteaccesstypes=0&mid=XXXXXXXXX&midv=1&v=13.1.8286
2018/07/16 08:46:45.192 27585 140149911488256 S CProcessCommandHandlerMasterConnect[20]::ReceivedMasterResponse(): Received MasterCommand CONNECT@XXXXXXXXX_10800_128000_XXXXXXXXX_XXXXXXXXX_10000__1_0_XXXXXXXXX_128000_XXXXXXXXX:128000;XXXXXXXXX:1280000;4:640000_XXXXXXXXX_XXXXXXXXX_BR-SAO-ANX-R005.teamviewer.com_ef/XXXXXXXXX/XXXXXXXXX
2018/07/16 08:46:45.192 27585 140149911488256 S! TcpCarrierBase[20]::SendCompleteQueue(): No Connections, Type_Tcp, Dir_Outgoing, Ending 0, SendQueue 1, CurrentSendQueue 0, SendCache 0
2018/07/16 08:46:45.193 27585 140149911488256 S Activating Router carrier
2018/07/16 08:46:45.193 27585 140149911488256 S CommandHandlerRouting[21]::CreateActiveSession(): outgoing session to XXXXXXXXX via BR-SAO-ANX-R005.teamviewer.com, protocol Tcp
2018/07/16 08:46:45.193 27585 140149911488256 S Carrier[20]::EndCarrierInternal(): ClientID: 0 SupportsEndSession: 0, SupportsCCmd2: 0, SessionType_MasterConnect, SendQueue: 0 (4 Bytes), CurrentSendQueue: 0 (0 Bytes), SendCache: 0 (0 Bytes)
2018/07/16 08:46:45.585 27585 140149911488256 S Negotiating session encryption: server hello received
2018/07/16 08:46:45.742 27585 140149919880960 S Negotiating session encryption: server handshake received, encryption established with AES key length 256
2018/07/16 08:46:46.030 27585 140149911488256 S UDP: send handshake: (*)
2018/07/16 08:46:46.031 27585 140149903095552 S PseudoRoutableCmdHandler[21]::StartPseudoRouter(): PseudoRouter has been started
2018/07/16 08:46:46.031 27585 140149903095552 S CPersistentParticipantManager::AddParticipant: [XXXXXXXXX,XXXXXXXXX] type=6 name=XXXXXXXXX
2018/07/16 08:46:46.031 27585 140149903095552 S CParticipantManagerBase InteractionDefaults arrived : CInteractionDefaults = (0) [ 0,2,0,0,2,0,0]
2018/07/16 08:46:46.032 27585 140149903095552 S CParticipantManagerBase participant XXXXXXXXX (ID [XXXXXXXXX,XXXXXXXXX]) was added with the role 6
2018/07/16 08:46:46.032 27585 140149903095552 S CPersistentParticipantManager::OnParticipantRoleChanged the participant [XXXXXXXXX,XXXXXXXXX] has changed the role from 0 to 6
2018/07/16 08:46:46.037 27585 140149919880960 S CPersistentParticipantManager::AddParticipant: [XXXXXXXXX,XXXXXXXXX] type=6 name=XXXXXXXXX
2018/07/16 08:46:46.037 27585 140149919880960 S ReadStreamParameters(): streamID=1 type=5 (StreamType_Chat), source=[XXXXXXXXX,XXXXXXXXX], features=1, compression=2
2018/07/16 08:46:46.195 27585 140149928273664 S UDP: ProcessHandshake2: (*)
2018/07/16 08:46:46.195 27585 140149928273664 S Initializing transmission control v2
2018/07/16 08:46:46.195 27585 140149928273664 S UDP: sending pings...: (*)
2018/07/16 08:46:46.198 27585 140149903095552 S CPersistentParticipantManager::AddParticipant: [XXXXXXXXX,XXXXXXXXX] type=3 name=samsung_SM-N950F_XXXXXXXXX
2018/07/16 08:46:46.198 27585 140149903095552 S CParticipantManagerBase participant samsung_SM-N950F_XXXXXXXXX (ID [XXXXXXXXX,XXXXXXXXX]) was added with the role 3
2018/07/16 08:46:46.198 27585 140149903095552 S CPersistentParticipantManager::OnParticipantRoleChanged the participant [XXXXXXXXX,XXXXXXXXX] has changed the role from 0 to 3
2018/07/16 08:46:46.207 27585 140149919880960 S UDP: UHP.PING response received: (*)
2018/07/16 08:46:46.209 27585 140149911488256 S ReadStreamParameters(): streamID=2 type=14 (StreamType_RemoteSupport), source=[XXXXXXXXX,XXXXXXXXX], features=1, compression=2
2018/07/16 08:46:46.234 27585 140149903095552 S UDP: UHP.PING response received: (*)
2018/07/16 08:46:46.253 27585 140149911488256 S UDP: UHP.PING response received: (*)
2018/07/16 08:46:46.253 27585 140149911488256 S UDP: punching: (*)
2018/07/16 08:46:46.253 27585 140149911488256 S UDP: PingOK.RequestUDP: (*)
2018/07/16 08:46:46.254 27585 140149911488256 S UDP: send UDPFLOW_REQUESTUDP: (*)
2018/07/16 08:46:46.266 27585 140149903095552 S ReadStreamParameters(): streamID=3 type=5 (StreamType_Chat), source=[XXXXXXXXX,XXXXXXXXX], features=1, compression=2
2018/07/16 08:46:46.313 27585 140149919880960 S UDP: UHP.PING response received: (*)
2018/07/16 08:46:46.321 27585 140149928273664 S CParticipantManagerBase InteractionDefaults arrived : CInteractionDefaults = (0) [ 0,2,0,0,2,0,0]
2018/07/16 08:46:46.345 27585 140149919880960 S UDP: UHP.PING response received: (*)
2018/07/16 08:46:46.511 27585 140149919880960 S UDP: SendUDPPunches: (*)
2018/07/16 08:46:46.561 27585 140149919880960 S UDP: punch received a=XXXXXXXXX: (*)
2018/07/16 08:46:46.561 27585 140149919880960 S UDP: send UDPFLOW_PUNCHRECEIVED: (*)
2018/07/16 08:46:46.561 27585 140149919880960 S UDP: SendUDPPunches: (*)
2018/07/16 08:46:46.561 27585 140149919880960 S UDP: received punch: (*)
2018/07/16 08:46:46.623 27585 140149911488256 S UDP: UDP send possible: (*)
2018/07/16 08:46:46.625 27585 140149903095552 S UDP: send UDPFLOW_MTUTESTRECEIVED (size = 448): (*)
2018/07/16 08:46:46.629 27585 140149919880960 S UDP: send UDPFLOW_MTUTESTRECEIVED (size = 1008): (*)
2018/07/16 08:46:46.701 27585 140149911488256 S UDP: send UDPFLOW_UDP_PREPARE_SWITCHTOUDP 2: (*)
2018/07/16 08:46:46.701 27585 140149911488256 S UDP: send/receive possible: (*)
2018/07/16 08:46:46.701 27585 140149911488256 S UDP: create udp connection was successful: (*)
2018/07/16 08:46:46.778 27585 140149911488256 S CarrierContainer.ProcessCarrierSwitch: state=1, carrier=2
2018/07/16 08:46:46.778 27585 140149911488256 S Activating UDP carrier ...
2018/07/16 08:46:46.778 27585 140149911488256 S CarrierContainer.SendCarrierSwitch: state=2, carrier=2

 When the connection ended suddenly (went from "Connection Accepted" to "Ready to Connect"):

Spoiler

2018/07/16 08:46:56.209 27585 140149911488256 S! UdpConnection[28]: UDP statistics: nb=26
2018/07/16 08:46:56.209 27585 140149928273664 S CarrierContainer.SendCarrierSwitch: state=2, carrier=1
2018/07/16 08:46:56.210 27585 140149928273664 S UdpCarrierDeactivationState::DiscloseStateToCarrier: empty send buffer is not flushed
2018/07/16 08:46:56.210 27585 140149928273664 S Activating Router carrier
2018/07/16 08:46:56.249 27585 140149903095552 S Carrier[21]::CmdEndSession(): Received CMD_ENDSESSION with reason: 1
2018/07/16 08:46:56.257 27585 140149919880960 S CGatewaySession[21]::EndSession(): Session to XXXXXXXXX ended. Estimated capacity=36571kBit/s, Latency=56ms

 Logs on my phone(also stripped of possibly identifying info):

Spoiler

2018/07/16 08:42:36.197 9316-9316 I/ActivityManager activityStarted com.teamviewer.host.ui.HostActivity@XXXXXXXXX

2018/07/16 08:42:36.199 9316-9316 I/ActivityManager activityResumed com.teamviewer.host.ui.HostActivity@XXXXXXXXX

2018/07/16 08:42:36.231 9316-9316 I/NetworkServiceStateStart Start network service

2018/07/16 08:42:36.263 9316-9316 I/NetworkService Start network.

2018/07/16 08:42:36.264 9316-25578 I/TeamViewer TeamViewer is going online!

2018/07/16 08:42:36.264 9316-9358 I/TeamViewer CKeepAliveClientClient::DoReconnectInternal: doing nothing, state = 0

2018/07/16 08:42:36.265 9316-9358 I/TeamViewer Activating Router carrier

2018/07/16 08:42:36.266 9316-9316 E/Connectivity ------------- ConnectivityStatusChange -------------

2018/07/16 08:42:36.266 9316-9316 E/Connectivity -

2018/07/16 08:42:36.266 9316-9316 E/Connectivity - No connectivity: false

2018/07/16 08:42:36.266 9316-9316 E/Connectivity - FailOver: false

2018/07/16 08:42:36.266 9316-9316 E/Connectivity - Reason: null

2018/07/16 08:42:36.266 9316-9316 E/Connectivity -

2018/07/16 08:42:36.266 9316-9316 E/Connectivity - Active network -

2018/07/16 08:42:36.266 9316-9316 E/Connectivity - Type: WIFI

2018/07/16 08:42:36.266 9316-9316 E/Connectivity - State: CONNECTED

2018/07/16 08:42:36.266 9316-9316 E/Connectivity - Failover: false

2018/07/16 08:42:36.266 9316-9316 E/Connectivity - Roaming: false

2018/07/16 08:42:36.266 9316-9316 I/KeepAlive Start

2018/07/16 08:42:36.266 9316-9316 I/KeepAlive Connecting

2018/07/16 08:42:36.269 9316-9353 I/TeamViewer CKeepAliveClientClient::HandleStartKeepAlive: doing nothing, state = 1

2018/07/16 08:42:36.302 9316-9357 I/TeamViewer CKeepAliveClientClient::HandlePing(): success

2018/07/16 08:42:36.303 9316-9357 I/TeamViewer Activating Router carrier

2018/07/16 08:42:36.304 9316-9357 I/TeamViewer CProcessCommandHandlerMasterConnect[28]::CreateMasterConnect(): master13.teamviewer.com:5938, Connection 42, proxy=''

2018/07/16 08:42:36.623 9316-9354 I/TeamViewer CProcessCommandHandlerMasterConnect[28]::HandleMasterConnect(): Sending MasterCommand addonchannels=0&client=TVHM&f=Login&getdeviceauthenticationtoken=1&gw=0&gwlevel=400&hideonlinestatus=0&httpout=0&ic=XXXXXXXXX&id=XXXXXXXXX&iguid=XXXXXXXXX&language=pt&licensetype=10000&mid=XXXXXXXXX<~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~XXXXXXXXX&midf=32&midhistory=0x768_000000000000_0000000<~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~XXXXXXXXX|m000000000000~~~~~~~~~~~~~~~<~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~XXXXXXXXX<~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~XXXXXXXXX|XXXXXXXXX<~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~XXXXXXXXX&midv=2&noofactivekeepalive=0&os=And8.0.0&port443out=0&rhash=XXXXXXXXX&runtime=0&smidv=3&sro=0&supportedfeatures=XXXXXXXXX&tcpout=1&usednsnames=1&v=13.1.8752 HM

2018/07/16 08:42:36.932 9316-9359 I/TeamViewer CProcessCommandHandlerMasterConnect[28]::ReceivedMasterResponse(): Received MasterCommand OK_10000_-_2__GB-MAN-ANX-R004.teamviewer.com:5938_33602_1_-1_0.0.0.0__XXXXXXXXX_XXXXXXXXX_0_XXXXXXXXX_1_0_0_0_XXXXXXXXX__AT-KLA-ANX-R001.teamviewer.com,BG-SOF-ANX-R005.teamviewer.com,CA-MON-IBM-R004.teamviewer.com,CA-VAN-ANX-R002.teamviewer.com,CH-ZRH-ANX-R008.teamviewer.com,DE-CGN-PLS-R019.teamviewer.com,DE-DUS-PLS-R003.teamviewer.com,DE-FRA-INT-R005.teamviewer.com,DE-HAM-PLS-R003.teamviewer.com,FR-PAR-ANX-R001.teamviewer.com,FR-PAR-IBM-R004.teamviewer.com,GB-LON-ANX-R004.teamviewer.com,GB-MAN-ANX-R003.teamviewer.com,IT-MIL-ANX-R006.teamviewer.com,IT-MIL-IBM-R002.teamviewer.com,IT-MIL-IBM-R001.teamviewer.com,SE-STO-ANX-R004.teamviewer.com_ef/XXXXXXXXX_XXXXXXXXX

2018/07/16 08:42:36.933 9316-9359 W/TeamViewer TcpCarrierBase[28]::SendCompleteQueue(): No Connections, Type_Tcp, Dir_Outgoing, Ending 0, SendQueue 1, CurrentSendQueue 0, SendCache 0

2018/07/16 08:42:36.936 9316-9359 W/TeamViewer CKeepAliveClient::HandleLoginUserAnswer(): KeepAliveServer GB-MAN-ANX-R004.teamviewer.com:5938

2018/07/16 08:42:36.937 9316-9359 I/TeamViewer Activating Router carrier

2018/07/16 08:42:36.938 9316-9359 I/TeamViewer Carrier[28]::EndCarrierInternal(): ClientID: 0 SupportsEndSession: 0, SupportsCCmd2: 0, SessionType_MasterConnect, SendQueue: 0 (4 Bytes), CurrentSendQueue: 0 (0 Bytes), SendCache: 0 (0 Bytes)

2018/07/16 08:42:37.180 9316-9352 I/TeamViewer KeepAliveSessionOutgoing::ConnectSuccessHandler(): KeepAliveConnect to GB-MAN-ANX-R004.teamviewer.com successful

2018/07/16 08:42:37.601 9316-9357 I/TeamViewer KeepAliveSessionOutgoing::KeepAliveChannelInitialized(): KeepAliveConnection to GB-MAN-ANX-R004.teamviewer.com initialized

2018/07/16 08:42:37.601 9316-9357 E/TeamViewer KeepAliveSession::KeepAliveChannelInitialized(): KeepAlive-Connection initialized with ID XXXXXXXXX (IP: XXXXXXXXX), SendQueue 3 (3818 Bytes), SendIndex 0, AckIndex 0, RemoteSessionID 29

2018/07/16 08:42:37.601 9316-9357 W/TeamViewer KeepAliveSession::SendCompleteQueue(): SendQueue: 3 (3818 Bytes), RemoteSession 29 (ClientID XXXXXXXXX), Time: 0 ms

2018/07/16 08:42:37.813 9316-9359 I/TeamViewer SyncManagersFunction::Start: current managerlist size: 1

2018/07/16 08:42:37.814 9316-9359 I/TeamViewer TVRouterClock Schedule next request in 0 seconds

2018/07/16 08:42:37.815 9316-9359 I/TeamViewer TVRouterClock Schedule next request in 0 seconds

2018/07/16 08:42:37.818 9316-9359 I/KeepAlive Online

2018/07/16 08:42:37.821 9316-9356 I/TeamViewer Account::UpdateState: KA = 1, active = 1

2018/07/16 08:42:37.824 9316-9316 I/TeamViewer Account::SetLoginState: new state: 2

2018/07/16 08:42:37.824 9316-9316 I/TeamViewer UpdateRegistrations:pl state change

2018/07/16 08:42:37.825 9316-9316 I/TeamViewer PushNotificationRegistration::UpdateRegistrationsInternal : device token: XXXXXXXXX:XXXXXXXXX-XXXXXXXXX

2018/07/16 08:42:37.841 9316-9353 I/TeamViewer RCmdAckMap::RemoveAckHandler(): AckMapEntry not found, CmdID XXXXXXXXX, TargetID XXXXXXXXX, SenderID: XXXXXXXXX, AckResult: 1, Payload: 23 Bytes

2018/07/16 08:42:37.841 9316-9359 I/TeamViewer RCmdAckMap::RemoveAckHandler(): AckMapEntry not found, CmdID XXXXXXXXX, TargetID 31, SenderID: XXXXXXXXX, AckResult: 1, Payload: 2321 Bytes

2018/07/16 08:42:38.056 9316-9357 I/TeamViewer RCmdAckMap::RemoveAckHandler(): AckMapEntry not found, CmdID XXXXXXXXX, TargetID 14, SenderID: XXXXXXXXX, AckResult: 1, Payload: 2321 Bytes

2018/07/16 08:42:38.264 9316-9356 I/TeamViewer TVRouterClock: received router time: 20180716T114240.XXXXXXXXX

2018/07/16 08:42:38.265 9316-9356 I/TeamViewer TVRouterClock Schedule next request in 43200 seconds

2018/07/16 08:42:38.277 9316-9316 I/ActivityManager activityStarted com.teamviewer.host.ui.SettingsActivity@XXXXXXXXX

2018/07/16 08:42:38.282 9316-9316 I/ActivityManager activityResumed com.teamviewer.host.ui.SettingsActivity@XXXXXXXXX

2018/07/16 08:42:38.810 9316-9316 I/ActivityManager activityStopped com.teamviewer.host.ui.HostActivity@XXXXXXXXX

2018/07/16 08:42:38.810 9316-9316 I/ActivityManager activityStopped: isFinishing: false

2018/07/16 08:42:41.794 9316-9357 I/TeamViewer PushNotificationRegistration::UpdateRegistrationsInternal [createOrUpdateRegistrationsCb]:Push Notification registration successful

2018/07/16 08:42:42.008 9316-9359 I/TeamViewer AsyncMessaging::RegisterAtAsyncMessageProvider(): Register successful

2018/07/16 08:42:48.479 9316-9316 I/ActivityManager activityStarted com.teamviewer.host.ui.EventLogActivity@XXXXXXXXX

2018/07/16 08:42:48.481 9316-9316 I/ActivityManager activityResumed com.teamviewer.host.ui.EventLogActivity@XXXXXXXXX

2018/07/16 08:42:48.980 9316-9316 I/ActivityManager activityStopped com.teamviewer.host.ui.SettingsActivity@XXXXXXXXX

2018/07/16 08:42:48.980 9316-9316 I/ActivityManager activityStopped: isFinishing: false

2018/07/16 08:42:50.836 9316-9316 I/MailHelper Create event log mail intent.

 I can provide more logs/detailed info if needed.

[ghostlab]

Any news for this issue? I got the same issue on ubuntu 18.04.1

[mady902]

Well the round about solution is using android emulator in ubuntu 

with team-viewer installed in it. And voila there you go you can solve your 

problem till team-viewer gets a solution to it.

-- Madhavan Pallan

[realman_notcow]

Any suggestions for an android emulator?

[smfielding]

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?

[gregoryjw]

Linux 18.04 ubuntu to android-8 still not working. Same problem as described in original post.

connects, get spinner on android and "connecting" on Linux, then ready to connect on android with failure. 

I was going with teamviewer because vnc servers/clients on android/ubuntu require root access on android which is a pain even with the great work by the xdadev folks.

[Brano]

Same problem here, can connect to Android from Ubuntu TV 14.2.8352

Android sees incoming connections but then it never connects.

[csl1]

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)?

[timrsfo]

I tried for an hour trying to resolve this issue on my Ubuntu 16.04 box. I thought it was a Sumsung Add-on problem, S10

I finally switched to an old Win7 box and it worked, unfortunately that solution does not work for me. 

Linux Teamviewer V 14.2.8352 FREE

Has Teamviewer made a decision not to support Linux?

[JuanTP]

I'm suffering from the same issue

Fedora release 30 (Thirty)

teamviewer-14.6.995-0.x86_64

[AlenaC]

Hello all,
hell o@csl1 ,

thank you for your post. Welcome to the community.

Does this issue still persist? Since you wrote that you have a license, could you please send us your log files in a ticket explaining the issue, please?

Our dedicated team will have a look at it as soon as they have the information

Thank you very much

Best, Alena

[JuanTP · Accepted solution]

Official Answer from Teamviewer:
[#33096754]
Unfortunately there is no mobile device support for Linux at the moment. We can't say when we will release it, but we are planning to do so.

If you have any further questions, please do not hesitate to contact us again.

Best regards

Dennis Antelmann
Support Engineer
-----------------------
TeamViewer GmbH * Jahnstr. 30 * 73037 Göppingen * Deutschland
Handelsregister: Ulm HRB 534075
Geschäftsführer: Oliver Steil, Stefan Gaiser

[simpz]

Since you say you have no Mobile device support on Linux at the moment do you still need log files ? As you seem to be aware this doesn't work and have already reproduced this.

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!

[AlenaC]

Hi @simpz ,

thanks for your post. 

No, we do not need the log files anymore. I made a mistake, sorry.
That is why JuanTP´s answer is marked as Solution.

As soon as we release this feature, we will inform you.

Best, 
Alena 

[iamit]

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.

[onex]

What are we paying for?

There is no Linux support for Android devices.
There is no working QuickSupport for Linux anymore.
Connecting to old Windows client versions from Linux fails (black screen)

A lot of non working stuff for a subscription product like this :(