yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Q&A, Help & Troubleshooting] crooozin:
I've had my s3 connected to my 601 bt since late July/early August. There was a few posts floating around where someone from England posted the app for the phone, as well as for the head unit. I honestly don't know HOW I ended up with it working just fine, but I did. ALSO: When the app first starts on my phone, the head unit will give the "no BT audio allowed"--- BUT, when I make or receive a phone call, guess what? it ends up going through BT! I don't know why but it does.

The only thing I ever did differently than all of the instructions I found around was to completely delete my samsung account from the phone and sign up to one on the UK webpage via my computer. I used that account to try and download it from the UK site with no luck; however, I still had that account set up when I d/l'd the package from around here. I get a registration failure with my sprint account, but it doesn't affect anything.

My comments on the whole deal:

First of all, drivelink sucks donkey balls. It's horrible. I couldve written a better one in my sleep, and I am not a coder. There are so many things wrong with the GUI it's pathetic. What does work, works with mediocrity. Google maps in my dash was the whole reason I even went this route- you can get to it, you just have to press a series of non-obvious buttons to get there through the lame-ass nav that constantly freezes on my system.

The music handling is just plain aweful. Just aweful. I want my PowerAmp!!!

The phone features are OK; like I said for whatever reason I get audio through BT. IF I turn BT off I get no sound or mic. THe messaging features are clumsy and buggy; I still cant figure out why my name and texts takes up the first like 10 in the list. THey aren't reorderable.

THe phone contacts list doesn't work, except the "favorites"--- so I have to go into the phone and make "favorites" from my contacts in order for them to appear on the head unit.

Shortcuts quite simply don't work at all.

Mirrorlink, on the other hand, seems to be quite robust. I've not had any problems with linking, handshakes, screen issues, etc, etc that could be attributed to mirrorlink (I think).

This is just my experiences with the system, your mileage is gonna vary

-CROOOZIN

---------- Post added at 04:21 PM ---------- Previous post was at 04:11 PM ----------

Oh, and I'll offer $100.00 US cash money for someone who knows what they are doing to get this whole thing right.... for Jelly Bean.... I want to be able to use other apps such as poweramp, maps (directly), etc, that shouldn't be too hard.
[Galaxy S III Q&A, Help & Troubleshooting] djwilliams100:
Here is my copy http://db.tt/qOQFGWTB

This is my copy of 1st release.
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
What I as wondering, what exactly happens when you connect the phone to your Sony unit, start Drivelink and then press the home button? Do you actually see the launcher on your Sony car unit? I'm thinking of a real dirty solution that has a small chance of working, but I can't test.
[Galaxy S III Q&A, Help & Troubleshooting] djwilliams100:
Yeah when using mirror link and the press home button on the head unit it returns u back to Sony launcher (tuner etc)
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
Maybe I'm not quite clear, apologies for that. What happens when you press the home button on your SGS3? My guess is that you return to the launcher screen, which is also displayed on the Sony headunit and when you try to start an app DriveLink takes over?

(Please say it works that way ;) )
[Galaxy S III Q&A, Help & Troubleshooting] djwilliams100:
It doesn't do anything unfortunately (if I remember correctly as I don't really use mirror link as it's clunky)
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
Maybe someone else wants to verify? Based on the following posts, I think I've a really dirty solution which I can't test. First the posts:

