yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
The USB cable shouldn't matter, any will do. I guess the guy at Best Buy had an AT&T SGS3 which works good with the unit...
[Galaxy S III Q&A, Help & Troubleshooting] prerunnerseth:
Darn, So it is carrier dependent? Fn Verizon... no Google Wallet, this doesn't work. Im getting fed up. will a custom rom solve this issue?

Adding $20 to the bounty for anyone who can get this working on stock rom Verizon SGS3 rooted or not.
[Galaxy S III Q&A, Help & Troubleshooting] murso74:
what if anything would i have to do with my Note to test?
[Galaxy S III Q&A, Help & Troubleshooting] Olywa123:
Seems you are also a night-owl! :) No problem with trial and error happy to test and test until we get there.

Unfortunately it still didn't work but I'm not sure I did it correctly, maybe there was a problem with the files... as it was a zip and you used the word flash I first assumed it was a CWM flashable Zip but that way I just get an error that the flash is aborted. So I tried renaming the zip to .apk but that doesn't install either ("There is a problem parsing the package"). Lastly I tried digging into the zip and extracting the "TMServerApp.apk" file and copying it over to /system/app/ replacing my existing file (maybe this is the way you intended - sorry if I'm being slow :)) Just popped out and tried it in the car but I couldn't even get a connection this time - getting "please reestablish your smartphone connection" on the headunit.

Thanks again though.

For these guys with compatibility issues - do you think it's possible that spoofing the phone as an S3 by editing the build.prop could work for them - I know that's the method the Play store uses to identify the phone for app compatibility - I wonder if this could be the same way the headunit detects the device?
[Galaxy S III Q&A, Help & Troubleshooting] prerunnerseth:
I might just return the phone. Im still in my return period. specifically bought this phone for this reason. Might just wait a little and get a Note 2.
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
The files are CWM flashables, but got corrupted. New versions:

Original: http://www.mediafire.com/?h62u6n3da5gvoy3

Modified: http://www.mediafire.com/?xo1flv3qj7g5qg3
[Galaxy S III Q&A, Help & Troubleshooting] walkeryan:
Jeez I go out of town for the week on business and someone figures it out. lol. Oh well, Nice work so far.
[Galaxy S III Q&A, Help & Troubleshooting] Olywa123:
Sorry j0ep0 - still no luck with this one, it seems to flash fine with CWM and I can see the 'TMServerApp.apk' in system/app/ afterwards but it's like the Android OS doesn't see it there. I tried flashing many times (from CWM app and from recovery mode) and even tried extracting it and manually placing it in system/app/ and several reboots but it just won't be seen (it doesn't show up as a running app/service and is not even listed in Titanium backup). I still tried connecting to the headunit on the off chance but no connection (i.e. I just get 'resstablish your smartphone connection').

---------- Post added at 03:32 PM ---------- Previous post was at 03:31 PM ----------

Indeed walkeryan - you missed the party :) have a play and let us know how you get on, j0ep0 has done some great stuff.
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
I'm pretty sure I've found the reason why the home button doesn't work when connected to the unit. A little background; since Android 4.0 it's almost impossible to override the Home button commands. Only way it to pretend the app is a launcher, but this should raise a pop-up when starting the app aking if it should be set as default action. To be sure that Drive Link wasn't the problem I've tried removing all kinds of onkey, buttonpressed events and methods, but nothing seemed to work.

So I dug into TMServerapp.apk and by checking almost all of the files I found the reason and it is darn simple. TMServerapp.apk puts the SGS3 in Car mode. When in Car mode, the home button is disabled! So, there are two options, disable the carmode in tmserverapp.apk or long-press the home button. Tha last option isn't the best but it works without further consequences. For the first option, I made a proof of concept. Start Drive Link, Plug in, TMServerapp.apk is started and keeps running (twice actually). Download the CWM flashable zip here: http://www.mediafire.com/?4yyfdhpp738efk6.

