Teamviewer QuickSupport now supports AOSP-based rooted ROMs (even non-Samsung!)

Search This thread

hmmwhatsthisdo

Senior Member
Jul 11, 2011
90
23
So, if you have used TeamViewer (remote control app, cross-platform and very versatile) you've probably seen the QuickSupport app talked about every so often. QuickSupport is essentially a TeamViewer server for Android devices, allowing other Teamviewer installations to remotely control it. With its effortless setup and automatic network transversal, it's possibly one of the best remote-control server applications for Android.

But, there was a catch. It only supported Samsung-signed ROMs. This meant that A) it was only working natively on stock ROMs and B) it was only going to work on Samsung devices. Drat.

But, yesterday, there was an update to the app. It didn't give much in the manner of update notes. However, once I launched it on my device running CM10, it started without any errors for the first time. After confirming on an HTC device running AOKP, it would appear that all AOSP ROMs are now supported without any issue in TeamViewer QuickSupport. It asks for root, presumably in order to facilitate the remote-control parts of the app. (Note that it will NOT work if root access is not given)

TL;DR: TeamViewer QuickSupport now probably works on all AOSP-based rooted ROMs AND now asks for root privileges.

I think this is something big. I've never heard of a company as large and... "professional" as TeamViewer using, for lack of a better word, a community-made "hacking" system for gaining privileged access.

Here's the link to TV QuickSupport on the Play Store. Try it out, and post your results here!
(GPlay not letting you download it? Get the APK straight from Teamviewer here.)

So far, here's a list of devices that have successfully ran TVQS:
  • d2att, AOKP
  • Skyrocket, CM10
  • Nexus 4 - this seems to be sort of iffy. More information is needed to figure out if this works or not.
  • Nexus One, Unofficial CM10

Did your device run TV properly? Let me know, and I'll put it on the list for others to see. Be sure to include the following:
  • Your device's model/board name
  • What codebase your ROM uses (AOSP, Sense, TW, etc.)
  • Whether or not you were able to download directly from the Play Store
  • Whether or not the APK installed and ran
  • Whether or not you were able to use the app

Did this make your day? Click the "Thanks" button!
Help this get more exposure! Click "Tip us?" in the top-right corner of this post!
 
Last edited:

Dave the Knave

Senior Member
Apr 18, 2008
1,653
353
Baltimore
If you don't grant it root access, it won't work. At least that's my story. I just tried it on my Galaxy S3 (i747) running AOKP, and with root access granted it works fine, without it, it didn't mirror my screen on my computer. I wish you didn't need to give it root. Not very happy about that.
 

hmmwhatsthisdo

Senior Member
Jul 11, 2011
90
23
If you don't grant it root access, it won't work. At least that's my story. I just tried it on my Galaxy S3 (i747) running AOKP, and with root access granted it works fine, without it, it didn't mirror my screen on my computer. I wish you didn't need to give it root. Not very happy about that.

My guess is that it requires low-level access in order to emulate screen events (sendevent/getevent, anyone?). I think the only reason it didn't require root on Samsung ROMs was because it had a backdoor it could access. I'd be more worried about this, really.

But still, Teamviewer is safe-to-use - you can't access the phone unless the app is running (and in the foreground) and confirmation must be given on the phone's end. I doubt anyone will use it as an attack vector.
 

Dave the Knave

Senior Member
Apr 18, 2008
1,653
353
Baltimore
My guess is that it requires low-level access in order to emulate screen events (sendevent/getevent, anyone?). I think the only reason it didn't require root on Samsung ROMs was because it had a backdoor it could access. I'd be more worried about this, really.

But still, Teamviewer is safe-to-use - you can't access the phone unless the app is running (and in the foreground) and confirmation must be given on the phone's end. I doubt anyone will use it as an attack vector.

I don't doubt it's safety at all. I use TV a lot to do things away from home and as a VPN. I just wish it wasn't necessary on AOSP roms.
 

ZeRoWaR

Senior Member
Jan 16, 2011
94
26
Jena
Can someone provide the apk?
It's not available for me to download on my HTC One X running CM 10.1, however my TF-101 could download it.
 
Aug 10, 2010
20
0
24-04 - 02:44:34:561 TV_RsaKey error: readFromFile open /data/data/com.teamviewer.quicksupport.market.samsung/files/PK: open failed: ENOENT (No such file or directory)
24-04 - 02:44:34:562 TV_RsaKey error: readFromFile open /data/data/com.teamviewer.quicksupport.market.samsung/files/SK: open failed: ENOENT (No such file or directory)

I get this on my Nexus 4, I guess it only works on Samsung devices, the only new thing here is that they added support for AOSP roms. I got excited too soon I guess.
 

hmmwhatsthisdo

