yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] MrDenisse:
Good afternoon!!

I have been using a Toyota Auris with Touch 2 since August 2016 that uses Drive Link as an app for mirrorlink and since then I have made great progress on the subject.

I have tested all the compatible phones with this version that are Samsung Galaxy S3, S3 4G, Note 2 and S4. All these mobiles are compatible whenever you put a rom 4.3.

In the Samsung Galaxy S3 I have achieved a perfect balance of power consumption and driving thanks to the rom Android Revolution HD 53 and the kernel PSN_AGNi_pureSTOCK-v3.9.2_I9300_4.3.0_AROMA.

This kernel has implemented the option of being able to charge at 1000mah while using drivelink, which will always charge more battery than it consumes while we drive. We could say that the Samsung Galaxy S3 with this rom is a perfect system except that it only has 1GB of RAM and that makes it very slow when you press the touch screen of the car.

With the Samsung Galaxy S4 Touch 2 and Drivelink are much better, much more fluid than with S3 but the only problem I encounter is that I can’t get any kernel that when connecting the terminal to the car loads more than 460mah and turn drivelink . If I have tried kernels in which you can implement the fastcharge and enable it to load at 1000mah but drivelink does not work.

In short, I can’t run Drivelink and charge at 1000mah at the same time on Galaxy S4, if I got this the phone would be perfect for use with drivelink.

I have to say that I am not a developer, I simply change roms and kernels and touch up these with apks, I will not make a rom from the beginning so if someone is willing to help me get this I will be eternally grateful.

First of all sorry for my English level but I use the google translator to translate from Spanish (if any Spanish developer can help me it would be even easier to understand)

Thanks in advance and if I can help someone in something related to this subject, here I am.

Greetings.
[Galaxy S III Android Development] pavez1982:
Drive Link Samsung Restrictions
[Galaxy S III Android Development] s.rahus:
The drive link app is crashing on my OnePlus 3 with Paranoid Android ROM (android v 7.1.2). Will this hack only work with Samsung devices? I am ready to test this if this is still in development.
[Galaxy S III Android Development] newbie_vlc:
I think only few models are mod compatible

Enviado desde mi ONE A2003 mediante Tapatalk
[Galaxy S III Android Development] drxx:
Hi ;

My car is Toyota C-HR inside Touch 2 ;

Buy a new telephone Samsung Galaxy S3 ; Custom rom instal and bootlooader install . Drivelink install and perfect ;

But I have a problem ? Navigation

I use navigation google maps sygic gsp signal lost very offten :(

What can I do ? Thanks
[Galaxy S III Android Development] A$$A$$!N:
Full Mirror for MirrorLink

If you want to use all your favorite app in the car through MirrorLink, then the app "Full Mirror for MirrorLink" makes it possible:

play.google.com/store/apps/details?id=net.sb_software.fullmirror
[Galaxy S III Android Development] 900913.jj:
Car screen Touch not working

Hello, may I ask for help.

I have a Samsung S3 device.

I rooted it, installed the included files within this post (TMServer and Drive Link.Apk).

I was able to mirror the whole android system, but the touch screen functionality (within the car’s touch screen) works only within the Drive Link app.

May I get help how to active the touch screen in the whole of the android system.
[Galaxy S III Android Development] cell128:
Its because jellybean has the proper framework with the tmserver installed which is required for drivelink to run
[Galaxy S III Android Development] wildpig8:
I have a 701BT, and S3 running Resurrection Remix JB v3.1.1

But sadly can't connect.......:crying:

Used to be running CriskeloRomV18, and it is able to connect....

Can help take a look?

Thanks!
[Galaxy S III Android Development] j0ep0:
MirrorLink (TMServer) doesn't work on AOSP/AOKP based ROMs. For now, you really need a Samsung Touchwiz based ROM. See the other thread for testing requests, maybe you can try. Check out this post: http://xdaforums.com/showpost.php?p=33695486&postcount=321 and let me know if that version works or not. Logcats are welcome.
[Galaxy S III Android Development] shirazdindar:
summary of where we're at, at this point

super appreciate your work, j0e0p. it feels like slow but definite headway. i'd like to do a sum-up of our progress. please correct me where i'm wrong or fill in relevant details.

1. unlocking mirrorlink's app restrictions -- this is already achieved. there are some bugs but these are mostly worked out? peeps please confirm, referring to point #1 in your response.

2. using mirrorlink in other ROMS than samsung's jellybean -- this is a matter of ripping out the TM server framework from the samsung ROM and putting it into other ROMs, but is hardly trivial due to TMserver inclusions and variances per ROM. je0e0p has done this for CM10 (for the S3) and it seems mostly successful at this point? someone please confirm actual usage, referring to point #2 in your response.

3. using other devices than the S3. Aside from considerations in #2, devices are identified and authenticated via a key-code system for which the source code has not been released on either Sony's side (confirmed) or Samsung's. J0e0p has identified some of the components involved but not much beyond that. Has anyone looked to see if Nokia has happened to release the source code for their deck? Perhaps they've (inadvertently) released their key code. It's my limited impression that there's more to glean here from the deck code than the mirrorlink code. Anyhow, overall I'd say this is where the least progress has been made. Has anyone managed to get Mirrorlink to connect and work with their Sony deck from a phone other than an S3? If so please state model number, and which Mirrorlink you used (official or which release from j0e0p), referring to point #3 in your response.
[Galaxy S III Android Development] mrjoshzombie:
1. From my limited testing on a working rom, you cannot access your home screen with a stock launcher, but you can switch back to already open apps/windows. Everyone seems to have different reports on this given the launcher used and apps being closed.

2. Doesn't work at all in CM10 yet (well, DriveLink opens, but no mirroring). It's getting there, but I have not yet successfully managed a connection. I sent je0e0p my logcat this morning.
[Galaxy S III Android Development] j0ep0:
First of all, I really should should get a nick change :) Second, check this post for new test versions: http://xdaforums.com/showpost.php?p=33733620&postcount=326