Based on these posts I was thinking about a solution to keep Drivelink running on the background and start and use other apps. Combine this with the fact that I'm a really bad devver, to be honest I'm not a developer at all (please don't tell). This results in all my attempts to modify the drivelink.apk in force closes while using the app. BUT when it force closes on the phone, it doesn't close completely, the drivelink app keeps running in the background. The only thing I can actually test if the VNC server is still running on te phone, and that seems to be the situation.

So maybe someone can test tbis. Only works with Nova launcher installed:

- Make sure you have a Drive Link apk or Samung Apps to reinstall drivelink after testing

- Uninstall Drive Link

- Enable the following option in Android Settings -> Security -> Unknown sources

- Download this file to your phone: http://www.mediafire.com/?2490bi2r0g8qcw9

- Install the file

- Connect your phone to the Sony headunit

- Start Drivelink and do the things you normally do to get the phone working with the unit, don't start the Music app before everything is working

- Start Music from Drive Link

- Drive Link crashes

Alternative test, onky works with google maps installed:

- Use the method above but dont start music

- In Drive Link set Navielite as your navigation software under Settings -> default app

- Go to Location

- Open navigation

- Drive Link should crash

If you're lucky, you now see your android launcher on your Sony headunit. You can start programs without Drive Link popping up. Again, I cannot test it myself, but this might (again: small chance) work. Let me know if this worked. If it doesn't just remove the app and install the original Drive Link again.
[Galaxy S III Q&A, Help & Troubleshooting] cnewman402:
Just tried the 1st version after moving over to Cyogenmod 10, and still no weather. Have not tried the mirrorlink its too late. I will also try the above mentioned to see if it works. Before I do what it the download in that post?

:confused:
[Galaxy S III Q&A, Help & Troubleshooting] Gothan:
Mirror link does not work on CM10/AOKP/AOSP roms, only on SAMMY roms. Drive link works, but your headunit will not pick it up if you run anything other than samsung rom
[Galaxy S III Q&A, Help & Troubleshooting] Olywa123:
j0ep0, I have downloaded your file and will try to give this a go at some point this weekend and let you know.

walkerryan, any news on your fiddling?

If neither of the above are fruitfull I guess we need to revert to the original plan - update the original post and make a formal request to dev's for help.

BTW - Drive Link seems to have been updated on 10th October on Sammy Apps (although as far as I can see the version no. didin't change - still 1.1.012) so not sure if there is any difference.
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
Nice, I'm very curious if this dirty method works, it could open possibilities for getting a decent solution. If I find some time, I'll look at the requirement to get Mirrorlink running on non-Samsung based roms.
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
Did some testing and Drive Link and Mirrorlink seem to be working on CyanogenMod with the packages below. VNC can connect, so I expect mirrorlink to be working. I've added the early release of Drive Link as this is the most compatible version. Newer versions should be working as well.

Drivelink for i9300 with CM10 or other Non-Samung JB ROMs: http://www.mediafire.com/?pwzw2w14h2no1ha

Drivelink for i9300 with CM9 or other Non-Samung ICS ROMs: http://www.mediafire.com/?ckecvrirh4ce125

I can't test the CM9, but it should work. Please report back :)
[Galaxy S III Q&A, Help & Troubleshooting] cnewman402:
Will try out first thing tomorrow.
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
Your sig reminds me that the files uploaded are for GT-i9300, apologies for not being clear.

Drive Link for SCH-i535 with CM9: http://www.mediafire.com/?vt8t58ow34nbbf0

Drive Link for SCH-i535 with CM10: http://www.mediafire.com/?od7h3d84d19ilf2
[Galaxy S III Q&A, Help & Troubleshooting] Olywa123:
Is XDA painfully slow today or just me!?

--

Hi j0ep0, well I gave your ‘dirty’ method a go and while not really successful it does seem to be a step in the right direction...

The Bad

-Followed your steps and on selecting ‘music’ in your version of drivelink, the app does crash – unfortunately this kills the connection to the head unit (get device not recognised on the screen), I tried this a few times with no luck.

-Can’t follow your second steps as Navielite is not available in my region (don’t find it on the play store) so can’t set that as the default in drivelink (I assume the results would be the same as above though).

The Good (partly)

I fiddled and tried out a few different things. With your version drivelink running I held the home button to get to the ‘recents’ menu and selected ‘Nova Launcher’ from my recents. This did give me full mirroring of the launcher on the headunit so it looked good, you can scroll your home screens in Nova Launcher and everything is there as you would hope and it doesn’t disappear or crash. Unfortunately that’s all you can do, trying to access anything from Nova/home screens (i.e. dialer/sms/any apps) just dumps you right back into the drivelink menu/homescreen.

So it seems to be some progress at least – whatever you did to make Nova ‘stick’ had worked – it’s just rejecting everything else as normal – perhaps what you did for Nova can be applied to individual apps?

Hope it helps.
[Galaxy S III Q&A, Help & Troubleshooting] fubu2k:
i will test the cm10 package with my galaxy nexus soon :)
[Galaxy S III Q&A, Help & Troubleshooting] fubu2k:
hmm i copied all 3 folders of the cm10 package to the root of my system and gave them rw rw r rights. after rebooting my device, drivelink was also installed. i started the app without any problems. while plugging my device (galaxy nexus) to the sony unit (september firmware) it is still not recognized. error: usb device not recognized. iam using the standard usb cable. maybe, do i need an adapter that mirrorlink is working?

on my phone the original jb 4.1.1 is installed
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
Thanks for testing. Unfortunately, the crash method doesn't work, so I dug into the code again. This time, I created a modified Drive Link apk, it is the latest version and all functions are working as normal. The big change is that it doesn't come into the forground when you start other apps. I tested this with on Samsung stock JellyBean with Nova Launcher and could browse, open settings, whatsapp et cetera while connected on usb.

This version can be installed by removing your current version, enable unknown sources and install this apk. Get it here: http://www.mediafire.com/?25xw30a5447yo96

@ Fubu2k, to be clear, above apk is for samsung roms. Have to dig in CM10 further. There might be some checks from the unit itself. If you have time, you might want to test the package by flashing it in CWM or another recovery so that permissions are ok without changing anythinh else.
[Galaxy S III Q&A, Help & Troubleshooting] Olywa123:
Hi j0ep0,

MASSIVE steps forward!!

As before I connected up, started your most recent modified ‘Drivelink’ app and with that running I held home button down to get to recents and access Nova Launcher home screens (a tap of the home button still doesn’t get me there but no bother).

and... Wow – everything I tried worked! I was able to access various apps/dialler/sms/email – all mirrored on the Sony head unit and audio running through the car speakers (and car mic where applicable)

A list of things I tried that worked:

Nova Launcher Home screens (obviously), Stock Dialler, Stock SMS, Stock Gallery App, Stock Browser, Dolphin Browser, Google Maps, Sygic Navigation Software, S-Voice, Google Voice Search, Cut the Rope, Root Explorer, Video Player, Camera, settings, a few other random apps.

So really good so far but I did hit one problem – a couple of times the drivelink app did stop working and connection was lost, this was not always with the same app/same point or after the same amount of time so not easy to replicate. I get the feeling that this could be a memory issue – it happened when scrolling through lots of photos in the gallery, when loading up my inbox in the email app and when opening the camera. Restarting everything and trying these same things again did not always repeat the problem. I think maybe because Drivelink is no longer in the foreground that Android memory management is killing it off eventually when RAM is needed elsewhere – could that be the case? any way to make it so that this doesn’t happen?

Anyway – I need to do some more testing (won’t get chance tomorrow but next few days hopefully) but so far – I am majorly impressed – If the crashing issue can be resolved my $30 donation is yours buddy. If the whole solution/access to the launcher can be made cleaner/easier I will up my donation to $50

Thanks, Olywa

Please – any other members here that already have Drivelink working - do give this a try and report back – it will help j0ep0 and to be honest it is already pretty impressive.
[Galaxy S III Q&A, Help & Troubleshooting] shirazdindar:
wow, nice work j0ep0!!

I tried installing your latest on my CM10 on my Samsung Skyrocket (the Samsung Galaxy 2.5, you might say), but as all other versions, "Unfortunately, Drive Link has stopped". I believe this is expected, but just wanted to let you know if not.

Also, I was the only one who requested CM9 support, and CM10 on the Skyrocket became solid enough for me to switch this week, so I don't think you need to worry about it at all. Seems CM9 development is petering off generally.

Anyhow, I'd like to increase my donation to $50 pending a successful implementation on CM10 Skyrocket.

Kudos to you, sir!
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
Glad to see it working, the solution can be polished a bit but this should be the base. Regarding the home button, on my device I can start DriveLink, then press home and Tesla is there. Strange that it doesn't work for you. Which ROM/software version are you running? Maybe I can reproduce it. All apps should work by the way, the only limit is free RAM.

The other problem of Drive Link getting closed is, like you said, probably due to memory management. Android 4.0 and 4.1 have pretty aggressive memory management which will kill apps that are unused for a while or to free memory if needed. Lots of tweaks are out there to prevent this. If I know your current ROM I can hopefully help out on this as well. Root permissions might be necessary to accomplish this by the way.

Thanks for the update. For me, CM10 support will be hard. The latest version is indeed CM10 incompatible, but to make a possible compatible version for your device, I need the exact type, is it the i727?
[Galaxy S III Q&A, Help & Troubleshooting] shirazdindar:
Yes, the i727 = Samsung Skyrocket. :) I would be impressed with anything about Drive Link working on this phone at this point to be honest. So, CM10 support would be hard because of the sheer diversity of devices, or for some other reason? I guess the single package working across Jelly Bean ROMs, across phones, is a pipe dream at this point? Or to be more specific, which is harder -- cross ROM, or cross device?

