Hello guys,
I'm currently considering two devices to buy. One is the Galaxy Alpha and the other the Galaxy S4.
I currently own an S3 LTE which just received update 4.4.4.. What brings me here is that not until my S3 received the 4.4.4 (last month) I could not display track info on my car via spotify bt streamming. What I would like to know is if any of you guys have used the Galaxy S4 (4.4.2) + Spotify + BT Car Audio System (Audi MMI, Mercedes Becker/Command, Renault R-Link, etc) and successfully showed up track info on the radio's display?
Thanks in advance :laugh:
Hi Guys, new to this forum so plz be gentle. Been reading this forum for a while now so hoping you guys and girls with expert knowledge can advise me if there is a work around or root i could download. Anyway, heres the problem, have a pioneer avh-x3600dab hu in the motor with the additional pioneer CD-ML100 smartphone interface and been using the samsung galaxy S3 with it with the drivelink app, i know the drivelink app has connection problems but it was okay as all i really wanted to use was the google map app on the hu. Well having updated to the samsung S5 i eagerly awaited the lollipop update but when i connect the S5 it comes back with a connection error even though the s5 says mirrorlink connected. Pioneer say cos the hu is running 1.0 mirrorlink and the s5 uses 1.1 then tough, pioneer cant or wont be updating the mirrorlink. Is there anyway i can get the drivelink app running on the s5 or is there another way to miiror the s5 screen on the hu. Thanks guys in advance:laugh:
The same problem here. Pioneer's support told me there is no way to do work in S5 because of the mirrorlink 1.1... I tried ARU, ARL, and nothing... after 2 months I give up. But my model is avh-x2780bt...
Hello everybody
I am owner of a Samsung Galaxy S4 i9505 5.0.1 lolipop. I also recently baught a car VW which supports Mirrorlink. When i tried to connect my Galaxy with the screen of the car i recieve a message which says ''the deviece is incompatible with the car's mirrorlink. I tried the drive link app but nothing. I would like to ask if there is any solution for this problem. My devise is also rooted.
thank you
I have MTCC-KLD6-V2.97 running factory 5.1.1 and a Samsung Note7 (no not an exploding one) running 6.0.1. I'm having issues with the bluetooth connecting to a Galaxy phone.
When i connect the phone via bluetooth, the bluetooth icon shows at the top of the screen then disappears after 5-10seconds. I can see on the phone, that when it connects initially, it connects for Call Audio (HSP) and Media Audio (A2DP). After 5-10 seconds the phone shows that HSP is off however leaving A2DP on. The Phone shows its still connected via bluetooth. No calls go through to the head unit etc.
Has anyone had this working with an Android 6.0.1 Phone? I was thinking maybe I should try Malaysk's ROM however I'm unsure if its an OS, MCU or Hardware issue. Any help or ideas would be appreciated.
moodie007 said:
I have MTCC-KLD6-V2.97 running factory 5.1.1 and a Samsung Note7 (no not an exploding one) running 6.0.1. I'm having issues with the bluetooth connecting to a Galaxy phone.
When i connect the phone via bluetooth, the bluetooth icon shows at the top of the screen then disappears after 5-10seconds. I can see on the phone, that when it connects initially, it connects for Call Audio (HSP) and Media Audio (A2DP). After 5-10 seconds the phone shows that HSP is off however leaving A2DP on. The Phone shows its still connected via bluetooth. No calls go through to the head unit etc.
Has anyone had this working with an Android 6.0.1 Phone? I was thinking maybe I should try Malaysk's ROM however I'm unsure if its an OS, MCU or Hardware issue. Any help or ideas would be appreciated.
Click to expand...
Click to collapse
as far as i can tell none of the mtcb/c machines will connect to 6.0.1 phones except for music. mine does not either. it does not work on maylay 4.4.4 either. I have not tried his 5.1.1
it does connect to my mtcd fine though
I have the exact same issue. I'm also using a Note7 running 6.0.1. I'm running a Malaysk 5.1.1 ROM on my HU and having the same problem you described. Hoping there is a way to make this work in the future.
sixstrum said:
I have the exact same issue. I'm also using a Note7 running 6.0.1. I'm running a Malaysk 5.1.1 ROM on my HU and having the same problem you described. Hoping there is a way to make this work in the future.
Click to expand...
Click to collapse
Has anybody got android 7 beta? I wonder if Android N works with MTCC OR MTCD units.
I've just connected an Sony Z3 running Android is 6.0.1 with no issues. This would appear to be an issue with the Samsung phones only at this stage.
I have a galaxy, J7 running 6.0.1 and my head unit has the same mtcc running 5.1.1, and I have had no problems so far as yet. My head unit is an eonon g2150f.
I have had 2 note 7 phones and they both worked with my HU with mtcb until i installed the samsung update that turns the battery indicater green.
I also installed the maylaysk 5.1.1 rom with no luck. Called samsung customer service, they were no help.
I believe it has something to do with the update.
mkmall said:
I have had 2 note 7 phones and they both worked with my HU with mtcb until i installed the samsung update that turns the battery indicater green.
I also installed the maylaysk 5.1.1 rom with no luck. Called samsung customer service, they were no help.
I believe it has something to do with the update.
Click to expand...
Click to collapse
Interesting odd how a battery icon update can adversely effect Bluetooth. Noted it was a 400MB update.
moodie007 said:
I've just connected an Sony Z3 running Android is 6.0.1 with no issues. This would appear to be an issue with the Samsung phones only at this stage.
Click to expand...
Click to collapse
Only real difference i can find is Z3 has Bluetooth 4 support and Note7 has 4.2. Bluetooth is meant to be backwards compatible.
Going to do a HCI log of both devices and compare. Samsung looking at old packet traces however the comparison of both may yield better results.
Samsung confirmed a fault however as we all know they axed the product. Consider this thread closed.
moodie007 said:
Only real difference i can find is Z3 has Bluetooth 4 support and Note7 has 4.2. Bluetooth is meant to be backwards compatible.
Going to do a HCI log of both devices and compare. Samsung looking at old packet traces however the comparison of both may yield better results.
Click to expand...
Click to collapse
moodie007 said:
Has anybody got android 7 beta? I wonder if Android N works with MTCC OR MTCD units.
Click to expand...
Click to collapse
i just got a LG V20, which is running Android 7, and it connects to my Joying MTCD just fine
hi
i have an old s5 (rooted lineageOS 17) that i would like to use in my car to do full mirroring on the car display.
mirrorlink doesn't seem to be supported anymore
regardless of mirrorlink rather than androidauto has anyone found a solution?
thanks