Its because jellybean has the proper framework with the tmserver installed which is required for drivelink to run
Sent from my SCH-I535 using xda app-developers app
[MOD] Drivelink (Mirrorlink) Full Mirroring
- Thread starter walkeryan
- Start date
Its because jellybean has the proper framework with the tmserver installed which is required for drivelink to run
Sent from my SCH-I535 using xda app-developers app
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.
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.
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.
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.
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.
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.
Second, check this post for new test versions: http://xdaforums.com/showpost.php?p=33733620&postcount=326To 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.
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)
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.
Last edited:
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!
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".
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.
Fun note, anytime you flash a new nightly, you need to reflash the TMserver app.
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
- Samsung Galaxy SIII SCH-I535
- cm-10-20121106-NIGHTLY
- No errors on TMServer appearing in GUI
- Logfile: http://www.mediafire.com/?c2gerwdbfqdyt5h
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.
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.
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!
Just so you know, CM10 audio is not working, JellyWiz, with my 10 minutes of testing, works fully.
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
18j0ep0 and I are currently working to get the mirroring that we were promised working with Drivelink and the Galaxy S III. Currently we have mirroring working successfully but there are a few bugs with the Drivelink app getting wiped and restarted. Here is a list of everything so far:
Full Mirroring without the drive link app resurfacing - Working (random restarts due to memory cleanup in android)
Work with Any Launcher - Currently Nova and Apex work
Reassigning the Home button -
Bypassing the two warning Messages -
Compatibility with Non-touchwiz Roms-
Compatibility with Other Devices -
Dim or turn off Phone screen when mirroring-
Automatically go into launcher (minimizing drivelink) -
Currently the setup we have is working for the following devices:
GSM Galaxy S III
CDMA Galaxy S III (No Data)
If it is working on your device please post, or PM me with the Following:
Carrier
Phone Model
Any Bugs
Rom/Kernel (If custom)
Installation Instructions:
Code:Non-root: Go into Settings and Enable "Install from Unknown sources" Install the APK and run it. Plug into your head unit and pray. This method has worked for some (including myself) and not for others. It will give you the standard Drivelink app and no custom code by us, you need root for that. Rooted users: Download the TMServer zip to your Phone Reboot into recovery and install (Like a ROM) No need to wipe anything, you're just replacing a system APK which is why you need root. Install the Drivelink APK after enabling Unknown sources. Run the Drivelink app and plug your phone into the head unit, After accepting prompts you should see the drive link app.
There are several ways to get to your stock home screen but the easiest for me is to hold your home button down the bring up task manager, Click on another open app, when it opens hit the home button and viola, you're at your home screen. We are trying to find a way to bypass this but drivelink puts the phone into car mode and that disables the home button. Car mode is required to get the audio to route correctly to the head unit.
Here are the Links:
TM Server- Must be flashed in a custom recovery:
TMServer
Drivelink- Remove all versions, allow unknown sources and install this apk:
DriveLink
Both j0ep0 and myself have full time jobs and families so we are working very hard to get this working on our own time. So please be patient. We will get this working fully!
Nice description write up by Olywa123, Thanks
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=sWNpK...eature=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).2Hi All,
After a long battle I managed to get a reply from the Samsung Drive Link development team on some questions I had regarding the issues with this app. Thought I would post here so that everyone can see the responses so far. I have since replied back to this for further clarification on some of the answers.
1. The Drive Link application has a background task which prevents the phone from switching off the screen EVEN when *NOT* using or running Drive Link on the phone. i.e. everyday use of the phone the screen fails to turn off the screen after the pre-set time limit. Killing the Drive Link background task temporarily or uninstalling the app is the only way to fix this. Not good!
- CONFIRMED THIS IS FIXED IN LATEST APP.
2. When running Drive Link hooked up to a MirrorLink compatible head unit the application keeps the screen on the phone. If you are using MirrorLink to display the phone on the car dashboard headunit screen you do NOT want the phone screen to be on for a number of critical reasons. The first being that the phone screen can be easily touched by accident when it is stowed in my arm rest for example. The second is that with the screen on constantly the power consumption and heat generated by the phone is very high! In some cases my phone has locked up and overheated forcing me to hard reset the phone during navigation.
3. The volume setting within the Drive Link application is forgotten about when you next start the application. The default volume (half) is far too low for my car speakers and I have to go through all the menus each time I use drive link to increase the volume. It should remember what volume level you left it on the previous time it was used, not reset it back to the default of half.
- THIS NOW APPEARS TO BE FIXED IN LATEST APP.
4. Functionality needs to be added to allow music to be played from the MAIN headunit whilst MirrorLink is running. It does not make sense to only be able to play music from your phone. I have all my music on a very large USB key permanently attached to my Alpine ICS-X8 head unit, I do not want to have to keep a second copy of all that music on my phone too! The Nokia Drive application allows this for Nokia phones via an API I am told by Alpine support. This allows you to control and play music from the main head unit
which is better than playing it from the phone.
5. Functionality needs to be added for a full application "Mirror Mode" like on Nokia Drive. This lets you mirror the entire phone or ANY application on the car headunit screen. This way it doesn't limit you to specific applications.
6. Need application support for Sat Nav software such as TomTom, CoPilot or Sygic, iGo, etc. Not just the standard Google Navigator which is very limited.
- ANYONE KNOW WHAT THEY MEAN BY PACKAGE NAME EXACTLY?
Hope this is useful. I will post further responses once I receive them if people are interested.