As fasr as I can find in a short period of time, enabling car mode sends the audio output over speaker/bluetooth, enables S-voice and probably some more. Question is, what is better? Long press home button or disable car mode. If anyone prefers disabling car mode I can try to tidy it up.
[Galaxy S III Q&A, Help & Troubleshooting] djwilliams100:
My car is currently the garage getting repairs. As soon i get it back (this weekend) i will experiment and see which works best. Thanks for your hard work so far!
[Galaxy S III Q&A, Help & Troubleshooting] murso74:
an upside to that may be that the screen will time out on the phone now...
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
Yep, that could be, but could be not as well. Besides car more in tmserverapp, Drive Link itself prevents the phone getting locked,so maybe that has some influence as well.
[Galaxy S III Q&A, Help & Troubleshooting] Olywa123:
Thanks j0ep0 - ufortunately I had the same problems as before with this new zip - CWM says it flashed and installed correctly and I can see the 'TMServerApp.apk' is in system/app/ afterwards but it's like the Android OS doesn't see it there and so I am unable to connect to the headunit ('resstablish your smartphone connection'). Not sure why it won't work.

Regarding your other points - a couple of thoughts, a long press of the home button should work but it's worth mentioning that the headunits own screen doesn't appear to respond to anything but single presses (no long press/gestures/multi-touch) I know this becasue a long press of the home button on the headunit dispaly will not bring up 'recents' and also because as a work around to get to the launcher home screen I'm using the GMD Gesture Control app - I've set a gesture for 'home' and this does take me to the Nova homescreen but it can only be done from the phone screen no matter what I've tried (2-finger swipe/pinch/triple tap, long press, etc.).

On the car mode thing - assuming this is the same as 'driving mode' for which there is a toggle in the notificaion toggles bar. I reverted to my working set up and once connect to the headunit I toggled off the 'driving mode' this seemed to have no negative impact and all audio/mic from the phone was still routed to the car speakers/mic with it off and could still access s-voice, etc. so maybe this is the way to go to make the home button work or maybe it's possible that the toggle is not really having an affect once already connected.

---------- Post added at 02:26 PM ---------- Previous post was at 02:06 PM ----------

Another idea (and maybe this is a longshot) but if the warning screens when starting drivelink could be removed or automaically accepted (i.e the code could be editied so it no longer waits for inputs for the 'agree', 'agree', 'discard' presses before you get to the Drivelink homescreen - then maybe 'tasker' could be used to get to the Nova homescreen. For example we could create a a task that when opened it starts drivelink waits for a couple of seconds and goes to the launcher homescreen without the need for any input by the user - this could work in theory but again would be slightly clumsy I guess.
[Galaxy S III Q&A, Help & Troubleshooting] walkeryan:
OK some discoveries so far with j0ep0's version. Due to me being on sprint the phone thinks its in a USB tether mode and thus disables data all together (Did this on stock, not j0ep0's fault). I'll see if Drivelink is throwing this flag or if its the phone's framework detecting it (Most likely the framework). If you have Sprint or possibly Verizon and are able to use data while connected with Drivelink please PM me.

The home button is probably going to need to stick with the car mode I think, because if not I'm betting the audio wont get routed. Another possibility could be to change the behavior of the back button to just allow the app to run in the background instead of closing it. Not sure if this is possible but worth a try.

I should be able to remove the warning prompts without to much of a hassle.

j0ep0 would you be willing to work on this together? Get maybe a github setup? I would hate to step on your toes.

Thank you for the donation Olywa123.
[Galaxy S III Q&A, Help & Troubleshooting] lodger:
walkeryan,,,

even my phone international on orange UK, thinks it USB Tether mode
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
Strange, I was able to reproduce your issue woth previous versions and saw that TMServerapp.apk wasn't started as well on my phone. With the latest posted version TmServerapp.apk started (twice) after conencting USB, so I thought it would work better.

[/quote]

During several tests I've noticed that when you start DriveLink without USB, the Home button works. After you connect USB, you'll get two warnings. While the first warning is displayed, home button still works. After hitting agree the home button seems to be disabled. To make it more confusing, it works this way on WanamLite 3.9 ROM (pretty much the same as Samsung stock), when I use my own HyperLite 0.9 ROM, Home button keeps working. Any details on when the Home button stops working on your device while starting Drive Link and connecting usb afterwards?

