yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Q&A, Help & Troubleshooting] Olywa123:
Hi Richy, ok, your headunit firmware is the right one, pretty sure Omega is Sammy based (has touchwiz right?) so it's not those and using Nova as your default launcher this should definitely work for you (I'm assuming it's the GT-i9300 model you have?).

TMSever12 was sort of a test version by j0ep0 - could possibly be the issue (actually with a sammy rom you shouldn't have needed to update tmserver if it was already there so if you have a recent backup to easily revert back to (without too much grief) do that, or if easier just use this one : http://www.mediafire.com/download.php?3926b2kuewyn84i

Also make sure you are using the right modified drivelink - think there were a couple of different ones but this is the one I am using: http://www.mediafire.com/?25xw30a5447yo96

Let us know if you do manage to get it working and have a read back in this thread for some pointers (from about page 24) :)

---------- Post added at 03:41 AM ---------- Previous post was at 03:33 AM ----------

I also get this sometimes, doesn't seem to be any pattern to it but it's def a bug in the original drivelink app - you will just need to kill off the services to make make sure it's closed if you find your phone is not timing out. Go into settings-->Application Manager-->Running-->Drivelink and stop any processes (a bit of a pain but maybe it can be fixed later).
[Galaxy S III Q&A, Help & Troubleshooting] richy562:
Thanks Olywa, i'll try those few things when i get home tonight and report back.

And my phone is the GT-I9300
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
Good post and I think it's important to stress out that TMserverxx.zip are for testing purposes only. I've cleaned up mediafire folder a bit, and these should be correct:

- Drive Link without continous resurfacing: http://www.mediafire.com/download.php?25xw30a5447yo96

- TMServer for Samsung based i9300 ROM's: http://www.mediafire.com/download.php?3926b2kuewyn84i (most of the ROMS should have it)

- TMServer for Non-Samsung based ROM's: http://www.mediafire.com/download.php?i2bb62rc4z87g20 (testing purposes, TMServer won't start)
[Galaxy S III Q&A, Help & Troubleshooting] spscoral:
So none of these are supposed to work yet with the US (specifically Verizon) GS3 ROMs, correct?
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
At least not 100%. The files in the TMServer packages are based on GT-i9300 (international) Samsung firmware. That goes for the TMServerapp.apk file as well as the Touchwiz framework. You can try, but statisfaction is not guaranteed as I don't have the device itself. Will clean up the files this weekend.
[Galaxy S III Q&A, Help & Troubleshooting] spscoral:
Would I just download the files in the first two links and side load to try? At this point, I'd be happy to get to a point where my head unit (XAV-601BT) will connect to my phone at all. My expectations are low as far as the overall functionality... I really appreciate all of your efforts here!
[Galaxy S III Q&A, Help & Troubleshooting] Searchbox:
I'm with you Sir. It would be nice for the radio to even recognize my phone via USB. I have newest firmware for the 601BT and Drive Link for the SCH-l535

and device still not recognized :) I wish Samsung would just it over with and come out with a nice Touchscreen Allshare Radio Device... call it the TARD, I'd buy it.
[Galaxy S III Q&A, Help & Troubleshooting] cell128:
+1 for TARD
[Galaxy S III Q&A, Help & Troubleshooting] pedderd:
I did want to post in the separate development thread, but as a new user it doesn't let me. Hopefully here will still get read. I am new to Android and rooting, though have been jailbreaking iphones for a few years.

I have an S3 (Voda UK) and an Alpine ICS-X8, which was purchased recently because it was compatible with Android. Drive Link is pretty poor as others has mentioned and I am well up for what the developers are attempting to do here.

My S3 is rooted and installed with NxtGen's ROM, v5.1 and is a big improvement, especially battery life. However my experience is that the connection with the Alpine does not work since I installed the ROM. I have tried to revert the S3's ID back using Titanium backup, I have tried to uninstall and reinstall stock Drive Link app, and I have also tried installing the TMServer and Drive Link apk - but still the Alpine refuses to accept. "Device not recognized" is what it tells me.

It is noted on here that car mode has to be enabled for it to work, and I have just found out where car mode is hidden in the phones settings, so will try to force this on. I also noted CDC/NCM is needed ? No idea on this one.

Anyone had similar experiences ? I will try the car mode later and report back. Hope I can be of some assistance.
[Galaxy S III Q&A, Help & Troubleshooting] pedderd:
My post above - I did not resolve the connection....even with car mode enabled. It seems all this does is play audio through the connection.