To get a bit more into detail in reply to shirazdindar;

1. The DriveLink app has several restrictions, the only one I've removed is the contious resurfacing of the app. With the normal version, as soon as you start another app, Drive Link puts itself to the foreground. That behaviour is removed, but several other restrictions are still there. As there's a workaround for the most annoying one (Home button not working), I'm not spending too much attention to this for now.

2. DriveLink is working on CM10 without adjustments, but TMServerApp.apk not. This app delivers the mirrorlink interface with the head unit. In "the other thread" you can download some test versions. Specifically named test version, because I cannot verify if they're working. I don't have a MirrorLink head unit and not planning to buy one in the near future. The "development" and testing procedure are basically trial and error so I have to rely on Sony/Alpine owners to test and provide useful feedback. If we get TMServer running on CM10 for the S3, testing must be done with other devices. Some devices might work, some won't.

3. Will be relevant as soon as 2 is solved. I think we shouldn't elaborate too much on this at the moment. In the testing process for CM10 we will run into this key-pairing and then we'll see if it can be bypassed or not. Nokia devices aren't really interesting from my point of view, however progress may take a leap when Xperia devices or firmware with MirrorLink support will be released.
[Galaxy S III Android Development] TheRandom1:
Any plans on bring this to the Galaxy Nexus by chance? (sorry to threadjack!)
[Galaxy S III Android Development] j0ep0:
Apologies not needed, why dont you try it to see it if works? Please flash this file (on cm10 offcourse) and report back: http://www.mediafire.com/download.php?is611vkxabwpzxy

Please test and report back:

- The device you're using

- CM10 build

- TMServer app behaviour (running, FC'ing or other)

- Logcat (check this thread)
[Galaxy S III Android Development] Killa200:
Clean or dirty flashing? What does the phone say when you connect to the head unit (connected as installer, connected as media device)? I'm running the same ROM with my S3, and no such luck on a Sony XAV-701HD. Head unit just sits there at reconnect.
[Galaxy S III Android Development] mrjoshzombie:
Clean flash from CM10, full wipe, didn't modify anything (I didn't even sync my Google account). Just loaded the rom up, installed the Drivelink APK from the first post, and everything worked as it should.

Great news, by the way: http://xdaforums.com/showpost.php?p=33740641&postcount=328

DriveLink is now working on CM10! Only the audio isn't playing through the headunit. Everyone give it a try!
[Galaxy S III Android Development] carrd:
Does anyojne know of a single din stereo that supports mirrorlink?
[Galaxy S III Android Development] mrjoshzombie:
I highly doubt you'll find one. The screen would be MUCH too tiny for something like that.
[Galaxy S III Android Development] Killa200:
Interesting issue on my side. Just clean flashed to the latest CM10 Nightly ( cm-10-20121106-NIGHTLY-d2vzw.zip) and can't get the drivelink app from this thread to install. I've got unknown sources enables, and it attempts to install the app, then fails with "X App Not Installed".
[Galaxy S III Android Development] j0ep0:
Uninstall the original drivelink app first before installing the modified one.
[Galaxy S III Android Development] mrjoshzombie:
I just flashed to that nightly and DriveLink still opens no problem. Not sure about installing it though.