TmsService.smali:

Line 644: .method public setPhoneInCarMode(Z)V
...
Line 675: const-string v1, "android.intent.action.DOCK_EVENT"

AcsDeviceMngr.smali:

Line 2645: invoke-virtual {v0, v2}, Landroid/app/UiModeManager;->enableCarMode(I)V
...
[Galaxy S III Q&A, Help & Troubleshooting] walkeryan:
j0ep0 and I are going to collaborate and see if we can get this app tweaked the way we think it was intended to be run. I've setup a Github and plan on trying to convert the Smali files into a jar that can be compiled and easily changed. If anyone would like to contribute let be know in a PM. If you want a link the the github I'll post it up as well once we get the two files out there and are working.
[Galaxy S III Q&A, Help & Troubleshooting] Killa200:
Watching this thread and willing to help. Running SCH-I535 rooted, stock rom @ I535VRLHD. Sony XAV-701HD Headunit.
[Galaxy S III Q&A, Help & Troubleshooting] mrjoshzombie:
I know absolutely nothing about coding, but I can certainly test any .zip/apk I need to.

Sony XAV-601BT: HR10_xav_1.12.001 firmware

Verizon SCH-i535: Android 4.1.2, CM10 Nightlies

Might I also suggest starting a new thread that doesn't have 27 pages of clutter? It would make it easier for new users to find the data they need when popping into to see the progress.
[Galaxy S III Q&A, Help & Troubleshooting] Olywa123:
Agreed - maybe this is worthy of a thread in the development section now as there is a partially working solution (might gain more coverage there too).

---------- Post added at 10:49 PM ---------- Previous post was at 10:10 PM ----------

Gave it another shot just to make sure it wasn't me but still a no-go here - could it be because I'm still on ICS and you're running JB. Not sure.

Yeah, when connected via usb to the headunit there are two warnings (a caution about usb tethering/possible data charges and then a warning about driving while using the app) you have to 'agree' to both of these and then they are followed by the welcome/weather screen - which you click 'discard'. The 'mirroring' on the headunit doesn't actually begin until you have passed all of these (just have a spinning circle on the headunit) and trying the home button at each of these message/warning stages has no affect at all. When not connected to the headunit the home button returns to the launcher home at any stage like you found yourself (the caution about usb tethering and possible data charges is not present when not connected via usb though).

While I would like to see the home button working from the app I have come up with another temp fix (mentioned in my post below in case it's useful for others) so I'm not desperate or anything :)
[Galaxy S III Q&A, Help & Troubleshooting] miumiu77:
thanks

I have the same problem

---------- Post added at 11:13 PM ---------- Previous post was at 11:03 PM ----------

I have the same problem
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
It was Siyah kernel 1.7b6, which doesnt support car mode. With the latest version the home button beviour is the same as on your device. Excellent posts btw! (If wanted I can SuperchargeV6 your ICS ROM)