Any pointers ? I will have to revert back to stock ROM as I need the drive link for navi
[Galaxy S III Q&A, Help & Troubleshooting] iandoug:
fake it

I am in South Africa and was only able to find and download the DriveLink app after I had used MarketEnabler to pretend to be on the Vodacom UK network.

However have not yet succeeded in getting the Sony unit to talk to my S3 ... when I connect the USB cable, Drivelink starts up, but the Sony tells me it is an unknown device.

S3 is rooted and running CriskelRom.

Any ideas gratefully received :)

thanks, Ian

---------- Post added at 04:14 PM ---------- Previous post was at 04:12 PM ----------

Please can you give idiot-proof instructions for finding Car Mode ... :)

thanks, Ian
[Galaxy S III Q&A, Help & Troubleshooting] pedderd:
Car mode - Settings / Language and Input / Text-to-speech output / Driving Mode
[Galaxy S III Q&A, Help & Troubleshooting] laxity:
The "device not recognised" message appears if the mirrorlink connection is not established with the Alpine unit. The message often appears when Drive Link starts and left on the "accept" the disclaimer notice screen as the mirrorlink connection doesn't start until you pass that point.

Also, I have found that the latest Drive Link app 1.1.012 doesn't work properly with the official Ice Cream Sandwich ROM and the Alpine ICS-X8. The older 1.1.011 worked fine though with ICS. When I finally upgraded to the official Jelly Bean 1.1.012 I found that it now worked with my Alpine unit.

Not quite sure what might be happening with your set up if it worked previously, but the points above may be food for thought.
[Galaxy S III Q&A, Help & Troubleshooting] iandoug:
thnx but no cigar

Thanks, put it in said Car Mode but the Sony still says it is an unsupported USB device.

The struggle continues :)

cheers, Ian
[Galaxy S III Q&A, Help & Troubleshooting] texan_ranger:
Galaxy S2 int version

Hi Guys,

Been following the thread for the last week. Been interesting following the attempts at getting a working solution.

Like Ian I am also in South Africa and have ordered the XAV-701BT in the hope that shortly there will be a solution. I have a International Galaxy S2 and have access to an International Galaxy S3. My S2 has been running CM10 for quite a while already. The S3 is stock and not yet on JB. I will be getting my Head Unit next week and would really like to be able to start doing some testing from my side.

As a stupid question has anyone actually tried to contact Sony or Alpine and ask what APIs are available for App development. According to the MirrorLink website the consortium has or should have got APIs together. For Sony to have done demonstrate at CES 2012 with the SGS2 and again on the link posted here from the UK Sony guys also demonstrating SGS2 connection. This means that there has to be APIs and apps available. Maybe considering that Sony has released the source code for the Head Units they would then be willing to send through some APIs for DriveLink and or MirrorLink itself. I am sure Samsung will not be the ones to come to the park with this as it would not promote sales of their newer handsets that will all be working or ready for mirrorlink. Sony and Alpine on the other hand will definitely be interest in a larger pool of potential sales.

Any ways guys I really appreciate the hard work and I look forward to some potential testing files when I get my Head Unit next week.

Regards

teXan
[Galaxy S III Q&A, Help & Troubleshooting] pedderd:
"Hopefully" I have stumbled on my cause. My thoughts were that drive link was not automatically starting when plugging the cable in.

So, after trawling the settings, I disabled 'USB debugging' under developer options.

And voila, sorted !

Will try this again tomorrow with the apk attached to the other developer thread.

Hope this helps you ?
[Galaxy S III Q&A, Help & Troubleshooting] iandoug:
{fume...!}

I've been talking to Dave@Sony here: http://www.talkaudio.co.uk/ipb/inde...laxy-s3-surpport/page__st__20__gopid__4222288

Will ask him your question ... :)

thanks, Ian
[Galaxy S III Q&A, Help & Troubleshooting] djwilliams100:
Bookmarked for future reads, thanks. Good to see they plan on quarterly updates. If it's anything like the last head unit update, not much will be updated/added.
[Galaxy S III Q&A, Help & Troubleshooting] texan_ranger:
I commented on his video post. How can they falsely "Advertise" something like that. It is so frustrating. I made the decision to go with the Sony over the Pioneer AppRadio 2 because the AppRadio is useless unless you have an actual phone. I have also toyed with the idea of building my own radio with a RasberyPi and buying a 7" capacitive touch screen but then I would still have to purchase a bluetooth unit like the Mobridge M1000 or alternatively actually build something from a Parrot bluetooth module.