Senior Member
Jul 11, 2011
90
23
I get this on my Nexus 4, I guess it only works on Samsung devices, the only new thing here is that they added support for AOSP roms. I got excited too soon I guess.

works fine on my rooted N4. tested via wifi and 3g - no issues here

(downloaded from http://download.teamviewer.com/download/TeamViewerQS_Samsung.apk)

What ROMs/kernels are you two running?

berserkwarwolf, did you grant TVQS root access?
 
Last edited:
X

xemino

Guest
works just fine on my N4, stock rom, franco stable kernel.
will test it today on my grandma's stock galaxy nexus, i was waiting for this a long time.
 

parkedraccoon

Senior Member
Sep 23, 2012
154
303
Works on my old Nexus One running VJ's CM10.

And my Nexus 4, flawlessly. I'm running CM10.1 M2 with ziddey's OTG kernel.
 

[deXter]

Senior Member
Aug 23, 2008
510
171
Works great on my Nexus 4.

- Was unable to install from the Play Store, had to install APK manually
- ROM: Paranoid Android 3+
- Kernel: Air Kernel R6

Thanks again, hmmwhatsthisdo! :)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 17
    So, if you have used TeamViewer (remote control app, cross-platform and very versatile) you've probably seen the QuickSupport app talked about every so often. QuickSupport is essentially a TeamViewer server for Android devices, allowing other Teamviewer installations to remotely control it. With its effortless setup and automatic network transversal, it's possibly one of the best remote-control server applications for Android.

    But, there was a catch. It only supported Samsung-signed ROMs. This meant that A) it was only working natively on stock ROMs and B) it was only going to work on Samsung devices. Drat.

    But, yesterday, there was an update to the app. It didn't give much in the manner of update notes. However, once I launched it on my device running CM10, it started without any errors for the first time. After confirming on an HTC device running AOKP, it would appear that all AOSP ROMs are now supported without any issue in TeamViewer QuickSupport. It asks for root, presumably in order to facilitate the remote-control parts of the app. (Note that it will NOT work if root access is not given)

    TL;DR: TeamViewer QuickSupport now probably works on all AOSP-based rooted ROMs AND now asks for root privileges.

    I think this is something big. I've never heard of a company as large and... "professional" as TeamViewer using, for lack of a better word, a community-made "hacking" system for gaining privileged access.

    Here's the link to TV QuickSupport on the Play Store. Try it out, and post your results here!
    (GPlay not letting you download it? Get the APK straight from Teamviewer here.)

    So far, here's a list of devices that have successfully ran TVQS:
    • d2att, AOKP
    • Skyrocket, CM10
    • Nexus 4 - this seems to be sort of iffy. More information is needed to figure out if this works or not.
    • Nexus One, Unofficial CM10

    Did your device run TV properly? Let me know, and I'll put it on the list for others to see. Be sure to include the following:
    • Your device's model/board name
    • What codebase your ROM uses (AOSP, Sense, TW, etc.)
    • Whether or not you were able to download directly from the Play Store
    • Whether or not the APK installed and ran
    • Whether or not you were able to use the app

    Did this make your day? Click the "Thanks" button!
    Help this get more exposure! Click "Tip us?" in the top-right corner of this post!
    5
    Hi I am trying to install QS Support on my CM12 based table. But it keeps telling me that the QS Support app can't be installed.
    In logcat I see
    "com.android.server.pm.PackageManagerException: Cannot install platform packages to user storage!"
    did somebody had success?

    EDIT: Managed to get it working!
    When I start the QS App and I try to remote control my tablet using Team Viewer it ask me to download an add on apk. lnstalling that apk fails with the above message
    I copy the app under /system/app and set permissions to 644 and reboot the phone.
    After that Team Viewer works without a problem :D
    1
    This needs more attention. Thanks OP!
    1
    Can someone provide the apk?
    It's not available for me to download on my HTC One X running CM 10.1, however my TF-101 could download it.

    Done.
    1
    It has worked for me on a Nexus 5 at the end of March.
    But now it has stopped working.

    I updated the Teamviewer 9 application on the PC in the meantime, but even a rollback to an old version does not bring back remote control. :(

    Not sure if still needed but I wanted to post somewhere so the information was captured.

    On CM11, Nexus 5 the AOSP QS add-on would download for me but not install. I checked out logcat and saw something like this:

    ActivityManager: No content provider for permission revoke: file:///path/to/aosp-qs-addon.apk

    Since this can happen when an apk is not signed, I verified this ($ jarsigner -verify -verbose -certs my_app.apk) then signed and zipaligned it using the instructions at the bottom of this page under "Signing your app manually": http://developer.android.com/tools/publishing/app-signing.html

    Once I did that the add-on installed and remote control works flawlessly.