Thanks!!
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
To get DriveLink working, I create a flashable package that contains the Touchwiz framework for your device. All these frameworks are different (at first look) so every model needs a seperate update file. That's a lot of work, but I can write an instruction so people can do it on their own. Problem here is Samung releases lots of devices with customized software.

You might want to try the i535 file to see if that works: http://www.mediafire.com/download.php?od7h3d84d19ilf2. It won't break anything. Another users (with i535) reports that Drive Link starts and works, but isn't recognized by the headunit. That last issue is quite a challenge, especially since I don't own a Mirrorlink enabled car system.
[Galaxy S III Q&A, Help & Troubleshooting] shirazdindar:
I see. It does sound like an instruction doc would be the way to go for sure. In any case, I tried the i535 package to no avail (same error msg).

It's crazy that you don't have the head unit yourself. Are you in this for the bounty or just as a good deed, or both? Or perhaps because you simply see the awesome potential in this? We may have enough in the pot now to buy you the deck though there's this chicken and egg issue in that people will want a working program before putting their share in. I personally trust you enough as you have been pretty dedicated so far, but I'm not sure what others think. To what extent would it help you to actually have the deck?

\
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
The first steps to get Drive Link working on non Samsung based ROMs are quite simple. Reminder, the usb device not recognized isn't fixed.