Fun note, anytime you flash a new nightly, you need to reflash the TMserver app.
[Galaxy S III Android Development] Killa200:
I had reflashed the tm server, and hadn't installed the apk yet as this was a clean install. Finally got the apk to load after going into CWM and doing a fix permissions. No luck with it working though, head unit still sits at re-establish connection.

- Samsung Galaxy SIII SCH-I535

- cm-10-20121106-NIGHTLY

- No errors on TMServer appearing in GUI

- Logfile: http://www.mediafire.com/?c2gerwdbfqdyt5h
[Galaxy S III Android Development] spscoral:
Sorry if I'm a bit slow, but just so I'm straight, the work in this thread only gets Drive Link and TMServer working in JB Touchwiz ROMs and CM10 ROMs, right? So stock ICS Touchwiz ROMs are not supported?
[Galaxy S III Android Development] mrjoshzombie:
From what I'm hearing. ATT and Sprint phones work out of the box with DriveLink. VZW is what has been limited, and development only works with two roms I've seen thus far. Fully with JellyWiz and CM10 lacks audio.

It doesn't seem many people are testing though.

---------- Post added at 03:27 PM ---------- Previous post was at 03:25 PM ----------

Try flashing a TMServer from this post: http://xdaforums.com/showpost.php?p=33733620&postcount=326

The DriveLink APK in this thread, and TMserver from that post is how I've managed to get CM10 and Drivelink working.
[Galaxy S III Android Development] spscoral:
Thanks. I'll try this and assuming it doesn't work, maybe I'll try JellyWiz. Been waiting for VZW to get on board with the JB update, but who knows how long that will take!
[Galaxy S III Android Development] mrjoshzombie:
Just so you know, CM10 audio is not working, JellyWiz, with my 10 minutes of testing, works fully.
[Galaxy S III Android Development] Killa200:
That was the TMServer that I flashed after installing CM10 this time around, but I tried flashing it again with no success. Still getting the re-establish connection on the head unit.
[Galaxy S III Android Development] j0ep0:
Strange stuff going on on your phone.. however, you might want to check permissions on /sys/class/android_usb/android0/terminal_version (rw-r--r--) and check that USB is set to MTP. Is USB Tethering working with your phone and the USB cable you're using to connect to the nav unit?
[Galaxy S III Android Development] Killa200:
Permissions on that file were off (they were 640, and not 644 like you listed). Changed them. Tested USB tether to the desktop using the same cable as in the car, and it is working. Also been in MTP mode the entire time. Still a no go on talking to the head unit.

Chown was also off on that file you listed. It was set as System:System, even though everything else in the folder was root:root. Didn't change it, as I wasn't sure who should own it.
[Galaxy S III Android Development] j0ep0:
When USB is connected at my phone, permissions on the file change to rw-rw----... Also happens at yours? If not, try set them manually. This is just rough guessing, from a distance it looks like somethings goes wrong installing the leaked JB. Else wait for a real JB release or see what the results are for other i535 users. Sa far we have 1 working and 1 not working, that's a pretty small sample ;)
[Galaxy S III Android Development] Killa200:
After connecting my phone via usb, permissions on the file change to rw-rw----. However they do not return when disconnecting my phone from USB, they just stay at rw-rw----. Out of curiosity I forced USB tethering on while connected to the headunit before trying drivelink to see if the head unit would connect to the phone and try to initialize vnc, but that was a no go as well. Things to note was that while tether was enabled on the phone, that you couldn't back out of drivelink. You had to shut off usb tether first, then the option to exit while backing out worked again.
[Galaxy S III Android Development] laxity:
New version of Drive Link released - 1.1.021 (12-Nov-2012).

http://www.samsungapps.com/venus/topApps/topAppsDetail.as?productId=000000469052

Interesting. Looks like the new version lets you set any installed app as the default navigation app. Can anyone with TomTom confirm if it works or not please?

Update : Looks like you can create shortcuts to various applications on your phone. Just about to try it with my headunit now...