Edit: Also on latest XXDLIH version with normal kernel, home button is available in DriveLinjk. Just for the fun of it a TMServerapp.apk which doesn't put the phone in carmode after connecting USB: http://www.mediafire.com/?71g089yzv13w281. Thanks to walkeryan, finally some readable code :)
[Galaxy S III Q&A, Help & Troubleshooting] prerunnerseth:
Went ahead and rooted and installed CWM on my VZ SGS3 and tried to flash your Zip to install tmserverapp.apk and still no luck for me. tmserver wont load and I still cannot connect. :(
[Galaxy S III Q&A, Help & Troubleshooting] msgonz:
:confused:I need some help; I installed the drivelink apk on my sprint Galaxy S3. The app works if I’m on Wi-Fi connected to the 601bt. However if I try to use 3G Data it give me Error Code 67 "Your PCS Vision username and/or password may be incorrect" and the phone have no data connection until I disconnected from the 601bt.

It looks like the sprint thinks I’m tethering even though it’s just connected to the 601bt. I tried unrooted and rooted with the same results. I used QCOM Toolkit to root the phone; I didn’t try any custom ROM since I did know which one would be the best to use.

Any help would be greatly appreciated.
[Galaxy S III Q&A, Help & Troubleshooting] prerunnerseth:
Well ... looks like VZ released an update yesterday!... going to flash it and see if this fixes things like it did for ATT version. Crossing my fingers.
[Galaxy S III Q&A, Help & Troubleshooting] cell128:
I tried it....nothing :( I also tried flashing that tmserver.zip file with no results all I can do is wait. I did flash a jellybean touchwiz ROM for a bit and I didn't get that "USB device not recognized" message but it just showed a loading swirly circle.
[Galaxy S III Q&A, Help & Troubleshooting] prerunnerseth:
I'm probably going to return my phone today if we don't get a solution today.
[Galaxy S III Q&A, Help & Troubleshooting] cell128:
I'm thinking about changing out my unit to something else that has navigation built in I'm being patient though. What phone are you going to get?
[Galaxy S III Q&A, Help & Troubleshooting] prerunnerseth:
I'm just going to return it and wait for the Note 2. I have no doubt this will get figured out at some point, but tomorrow is my last day to return it so i dont want to risk it. I love the phone otherwise, but would rather have the Note 2 if this one isnt going to work with my HU.
[Galaxy S III Q&A, Help & Troubleshooting] cell128:
I think there's that new HTC super phone coming out for the holidays quad core s4 chip 5" 1080p screen.
[Galaxy S III Q&A, Help & Troubleshooting] rahularora1:
Hi just to let you know I have the note 2 and the Mirror link works with that in exactly the same way as with the sgs3.

Fyi I have an alpine ics x8 with mirror link but also alpine navigation
[Galaxy S III Q&A, Help & Troubleshooting] prerunnerseth:
I wish that was good news. but the international version and US AT&T version of the SGS3 work with mirror link as well, but the Verizon version does not.
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
Was thinking about your comment, with system apk's, Android is very picky on signatures (meta-inf folder the apk). To get that sorted, I need the original TMServer.app if you want to get it modified and test. Have to look for other options if your ROM doesn't contain TMServerapp.apk by default.
[Galaxy S III Q&A, Help & Troubleshooting] prerunnerseth:
I would love to keep working on this, but without knowing for sure this is going to work It wasn't worth it to keep the phone. I returned it and will wait for the Note 2.. Hopefully it will have support out of the box.
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
Best choice, eta for additional mods/functionality is unknown. When buying a Note2, check out the difference between AT&T and Verizon version,
[Galaxy S III Q&A, Help & Troubleshooting] mipstien:
This thread stopped rather abruptly. Did a new thread get started about this? I have a XAV-601BT Sony and have been following this thread in hopes of seeing some eventual usage of a Galaxy Nexus.
[Galaxy S III Q&A, Help & Troubleshooting] TheAngelus:
Me too, i dont really want to pay another £299 for the gps module.
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
No new thread started, but in the background we did some research. Disassembling Drive Link seemed to go pretty well, but the files with the main application give major errors. Without this being fixed, stuff like the home button enabling might be doable, but making it work on other platforms will be pretty hard. Also please don't forget we have a normal job and a family to look after. Hopefully I can find some time this weekend to dig in again and look at the options to get it running and recognized on CM10.

---------- Post added at 10:37 PM ---------- Previous post was at 10:16 PM ----------

Could you post the drivelink apk (app.scm-1.apk)? The one I am looking at only seems to like International (i9300) or japanse (SC-06D) Galaxy S3.
[Galaxy S III Q&A, Help & Troubleshooting] chinlin0924:
It uses USB NCM/CDC command, if u don't enter this mode. MirrorLink won't work at all.
[Galaxy S III Q&A, Help & Troubleshooting] walkeryan:
I too have been working long hours, being the only income with a new baby is rough and when I get home its hard to tell the wife I'm getting on the computer, lol. Money is tight, and formula is expensive. I will have quite a bit of free time at work once the project I'm working on is finished. I will be able to throw in some hours here after work to see what can be accomplished. As my partner in crime said, we decompiled the dex file to a jar but the resulting file doesn't always get converted completely and as complex as the drivelink app is (I know it doesn't seem like it but you try to put your phones screen on another device and accept input from it at the same time, lol). I started a Drive link development thread a while ago but it was shut down. I'm going to start another one so I dont have to sift through pages of crap. I'll try to keep the OP updated with requests and development progress.
[Galaxy S III Q&A, Help & Troubleshooting] walkeryan:
New development thread

http://xdaforums.com/showthread.php?p=33176372#post33176372
[Galaxy S III Q&A, Help & Troubleshooting] Olywa123:
Great start walkeryan :) Can I suggested adding the word 'mirrorlink' to the thread title - seems some people search specifically for mirrorlink and start new threads not realising the association with Drivelink.