1) Download a Samung based rom (JB is recommend, ICS should be tested).

2) Extract the following files:

- /system/app/app.scm-1.apk - if it's not there, don't worry

- /system/app/TMServerapp.apk - if it's not there, don't worry

- /etc/permissions/touchwiz.xml

- /framework/twframework-res.apk

- /framework/twframework.jar

3) Get a zip that can be used as a CWM flashable file, for example this.

4) Open it with 7-zip and put the files you've extracted in step 2 in it. The folder stucture is the same. If you couldn't find the apk's in step 2, leave the current apk's in te zip

5) Flash the file in CWM or another recovery and reboot

For your phone I couldn't find a Samsung based JB ROM, you might want to try adding the files from an ICS based stock Rom, but that's really trial and error. Next steps in solving the usb device not recognized are:

- modifying CM10 that is presents itself 100% as a S3

- checking the Sony source code

The main two reaons I'm in here; I'm interested in learning new stuff and I can't stand the fact that this sweet technology is being restricted to a few apps that Samsung approves. Too much Apple if you ask me. It won't help really much if I get the deck, the usb issue might be way out of my league.
[Galaxy S III Q&A, Help & Troubleshooting] Olywa123:
Hi j0ep0,

Thanks again. I managed to have a bit more of a play with it this lunch time, finally being able to use voice commands to play music as well as being able to use whichever Nav software we want is just awesome.

Regarding the home button – I think this is something in Drivelink telling it that if the home button is pressed when connected via mirrorlink then to revert to the drivelink homescreen not the phone/Nova homescreen (to be clear this only happens when connected to the headunit, if not connected and running drivelink the home button does work as expected, taking you to the Nova homescreen). Would be great if there is a way to fix this.

The crashing issues definitely seems to be RAM related as you say – I installed a free app called ‘Smart RAM Booster’ which frees up RAM at user defined intervals (i.e. every 15 seconds), adding drivelink to this apps ‘whitelist’ means it doesn’t get killed as often and I was able to do a lot more for a lot longer before I saw any crash. Any pointers on the tweaks are out there to prevent this would be good as I’d prefer not to have to use the RAM booster. I am running Rooted Stock XXBLG8 ICS 4.0.4 by the way (but will likely make the jump to JB in the next couple of weeks when the UK update finally hits).

Again thanks for your effort on this. For me, you’ve delivered a workable solution here for the S3/i9300 so I’ve just donated $30 to you. PP Confirmation number: 4GU82.........10N (and another $20 still up for grabs if the home button can be made to work :))