The Sony unit at least has DVD and USB playback.

I might just get my bother's N8 from him purely for the navigation aspect. Leave the phone in the car without a simcard.

I am waiting patiently for solutions to MirrorLink on the SGS2.

Hope everyone has a good HUMP DAY.

Regards

teXan
[Galaxy S III Q&A, Help & Troubleshooting] cell128:
I finally got drivelink working on my Verizon gs3 on the new leaked jellybean ROM. http://xdaforums.com/showthread.php?t=1853337

The app is very buggy though and it keeps freezing on my within a minute evsrytime. Hopefully this technology gets better because I'm really stating to get annoyed by this.
[Galaxy S III Q&A, Help & Troubleshooting] djwilliams100:
This is a force close error I got when I started my car and my head unit came on this morning..
[Galaxy S III Q&A, Help & Troubleshooting] Kan-g:
Hello guys,

Many thanks for the hard work you have done till now!

Hope you are going to continue.

I have a galaxy nexus and a padfone.

Moreover, I'm a big fan of Alpine for the quality of the sound. Last weekend, I installed the Alpine ICS-X8, really better than my 502!

Are you going to port your work for all Android JB devices?

If yes, I'll be glad to provide my help for testing purpose or to check with my network to develop further.

Again, many thanks for your work :)
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
Porting is very hard because disassembling doesn't go properly and sourcecode isn't provided....
[Galaxy S III Q&A, Help & Troubleshooting] shirazdindar:
thanks for engaging the sony rep, iandoug. he was helpful. alas, this pretty well tells the story -- "This pairing will not be relaxed as it is a key tenet of how MirrorLink operates. For a unit to be MirrorLink certified, it must adhere to these standards.". Sony is bound by the Car Consortium. We're definitely not going to get them to open any APIs for us.
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
Did some sunday-evening pondering and made a new TMServer package for CM10 (i9300). All my tests (without a unit) succeed, e.g. TMServerapp is running, VNC server is reachable. If someone would like to test it on his/her i9300 with CM10 and a mirrorlink headunit, please. Also test with USB debugging tunred off and on. Please report back:

- The device you're using

- CM10 build

- Is TMServerApp.apk running after starting DriveLink and connecting USB? (check with System Tuner or likewise app to show system processes)

- If TMServerApp.apk running, the exact error (or not) from the head unit

Edit: new files here http://xdaforums.com/showpost.php?p=33733620&postcount=326

If TMServerapp.apk is not starting on i535 or i747, please DM for a procedure to get it running (probably). For testing on other platforms send me a DM for more info. A working stock ROM is required. And keep in mind, this is just another test.Quite busy this week, so don't expect fast answers.
[Galaxy S III Q&A, Help & Troubleshooting] mrjoshzombie:
Very interesting.

Device: SCH-i535

Build: cm_d2vzw-userdebug 4.1.2 JZO54K eng.20121104.022645 test-keys

Is TMServerApp.apk running: It tries to, but force closes

Headunit Error: USB Device is not supported

So, I noticed the USB tethering becomes active, TMServerApp opens up (and then force closes, tries to open again, force closes), and despite getting the error on the headunit, after a moment it begins to almost connect. The screen switches to the circling dots, but the image is never mirrored. I feel like this is getting painfully close to working on CM10 now.
[Galaxy S III Q&A, Help & Troubleshooting] texan_ranger:
Enjoying the Progress

Hi Guys,

Thank you for all the hard work.

But just a question, how hard will it be to make the TMServer and drivelink work on the GT-i9100 running CM10. I would like do some testing for you guys. Will have my head unit by Wednesday.

Regards

teXan
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
Thanks for testing. If you have experience with logcats let me know. I really would like to see a logcat of the FC.

I understand your curiosity, but I really can't tell.
[Galaxy S III Q&A, Help & Troubleshooting] gpmIII:
more info on 601/701 sony headunits

The other very cool thing is that if you notice when you use the Bluetooth audio streaming it's much clearer than anything else because when use satellite radio or your iPod they compress the audio which doesn't sound as good the Sony Bluetooth does not compress it at all in anyway so you get direct digital audio sound quality which is phenomenal
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
With much thanks to mrjoshzombie, I've found the reason for the TMServerApp FC'ing after connecting. It was missing some libraries, so I've added it to the installer. It is starting on i535, so I expect it to be starting on i747 as well, that means on 3 CM10 platforms DriveLink is running and TMServer starts. That last one is a step forward, now on to fixing TMServer and see where we end. For the new test I've created some CMW flashable zips containing TMServerapp.apk, Touchwiz framework and (new) TMServer libraries.