Update 2 : Crap. Ok looks like the default navigation app and shortcuts get overridden when you hook it up via mirrorlink to a head unit :(

Update 3: Link to new Drive Link apk - https://www.dropbox.com/s/66jls0b7yxghusf/app.scm-2.apk
[Galaxy S III Android Development] cell128:
Do you mind sharing the apk? I still can't download it from the USA store
[Galaxy S III Android Development] laxity:
Here you go :

https://www.dropbox.com/s/66jls0b7yxghusf/app.scm-2.apk
[Galaxy S III Android Development] prerunnerseth:
So I bought my mom a used SGS3. I will be using it next week til she comes to visit. This is a verizon phone now rooted, unlocked and running jellywiz. I can connect just fine with mirror link though it is pretty slow :(. The Only issue at this point is that the drivelink app keeps my screen from timing out and not just with it plugged in. It stays on indefinitely. I uninstalled the drivelink app and sure enough my phone screen now times out.
[Galaxy S III Android Development] laxity:
Workaround I have found (not exactly ideal), is to go into settings > Application Manager > Drive Link -> Force Stop.

This lets the screen time out again but still lets Drive Link work. I think you still have to force stop again if you start Drive Link again, I can't remember.
[Galaxy S III Android Development] prerunnerseth:
Too much work for me. Hopefully j0ep0 can maybe solve this issue for us. Would make the thing actually useful. I dont plan to use it all the time. My main use is when i need to navigate. I don't like that the HU wont allow me to listen to XM while using stuff in the mirrorlink. I dont listen to music through my phone so it doesnt help me much in that sense. Would really like to have the mirrorlink screen up with the XM running in the background, but thats a Sony issue. Hopefully we see some more progress in this field with next years HU models.

j0ep0 let me know if you have anything you want me to test with the drivelink app. I can pretty much run down to my truck at any time to test things out.
[Galaxy S III Android Development] laxity:
Not sure what XM is exactly but I'm asuming its the audio playback on the Sony HU? On my Alpine head unit I am unable to play my music from the head unit either when Mirror Link is running. With the Nokia Drive this is possible on the Alpine unit. I have spoken to Alpine support and they say that they would need support on the Drive Link side for this to work. It is one of the things that I have support tickets open with Alpine and Samsung for.
[Galaxy S III Android Development] TheRandom1:
I imagine he means XM radio.
[Galaxy S III Android Development] spscoral:
Seriously? That's completely retarded! This makes me want to get rid of the Sony and get something without Mirrorlink if I can't even view navigation on the screen via Mirrorlink while listening to XM. The firmware for these units is half baked at best! It's bad enough that the artist and title use approximately 10% of the screen real estate and you have to hit the escape button on XM to get to the preset buttons...
[Galaxy S III Android Development] Killa200:
Found out my issues (turned out to be a usb module in the car causing the phone not to enter tether mode). Reporting that this is now working with two sets of roms i've tried.

Carrier: Verizon

Phone Model: SCH-I535 (Verizon S3)

Any Bugs: Home button on phone is not going to home screen, getting around this by double clicking the home button and launching s-voice, then launching apps by voice.

Rom/Kernel JellyWiz RLS13 (VRBLJ1 base)

Carrier: Verizon

Phone Model: SCH-I535 (Verizon S3)

Any Bugs: Typical reported, no usb audio and landscape viewing issues.

Rom/Kernel: cm-10-20121114
[Galaxy S III Android Development] haynjoker68:
drivelink

I just purchased AT&T Samsung galaxy s3 just for the reason of the drivelink. It installed with no problems. Tried it out on a Sony XAV-701HD. It works as I think it was intended to do. The only thing I noticed is that if I turn off car while watching netflix it locks up phone. Other than that if just using it as Drivelink and not cheating around with the taskmanager it works fine. Wish that it could just be a full mirror of my phone, guess I have to learn how to root this thing so I can get that feature. It may take me awhile since I was a long time HTC fan.

Thanks for the thread and great work
[Galaxy S III Android Development] Killa200:
Carrier: Verizon

Phone Model: SCH-I535 (Verizon S3)

Any Bugs: Typical reported, no usb audio and landscape viewing issues.

Rom/Kernel: cm-10-20121116

Carrier: Verizon

Phone Model: SCH-I535 (Verizon S3)

Any Bugs: Typical reported, no usb audio and landscape viewing issues.

Rom/Kernel: cm-10.0.0 stable
[Galaxy S III Android Development] laxity:
Finally got around to testing this. It works but I can't get it to return to the home screen using the home button method. If I hold down the home button I can get the task manager but if I select and application it jumps me back into Drive Link again and disconnects me from my Alpine head unit and the head unit displays "No application". To get it connecting again I have to power the head unit on and off otherwise mirrorlink never connects again.

Carrier: O2 UK

Phone: i9300 International UK Stock Jelly Bean 4.1.1 (I9300XXDLID)

Bugs: Starts up ok but unable to bring up any non-standard apps or get to home screen without disconnection or jumping back into Drive Link.

Thanks for the work so far.

Cheers,

Richard.
[Galaxy S III Android Development] djwilliams100:
Hi Richard. Make sure your using a downloaded launcher like Nova, Apex or Go Launcher. I'm on same 4.11 as you and mine works fine using Nova launcher and Go launcher.

Dan
[Galaxy S III Android Development] denny_1986:
hi guys,

has anyone looked at the pioneer's appradio receiver and compared it with the sony's?

there is an "aftermarket" app on google play called ARliberator which basically mirrors your phone on the receiver. Pioneer has an app call appradio on google play but that comes with limitations just like drivelink. It would be nice to have an ARliberator type app for the sony...

have a look

http://appradioforums.com/index.php
[Galaxy S III Android Development] laxity:
Thanks Dan. Unfortunately I prefer some of the widgets on the stock launcher which the other launchers don't let you use for some reason.
[Galaxy S III Android Development] bherrin2:
Quick Question...

I have a toro (verizon galaxy nexus) running CM10-nightly 11/24/2012. I do not see tmserverapp, twframwork.jar, nor twframework-res in the CM10 file system. I am about to purchase an XAV-601BT and would like to see if i can get mirrorlink working.

Should I install both packages from the first post (TMserver12.zip and app.scm-1-j0ep0-v1.0.apk) or should i install another set of packages for testing?
[Galaxy S III Android Development] j0ep0:
Small chance that it will work. Use this file: http://www.mediafire.com/download.php?2avvdq19o8c6in1 for TMServer and the Touchwhiz framework, then install the DriveLink APK (app.scm-1-j0ep0-v1.0.apk).
[Galaxy S III Android Development] bherrin2:
OK, I found a local best buy before i saw this post and installed the frameworkzip and app from post 1. Got the unrecognized usb error, then when i launched mirrorlink on the head unit i got a phone communication error.

I removed drivelink, flashed this zip and on reboot got an "upgrading android" message and it updated 21 files. Reinstalled Drivelink. I will stop in best buy tomorrow and try again. I may also bring the sony update wtih me on a usb drive.
[Galaxy S III Android Development] laxity:
New version of Drive Link released - 1.1.024 (28-Nov-2012).

http://www.samsungapps.com/venus/topApps/topAppsDetail.as?productId=000000469052

Link to new Drive Link apk for those without access to Samsung App store - https://www.dropbox.com/s/66jls0b7yxghusf/app.scm-2.apk
[Galaxy S III Android Development] cell128:
Is there any changes to the new one?
[Galaxy S III Android Development] laxity:
Well the screen time-out issue appears to have finally been fixed (took them long enough!) but thats about all I have noticed.
[Galaxy S III Android Development] Mx_Passi:
I am not up to date, but in this version I can set every app I have installed as shortcut. I cannot test ist with the Headunit because I have none.

Can somebody try it?
[Galaxy S III Android Development] prerunnerseth:
Got my Verizon note 2 yesterday. Works even better than the SGS3 did. Home button doesn't work though. Installing the new version posted a couple posts up. Will report back on that one.
[Galaxy S III Android Development] laxity:
Unfortunately in the official app any unsupported shortcuts are ghosted out / hidden deliberately as soon as Drive Link is connected to a Head unit. Stupid I know. I've sent feedback via Samsung app support line about all the issues and limitations of Drive Link. I would recommend doing the same so that Samsung know that there are other people who want improvements.
[Galaxy S III Android Development] Vangelius:
hello. I have GS3 Sprint L710, set Stock firmware 4.1.1. I want to use S3 with Sony 601 mirrorlink (now I have a negative result). Move to CM 10 do not want ... Please help me who has successful result?!
[Galaxy S III Android Development] laxity:
Not seen any app updates in this thread for a while. Just wondering if development is still continuing or if it has been abandoned? Would love to see the latest version of Drive Link modified and of course the features mentioned on the main page added. I am still hoping to have TomTom mirrored onto my headunit and have the phone screen off when in use. :)

Thanks for the hard work so far.