Really hope your tips help out the others with compatibility of their phones so they can get to enjoy this too.
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
Thanks a lot for your generosity, really appreciate it! For RAM tweaks, there are lots available, some of them are easy, some of them are more complicated. You can also use a custom, tweaked ROM.

- supercharger V6 - more details here

- mattiadj multitaskingfix (JB)

- adjust lowmemorykiller (for example echo "2560,4096,6144,10000,22000,25000" > /sys/module/lowmemorykiller/parameters/minfree) - see here for explanation

- Run a script that checks the process id of Drive Link every 5 minutes and sets OOM value to -17 (these apps are killed last) (comparable with Smart RAM booster)
[Galaxy S III Q&A, Help & Troubleshooting] murso74:
Tried this on my stock ics att note but it was a no go. Keeps telling me device not supported and to reestablish connection to device
[Galaxy S III Q&A, Help & Troubleshooting] mrjoshzombie:
Wow, this is a helluva lot of progress I missed over the weekend!

I'm going to flash the i535 file to my CM10 Nightly rom and see what happens. By the sounds of it, I shouldn't expect much, but I figured I'll help in what ways I can.

**Edit

Nope, no go. DriveLink opens up just fine, but I'm still getting the "USB not supported" message. I tried both methods of USB input as well.

This is on model number SCH-I535, Android 4.1.2 10-20121012-NIGHTLY-d2vzw CM10 rom.
[Galaxy S III Q&A, Help & Troubleshooting] fubu2k:
modifying CM10 that is presents itself 100% as a S3 will be fine :)

there is no sammy rom for the samsung galaxy nexus... :(
[Galaxy S III Q&A, Help & Troubleshooting] shirazdindar:
so how do modify CM10 to change what the phone presents itself as? i'm not clear on what the deck is actually querying here. hoping we can do this in a way that doesn't affect the device identification on Google Play.
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
I've checked all the USB id's, and for the i9300 on CM10 they seem to be correct. If I understand the replies correctly, there are two possible errors, not recognized and not supported. Could someone please post the exact error(s)?
[Galaxy S III Q&A, Help & Troubleshooting] JabroniMx:
Works on my S3 / XAV710 :) Was able to do some Grooveshark playback, just after a while i did experience the commented drivelink restart, but this looks promising. The only drawback i had to have Grooveshark running before Drivelink, so when i was on the dashboard, i could leave the home button clicked to get the running programs list, and then I could switch to Grooveshark
[Galaxy S III Q&A, Help & Troubleshooting] mrjoshzombie:
I'm getting "USB device is not recognized" on mine.
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
Regarding the Home Button not working in the app, please test "version 1.1": http://www.mediafire.com/?pabq2ajfr81dz2t . The Back button is functioning as normal, so don't use it in the Drive Link app, it will close it. Interested in your feedback.

(versioning is just for clarity, 1.0 is the previous apk which enabled using other apps).
[Galaxy S III Q&A, Help & Troubleshooting] Olywa123:
Thanks yet again j0ep0, unfortunately no luck with this one either, I uninstalled the prev version and put this one on but still no 'working' home button (just takes you back to drivelink home or does nothing if already in drivelink).

Thanks for trying
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
Thanks for testing :) If you're in for a new test, I've modified tmserverapp.apk:

Original version (to flash back): http://www.mediafire.com/?jl6o7obl5gz38b3

Modified version (to test): http://www.mediafire.com/?zzq6tj9tgcvce8x

Sorry about the trial and error method, but at this moment it's the only way. Please let me know if it works, I've tested for FC's and it seems to be fine.
[Galaxy S III Q&A, Help & Troubleshooting] prerunnerseth:
Anyone have luck with this on a Verizon Galaxy S3. I have the HR10 Firmware installed on my XAV-601BT and the newest version of the Drive link apk. Drivelink apk launches and runs perfectly but I get no connection to the HU. It asks me to reestablish connection with smart phone. The guy over at Best Buy was able to just download the Apk, plug in, and have it working. Not sure which carrier his SGS3 was from or what version of APK or Firmware their demo unit was using. I specifically bought this HU Because of this feature. am I missing something? Do I need to use the USB cable that came with my SGS3??