Please test and report back:

- The device you're using

- CM10 build

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

- Logcat (check this thread)

Download i9300: http://www.mediafire.com/?is611vkxabwpzxy

Download i747: http://www.mediafire.com/?y1p6ll93e444l9x

Download i535: http://www.mediafire.com/?b0vbddxz224d0hj
[Galaxy S III Q&A, Help & Troubleshooting] mrjoshzombie:
Glad those helped. Downloading now and I'll test on the way home when I get out of work. Here's hoping!
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
With thanks to mrjoshzombie, a pretty quick update. It seems that there's another major step made, but the first tests show that mirrorlink is reported to be working on CM10 on the i535. It has some bugs (not everything is landscape and usb audio not working) which might be fixed in the app, but also when using workarounds. For example, I ran into Car Home Ultra, which looks like it is the app that DriveLink should have been. As far as I know it doesn't support mirrorlink natively, but it has some options (Display orientation, Enable car mode, BT settings) that could fix the bugs present with mirrorlink on CM10.

Looking at this positive results, I invite every CM10 user to try the earlier posted files and report back with the requested details. With every CM10 user I also mean non-S3 owners. Exepct no miracles, but deeper insight is needed in the app functioning on both S3 as well as non-S3 devices. Your feedback is appreciated!
[Galaxy S III Q&A, Help & Troubleshooting] texan_ranger:
Assistance in ADB Logcat

Ok so I managed to get a logcat file saved. Is there a way to only look for the information that you need from the Logcat. I let the Logcat write to file while opening the Drivelink App.

Device: Samsung Galaxy S2 (International GT-i9100)

CM10 Build: cm_i9100-userdebug 4.1.2 JZO54K eng..20121105.011632 test-keys

TMServer app: Not sure on TMServer, drivelink FC'ing

Logcat: see attached file
[Galaxy S III Q&A, Help & Troubleshooting] mrjoshzombie:
It may just be the latest build of CM10 nightly that isn't allowing the device to rotate. Thanks to the suggestion from j0ep0, installing Rotation Locker from the Play store solved that issue, and I can just force everything into Landscape to use with the headunit.

Right now, my only issue with CM10 and Drivelink is no audio playing. I haven't had a single force close since last night, the app hasn't just stopped working, no memory kills, nothing. We're so close to this working now!
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
Usb audio has some issues on cm10, but a fix might be close. Check this interesting thread: http://xdaforums.com/showthread.php?t=1930664
[Galaxy S III Q&A, Help & Troubleshooting] mrjoshzombie:
So, basically, it's nothing with DriveLink, just Cyanogenmod. That's both good and bad news then. Do you think it'd be possible to continue to route audio through bluetooth?

I think, my last request with this, is altering the home button that's displayed on the headunit, to go to the launchers home screen, and not back to drivelink. Then this would be perfect.
[Galaxy S III Q&A, Help & Troubleshooting] Killa200:
I'm not sure about the 601, but the Sony XAV-701BT forces bluetooth audio off to the phone when starting mirrorlink.
[Galaxy S III Q&A, Help & Troubleshooting] mrjoshzombie:
The 601 does indeed have the same habits, I just wasn't sure of work arounds for it.

---------- Post added at 02:44 PM ---------- Previous post was at 01:51 PM ----------

Flashed the latest CM10 nightly (1106), still no USB audio, and no amount of trying to switch between Mirrorlink and Bluetooth audio will transmit over bluetooth. It seems it's a headunit restriction, not a phone.
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
Not all the changes afor USB Audio on CM10 are approved, so no support yet. If I understand things correctly, you should get extra options in Settings -> Dock when the changes are approved and committed.

TMServer with altered Home button for testing purposes is here: http://www.mediafire.com/?wtbh2t7010814cz. Works on CM10 only. Interested in your test results.
[Galaxy S III Q&A, Help & Troubleshooting] mrjoshzombie:
Downloading now, will test on the way home.
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
Thanks for your reply and logcat, DriveLink FC'ing is bad news. I've looked into it a bit and I can't fix this on short term. If someone more experienced is reading along, this is what happens:

Logcat:

[ 11-06 12:13:35.230 13792:13792 W/ResourceType ]
Failure getting entry for 0x7f030030 (t=2 e=48) in package 0 (error -75)

[ 11-06 12:13:35.230 13792:13792 D/AndroidRuntime ]
Shutting down VM

[ 11-06 12:13:35.230 13792:13792 W/dalvikvm ]
threadid=1: thread exiting with uncaught exception (group=0x40df3300)

[ 11-06 12:13:35.230 13792:13792 E/AndroidRuntime ]
FATAL EXCEPTION: main
java.lang.RuntimeException: Unable to create application app.scm.main.ScmApplication: android.content.res.Resources$NotFoundException: Resource ID #0x7f030030
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4339)
at android.app.ActivityThread.access$1300(ActivityThread.java:142)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1268)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4931)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:558)
at dalvik.system.NativeStart.main(Native Method)
Caused by: android.content.res.Resources$NotFoundException: Resource ID #0x7f030030

Resource ID #0x7f030030 is defined in R.jar:

public static final int vehicle_motion_layout = 2130903088

The error occurs in ScmApplication.smali:

.method private createPopUp()V
.locals 15

.prologue
.line 312
const-string v11, "layout_inflater"

invoke-virtual {p0, v11}, Lapp/scm/main/ScmApplication;->getSystemService(Ljava/lang/String;)Ljava/lang/Object;

move-result-object v4

check-cast v4, Landroid/view/LayoutInflater;

.line 314
.local v4, inflater:Landroid/view/LayoutInflater;
const v11, 0x7f030030

const/4 v12, 0x0

invoke-virtual {v4, v11, v12}, Landroid/view/LayoutInflater;->inflate(ILandroid/view/ViewGroup;)Landroid/view/View;

move-result-object v9
[Galaxy S III Q&A, Help & Troubleshooting] mrjoshzombie:
Just got home. The button remap either would do nothing, or go back to drive link. Need a logcat?
[Galaxy S III Q&A, Help & Troubleshooting] texan_ranger:
South African Galaxy S3 (i9300)

Hi Guys,

I installed the Drivelink from the http://xdaforums.com/showpost.php?p=33176372&postcount=1

on a stock South African Samsung i9300 with ICS on it. The app works but have not had the chance to get another Launcher onto it as to test the other launcher. Unfortunately I cannot mess around with Rooting the phone or putting custom CWM on the phone so I am worried about testing the modified TMServer package.

I have my XAV-701BT plugged into a power supply in room and will be keeping it there for testing sakes until a solution for my SGS2 (i9100) has the working DriveLink app or another app that can work with TMServer. Is there something I can do to test the TMServer and framework on the SGS2 (i9100).

I am willing to add in $20 to the bounty.

Please message me if you have any ideas for me and my SGS2 (i9100). Being South Africa... maybe I will find a phone that has "fallen off the back of a truck" ;).

Once again thank you so much for the effort.

Regards

teXan
[Galaxy S III Q&A, Help & Troubleshooting] pedderd:
I must be doing something wrong here, need assistance.

My mirrorlink head unit will not recognise my S3 (I9300) at all now. I am pretty sure it is the phone that is not putting itself into 'car mode'.

When it works, the phone will start Drive Link automatically on the S3. That doesn't seem to happen anymore, so even before manually starting drive link, I know it isn't going to work. When I was testing things early doors on this, the USB debugging seemed to be causing the problem, but now disabling (and rebooting) makes no difference. I am at a loss.

Here's what I have tried:

S3 with NxtGen ROM and drive link from play store unmodded

S3 with Nxtgen ROM and drive link modded from this thread

The above with TM server installed separately

S3 with CM10 (version 20121107) and the latest TM server

I all instances, drive link works fine on the phone.

Can anyone steer me in the right direction ? Is it worth a Logcat ?

Ta
[Galaxy S III Q&A, Help & Troubleshooting] j0ep0:
The kernel of the installed is playing a role as well, e.g. I see different behaviour when using Siyah kernel and stock Samung. Nxtgen is using galaxsih kernel, which might behave differently. An interesting option would be to flash the stock Samsung kernel (rooted offcourse) on Nxtgen ROM. This one works with XXDLJ4, make a CWM backup before you try pls : http://www.mediafire.com/?zgx6xi9nli3rxno

You can send me a logcat and I'll take a look later on. FYI, I think USB tethering is more important than car mode, because the screen output is being transferred over network using VNC. I think Car mode is used for audio and cutting off access to the home button.