Also, some suggested words you might want to consider adding to the first post of the new Dev thread to give people clarity as to what it's all about...

What is it

Drivelink is Samsung's application used to facilitate ‘Mirrorlink’ connectivity with supported car headunits. Currently their are several aftermarket car stereos by Sony, Alpine, and JVC that support this technology. The majority of users here have the Sony XAV-601BT headunit but it is believed the protocol for connection is the same for each. This standard is known as Mirrorlink (formerly Terminal Mode) and uses the VNC RFB3.8 protocol allowing for two-way communication between the smartphone and headunit over a usb connection for both display duplication and key-inputs and uses Bluetooth A2DP for Audio.

Videos

The following videos best provide a summary of this technology

Mirrorlink Overview: http://www.youtube.com/watch?v=sWNpKrEjWqs&feature=related

Example of MirrorLink on XAV-601BT: http://www.youtube.com/watch?v=BsT1l8bLOfU (shows Nokia and Samsung phone support)

Example of Drivelink App: http://www.youtube.com/watch?v=CHVmogapY9U

Why The Drive Link App needs Modification

Although Samsung have released the Drivelink application, this is not only very limited but also compatible only with the Galaxy SIII currently. It provides a ‘dashboard’ interface allowing for the use of only stock Music, Phone and Navigation (limited to Google maps) functionality. You cannot get back to your phones home screen or run any other apps while Drivelink is running/mirrored on the headunit and killing Drivelink kills the interface meaning the stereo no longer sees and mirrors the phones display. This appears to be a restriction coded into the Drivelink software as the video above shows that the Nokia interface allows for full phone control in addition to just the Nokia released Mirrorlink app on Symbian (Car Mode).

Feel free to add to the first post (or not :))

---------- Post added at 11:55 PM ---------- Previous post was at 11:23 PM ----------

Hi j0ep0, sorry never tried this out yet as it was for JB and I'm still stuck on ICS waiting for the official release of unbranded UK JB to drop - I should be fine with doing the superchargeV6 thing though, thanks for the offer - just reluctant to go through it if I will update very soon (actually if the firmware doesn't land by next week I'll prob try out one of your ready tweaked HyperLight roms) :)
[Galaxy S III Q&A, Help & Troubleshooting] richy562:
Hi everyone, i've been following this thread for a while, I just bought the Xav 601bt and installed it this week. very happy with the unit so far.

I thought i'd share my experience and try get some advise..

Firstly i'm running the Omega v28 JB rom on my SIII and updated the headunit to HR09_xav_1.12.001 firmware.

I've downloaded and installed the modified drivelink app from this tread and flashed the TMSever12 zip.

Unfortunately i'm unable to access any other apps by holding the home button down on the phone and going to recent apps. It just keeps keeps sending me back to the drivelink app. I've tried Nova launcher and Apex launcher with the same result. Drivelink itself works fine and connects to the headunit without any issues.

I'm not sure if im missing anything, i'm thinking it may be the Omega rom? I think its based of the samsung rom right?

Also i've noticed after installing the drivelink app my phone screen doesn't time out and stays on continously, this doesn't happen all the time it seems to be quite random at this stage, on one instance, even when i hit the power button it would turn off and come straight back on, had to reset it to stop it.

Any advice recommendations?

Cheers Richy

p.s had to post in this thread and not the new dev thread because i've just joined xda and can't post in there yet.
[Galaxy S III Q&A, Help & Troubleshooting] richy562:
Sorry forgot to mention i''m on stock kernel