Develop Bugs

[Q] How Can I Update Bluetooth from 1.9.2 to 2.0 (+)

I have been searching for days trying to resolve this. I have a new cordless landline phone (Uniden) that has a great feature where it will bond to my mobile via Bluetooth ... allowing me to accept and make mobile calls via the cordless landline handset. When I try to bond though - it fails.
I read the Uniden instructions - and they say it requires Bluetooth 2.0 or greater ... and my HTC Touch Pro 2 (Australian Telstra version - initial release version from a couple of years ago) has version 1.9.2 Build 600.
I read that the more recent models of the Touch Pro 2 have Bluetooth 2.0, so I ordered a replacement HTC Touch Pro 2 and it arrived today. Sadly - it has the exact same bluetooth version as my 2 year old version.
Next - I try to flash the ROM (thanks to ENERGY ROMS). It works great - but the bluetooth is still 1.9.2 build 600. So I flash the radio. It works great - but the bluetooth is still 1.9.2 build 600.
Around about now - I realise that I don't have a clue what I am doing and that randomly flashing things hoping for an update is not the way to go. So - can anyone out there please help me to figure out how an HTC Touch Pro 2 can have it's bluetooth updated to 2.0 or beyond?
Many thanks,
Scott

Can I drop my Bluetooth version from 2.1 back to 2.0?
Looking further into this - I have noticed that despite the Bluetooth module reporting version 1.9.2, if I look at Device Information (Hardware) - it reports that I have "Bluetooth version 2.1/2.1 + EDR". This has me thinking that my problem is actually that my Bluetooth version is beyond the spec that my Uniden cordless phone can deal with (Uniden claim that their bluetooth hookup is only compatible with version 2.0). I have heard of others with this problem when trying to hook up to their car bluetooth eg. GM only supports connections with devices running up to Bluetooth version 2.0.
Given the above - what I am now looking for is a way to dumb my bluetooth down to 2.0 from the current 2.1 spec it seems to be running. Has anyone managed to achieve this - perhaps through some sort of registry editing?
Cheers,
Scott

Noone answered this so I'll take a crack at it... 2.1 is backwards compatible, so it'll work. You need to figure out what profile the Uniden requires. Is it handsfree or headset? When you try to bond (pair) there are two things that'll fail it... wrong passcode or device accepting the pair NOT in discovery mode. Since I doubt it's the passcode, it must be the latter. I assume you're turning on the BT on the Uniden and having the TP2 discover it. It'll see it... but it won't pair. Turning on the BT doesn't put the device in discoverable (pairable if you will) mode.

Who else is having bluetooth w/ car headunit issues?

Been having this issue ever since moving to official UVLE1 derived ROMs. I have tried everything except going to the Mr X rom. I would other ROM types( i have actually) but need wi-fi calling as tmobile does not dare enter my house. The issue is that bluetooth conencts to my Kenwood headunit immediately but then disconnects anywhere between 2 minutes and ten minutes later. It will then reconnect 30-60 seconds later but not have any audio unless i hit the play button on the headunit itself. I tried "bluetooth keep alive" app but did not work for me- yes i tried all the options. I actually got it working one night but flashed another rom and cant remember what i did. I've spent hours searching this issue. Anyone else have any luck?

oh some additional information: Problem is not present on any other rom bases including CM9, AOKP, Gingerbread, and skyrocket based ROMS. I have also turned off phone audio to strictly keep it to media with no difference. My Nexus 7 does not have this problem with the head unit.

this might or might not relate to your ROM but it helps my connection with AOKP anyways browse to /system/etc/bluetooth/ open up file audio.conf
look for the "autoconnect=" should be halfway through the page make sure there's no "#" in front and that it says AutoConnect=true
I'm on AOKP and it helps me, sometimes only phone audio connects for mine but ^^ that helped it.

Always seems to connect quickly- just disconnects just as efficiently lol. I will however give this a try and look around the rest of the config file.

yeah i looked around at the config file too and there doesn't seem to be anything else that might trigger a random disconnection. But for me, it always connected quickly, but for some reason with AOKP the media wasn't connecting all the time, and then someone mentioned the "#" in front of the AutoConnect. Hope it helps.

configuration
Teo032 said:
yeah i looked around at the config file too and there doesn't seem to be anything else that might trigger a random disconnection. But for me, it always connected quickly, but for some reason with AOKP the media wasn't connecting all the time, and then someone mentioned the "#" in front of the AutoConnect. Hope it helps.[/QUO
Itookyour advic and then wentonefurther. ItookthewhileBluetooth folder from cm9and copied it. been good for about ten minutes so far. if I continue to have problems I'll copy over the Bluetooth apk. thanksagain.
Click to expand...
Click to collapse

Software Engineer with Bluetooth Car Disconnect Issue
Hi, this is my first post. Think I am in the right place.
I have a Samsung Galaxy S2 (hercules) and a 2010 VW Tiguan. The phone is running ICS, but problem happened on Gingerbread too. The problem happens at random times, but normally seems to happen while on the phone. I have tried a number of things including turning off the PAB service when running Gingerbread (didn't work). I also modified the config files from a tip from another post, but this didn't work either.
Below is a a portion of a log of when this appeared recently. I have not looked into much further just yet, but maybe this will help or maybe someone can explain what they think is happening at the disconnect. Thanks.
Note - The disconnect happened at 12:05:
08-06 11:58:28.267 E/BluetoothPbapVcardManager(20687): write outputstrem failedjava.io.IOException: Abort Received
08-06 11:58:28.267 E/BluetoothPbapVcardManager(20687): write outputstrem failedjava.io.IOException: Abort Received
08-06 11:58:28.267 E/BluetoothPbapVcardManager(20687): write outputstrem failedjava.io.IOException: Abort Received
08-06 11:58:28.287 E/BluetoothPbapObexServer(20687): operation close failedjava.io.IOException: Abort Received
08-06 11:58:29.318 D/Bluetooth HSHFP( 592): AudioStateIntent: 00:0E:9F:7B:96:BA State: 11 PrevState: 10
08-06 11:58:29.428 I/AudioHardwareMSM8660( 175): Routing audio to Bluetooth PCM
08-06 11:58:29.468 D/Bluetooth HSHFP( 592): AudioStateIntent: 00:0E:9F:7B:96:BA State: 12 PrevState: 11
08-06 12:02:05.559 I/HeadsetService(24033): Headset=false; Bluetooth=false
08-06 12:05:21.790 I/AudioHardwareMSM8660( 175): Routing audio to Bluetooth PCM
08-06 12:05:22.060 D/Bluetooth HSHFP( 592): AudioStateIntent: 00:0E:9F:7B:96:BA State: 10 PrevState: 12
08-06 12:07:25.884 D/Bluetooth HSHFP( 592): AudioStateIntent: 00:0E:9F:7B:96:BA State: 11 PrevState: 10
08-06 12:08:05.953 E/Bluetooth HS/HF( 592): BluetoothSocket could not connect
08-06 12:08:07.955 D/Bluetooth HSHFP( 592): AudioStateIntent: 00:0E:9F:7B:96:BA State: 10 PrevState: 11
08-06 12:20:16.896 D/BluetoothAdapterStateMachine( 332): BluetoothOn process message: 2
08-06 12:20:16.926 D/BluetoothAdapterStateMachine( 332): Bluetooth state 12 -> 13

replacing the Bluetooth folder with the one from cm9 fixed my problem completely. you can try bluetoothkeepalive app as it works for some. i have since ditched tmo based roms in lieu of JB and haven't had issues yet. limited use so far since i been pairing my nexus 7 with stereo mostly

TeamHackura said:
replacing the Bluetooth folder with the one from cm9 fixed my problem completely. you can try bluetoothkeepalive app as it works for some. i have since ditched tmo based roms in lieu of JB and haven't had issues yet. limited use so far since i been pairing my nexus 7 with stereo mostly
Click to expand...
Click to collapse
Oh, forgot to mention that the log file is with cm9. It seems to happen less with cm9, but not fixed for me. Will take a look at that app, and continue my mission to fix this.
Thanks for the reply!

I know this is dead but upgraded to note two on T-Mobile and issue is there.
Sent from my Nexus 7 using Tapatalk HD

Bluetooth Issue's with Garmin Vivosmart

Not sure anyone will be able to help with this appreciate its a long shot, i've bought a Garmin Vivosmart fitness tracker and it connects to the phone via Bluetooth, now it all works mint except if i go out of range with the bluetooth the phone and garmin are supposed to reconnect automatically but it doesn't i have to unpair and then repair which isn't the end of the world but is a pain in the backside, looking on the garmin forums lots of people with M8's saying the same so there seems to be an issue with the way HTC - Garmin bluetooth works, some phones seem to work perfect (as in other android phones) so it doesn't seem a generic android-garmin issue, just wondering if anyone has had the same issue with any other bluetooth equipment and managed to find a cure ?
also if anyone know if custom roms mess about with bluetooth and the way it works, tempted to try an AOSP rom or CM to see if the bluetooth works properly but i do like sense so would prefer to stick with what i got, using Insertcoins Sense 7 rom, might go back to official sense 6 and see if that works also...
thanks for any suggestions...

wakers said:
Not sure anyone will be able to help with this appreciate its a long shot, i've bought a Garmin Vivosmart fitness tracker and it connects to the phone via Bluetooth, now it all works mint except if i go out of range with the bluetooth the phone and garmin are supposed to reconnect automatically but it doesn't i have to unpair and then repair which isn't the end of the world but is a pain in the backside, looking on the garmin forums lots of people with M8's saying the same so there seems to be an issue with the way HTC - Garmin bluetooth works, some phones seem to work perfect (as in other android phones) so it doesn't seem a generic android-garmin issue, just wondering if anyone has had the same issue with any other bluetooth equipment and managed to find a cure ?
also if anyone know if custom roms mess about with bluetooth and the way it works, tempted to try an AOSP rom or CM to see if the bluetooth works properly but i do like sense so would prefer to stick with what i got, using Insertcoins Sense 7 rom, might go back to official sense 6 and see if that works also...
thanks for any suggestions...
Click to expand...
Click to collapse
It worked fine for me with KitKat.
Friday evening I upgraded to LolliPop. (Did a clean install, no data restore from backup)
Since then I have the same problem. Once you lose your Bluetooth connection it won't reconnect anymore.
You have to unpair and the repair in order to be connected again. A real pain in the ass, as I use it only for the notifications on the bracelet.

I have had a Vivosmart since the week they came out. I had a lot of the BT issues the first few months (mainly due to their software being released before it was really production ready) but has been fine since. I'm rooted and have ran a few different roms without an issue. Currently I'm using SkyDragon's Sense 7 rom. I haven't had to pair to my phone due to disconnects for at least a couple months. Are you pairing from with-in the Connect app? At one time the pairing was done via the regular android BT devices but they got rid of that and now pair from the app only. So technically your Vivosmart shouldn't ever show up on the list of installed/connected BT devices because it's only paired from the Connect app. I'm sure you've been on the garmin forum but if you haven't or someone else reading this hasn't it's here https://forums.garmin.com/forumdisplay.php?478-vivosmart. I've seen posts over there about m8 users having problems but don't remember reading if anyone was able to get the problem fixed and what they did. It doesn't make sense that it works for some (like me).

Hello,
I have same problem with Garmin Fenix 3. Apparently there is some bug in HTC ONE M8 Android 5.0.1
I am able to connect and connection is quite stable but watch wont reconnect automatically.
Usually it will reconnect once you reset BT on phone and than on watch. But its quite annoying so I am also looking for solutions. Any idea? Ive tried to add watch to trusted device under smart lock but its not working either. I know most Garmin devices worked on previous version of android on HTC ONE M8 but with Lollipop its bugged..

wakers said:
Not sure anyone will be able to help with this appreciate its a long shot, i've bought a Garmin Vivosmart fitness tracker and it connects to the phone via Bluetooth, now it all works mint except if i go out of range with the bluetooth the phone and garmin are supposed to reconnect automatically but it doesn't i have to unpair and then repair which isn't the end of the world but is a pain in the backside, looking on the garmin forums lots of people with M8's saying the same so there seems to be an issue with the way HTC - Garmin bluetooth works, some phones seem to work perfect (as in other android phones) so it doesn't seem a generic android-garmin issue, just wondering if anyone has had the same issue with any other bluetooth equipment and managed to find a cure ?
also if anyone know if custom roms mess about with bluetooth and the way it works, tempted to try an AOSP rom or CM to see if the bluetooth works properly but i do like sense so would prefer to stick with what i got, using Insertcoins Sense 7 rom, might go back to official sense 6 and see if that works also...
thanks for any suggestions...
Click to expand...
Click to collapse
G'day wakers,
I have had exactly the same problem with my m8. I also have only used insertcoin rom which may be part of the problem as I have an identical m8 with stock lollipop (never unlocked or rooted) and it has no problems with the vivosmart or Garmin Fenix BLE connection.
I have since sold my m8 and traded up to an m9, which is still stock, but I'm reluctant to flash custom Rom as the Bluetooth works perfectly... On the other hand, stock roms drive me mental with bloatware and ads.
If you try another Rom I'd be very interested to hear how you go...as it may give me some confidence to unlock my brand new m9.
Cheers.

great_lumbuey said:
G'day wakers,
I have had exactly the same problem with my m8. I also have only used insertcoin rom which may be part of the problem as I have an identical m8 with stock lollipop (never unlocked or rooted) and it has no problems with the vivosmart or Garmin Fenix BLE connection.
I have since sold my m8 and traded up to an m9, which is still stock, but I'm reluctant to flash custom Rom as the Bluetooth works perfectly... On the other hand, stock roms drive me mental with bloatware and ads.
If you try another Rom I'd be very interested to hear how you go...as it may give me some confidence to unlock my brand new m9.
Cheers.
Click to expand...
Click to collapse
Cheers for the reply i might try a few different rom's i presumed that lollipop was the issue from what your saying maybe not then i'll let you know...

I have any M8 stock lollipop and vivosmart. When vivosmart go out of range lose connection. When vivosmart come Back near smartphone, if I want to connect it, i must switch off Bluetooth and switch on manually.
It is not auto.
Can you help me?
Thank you
Inviato dal mio HTC One_M8 utilizzando Tapatalk

I'm experiencing an even worst problem with no pairing at all with my fenix 3 and Garmin Connect with Cyanogenmod 12.1 .
I've done the test with a Samsung SII, Oneplus X and Oneplus One. All pairing fail and all with Cyanogenmod 12.1
It's working well with a Samsung Galaxy S5 ! So if one Cyanogenmod developper is reading this, can you please let us know if this bug is known, or if you can log it, and i can help some troubleshooting as well.

Samyterje said:
I'm experiencing an even worst problem with no pairing at all with my fenix 3 and Garmin Connect with Cyanogenmod 12.1 .
I've done the test with a Samsung SII, Oneplus X and Oneplus One. All pairing fail and all with Cyanogenmod 12.1
It's working well with a Samsung Galaxy S5 ! So if one Cyanogenmod developper is reading this, can you please let us know if this bug is known, or if you can log it, and i can help some troubleshooting as well.
Click to expand...
Click to collapse
Solution found on my side by realizing that one dialog box is not scaled in Garmin Connect and so the "yes" button is not visible in material design. I've understood this by rolling back to Cyanogenmod 11 and see the process.
Workaround is to use a language with shorter words like english. My initial set was in French. So if it can help somebody else with Garmin Connect, use it

Peugeot 208 Full mirroring/Android Auto

Evening all,
I recently acquired a 2016 Peugeot 208 - Much to my dismay however it only supports Apple Carplay and mirrorlink, which is not ideal for me as a Samsung S7 edge user with the advent of Android Auto as the very superior UX.
Whilst mirrorlink works for the odd app I find it all in all useless and so for now I just have my phone mounted below the head unit using the android auto UI on my phone.
Peugeot have iced the cake by telling me that they can't add Android Auto functionality to my head unit in February when they release the new 208s with it, which strikes me as ridiculous given it has a USB interface which means if it can run Apple Carplay it should be able to run Android Auto (if someone can confirm this for me just so I know I'm not being stupid that'd be great as I'm going to go and push them in the garage in February if I dont hear otherwise).
After quite some googling I have come across nothing: Does anyone have a way to completely mirror the screen of my android phone to the head unit of my car, or alternatively make it so Android Auto is miraculously supported by Mirrorlink? The wonders of rocksound appears to have been patched since it immediately recognises I'm trying to access my home screen and tells me it is not supported. For now I'm stuck either with my phone mounted or alternatively plugging an old iPhone in and tethering it, but that's not ideal given I want all my notifications etc, plus Android is just better anyway. I considered ripping out the entire head unit and putting an entire new one in but that's impractical and expensive.
If anyone has any input on this (or a link to something I've missed explaining how to fully mirror it) it would be greatly appreciated.
Thanks!

Try this MirrorLink Samsung How-to

shaggyxda said:
Try this
Click to expand...
Click to collapse
Thanks - that seems to partially work, however I am finding that whenever I interact with anything within for example android auto, or when I try to launch an app, the smeg says that the application is not supported and I have to reselect LG mirrordrive to keep going (the same happens when starting voice control since presumably the launching of the google now overlay that triggers it) - okay whilst Im sitting still but a touch impractical for when Im driving. It's certainly a decent workaround for now, however if there's something I can change that will make it either so it doesnt error with every app being opened or an alternative, that would be much appreciated.
Cheers

I'm so sorry .It was worth trying. This works at Honda, VW, Skoda und SEAT.
https://forum.xda-developers.com/general/connected-car/phone-mirroring-mirrorlink-t3485908
With ROOT permissions, you can try this Samsung
blaz1ng said:
the smeg says that the application is not supported
Click to expand...
Click to collapse
Video How-to Step 3?

blaz1ng said:
Evening all,
I recently acquired a 2016 Peugeot 208 - Much to my dismay however it only supports Apple Carplay and mirrorlink, which is not ideal for me as a Samsung S7 edge user with the advent of Android Auto as the very superior UX.
Whilst mirrorlink works for the odd app I find it all in all useless and so for now I just have my phone mounted below the head unit using the android auto UI on my phone.
Peugeot have iced the cake by telling me that they can't add Android Auto functionality to my head unit in February when they release the new 208s with it, which strikes me as ridiculous given it has a USB interface which means if it can run Apple Carplay it should be able to run Android Auto (if someone can confirm this for me just so I know I'm not being stupid that'd be great as I'm going to go and push them in the garage in February if I dont hear otherwise).
After quite some googling I have come across nothing: Does anyone have a way to completely mirror the screen of my android phone to the head unit of my car, or alternatively make it so Android Auto is miraculously supported by Mirrorlink? The wonders of rocksound appears to have been patched since it immediately recognises I'm trying to access my home screen and tells me it is not supported. For now I'm stuck either with my phone mounted or alternatively plugging an old iPhone in and tethering it, but that's not ideal given I want all my notifications etc, plus Android is just better anyway. I considered ripping out the entire head unit and putting an entire new one in but that's impractical and expensive.
If anyone has any input on this (or a link to something I've missed explaining how to fully mirror it) it would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
I'm in a very similar (worse) situation as you are. I have a Nexus 6P, which doesn't even support MirrorLink... only Android Auto. And my 208 has CarPlay and MirrorLink, but no Android Auto .
Is this true, that the new 2017 models have the Android Auto installed? We should see which SMEG unit and version 2017 models have installed... the 2016 model has a SMEG IV2 unit and software versions starting with 6.x.x.x (my current installed version is 6.1.D.R8).
I found a 6.3.C.R11 update on the internet, but i'm not sure if it includes the Android Auto.

I have a 2017 model and a htc one m8s. The idea behind android auto is fantastic - unfortunately, my phone keeps disconnecting and rendering the google maps redundant after 4 mins driving! I think this is probably my phone's fault, but I am interested to see that others are having trouble....

I have a 2017 rental 208, but it doesn't even launch android auto. It completely fails to detect IT. Using a Nexus 6P

TurboX2 said:
I have a 2017 rental 208, but it doesn't even launch android auto. It completely fails to detect IT. Using a Nexus 6P
Click to expand...
Click to collapse
Could you let us know what SMEG version you are running? Then we can try to update our older 208s to it

Works for me. With the right cable.
My reply comes a little late, but might help others coming here with the same problem...
I got my 2017 Peugot 208 yesterday and one of the first things, I tried, was connecting it to my phone(s). Although the manual only says, it supported Apple Carplay and Android Mirrorlink, I can confirm, that it also supports Android Auto. At first, it didn't work for me. I had to use 6 different USB cables, until I found one, it worked with.
With the first cable, it tried to connect, but before I even had a chance to press OK, the dialog disappeared. The phone showed a android auto communication error 16.
With the next four cables, nothing happend. Neither on the car display, nor on the phone. Manually opening the Android Auto app, didn't help either. It only showed it on the phone.
When I was already about to give up, I tried one last cable, that I brought to the car with me. It was a very short one (about 15 cm) from Aukey. With that cable, it worked like a charm. I could confirm the dialog on the car display and instantly saw Android Auto after that.
Later, I found this article: productforums.google.com/forum/#!msg/android-auto/LV5HsOjkPyI/MlyOoBoPBAAJ. It seems to be a common problem and in that article, you can find a list of cables, that are supposed to work. One good idea seems to be to use the original usb cable, that came with your phone. I tried that today and it worked right away. It's a Samsung cable in my case (connected to a Galaxy S7 running SuperMan Mod). Here is a link to the cable together with a charger: amazon.de/Samsung-ETA-U90EWE-Ladeger%C3%A4t-Netzadapter-DatenKabel-Wei%C3%9F/dp/B01E9G4IHG/ref=as_li_ss_tl?s=ce-de&ie=UTF8&qid=1514492334&sr=1-6&keywords=original+samsung+micro+usb+kabel&linkCode=ll1&tag=yammade-21&linkId=237d676f3199eb607c4e07f09e3fdafb" (Note: I linked to the one with the charger, because this one has good ratings. There are a lot of fake cables on amazon with poor ratings.)
I didn't have a lot of luck with cables from Aukey amazon.de/Ladekabel-Datenkabel-Samsung-Android-Smartphones-Wei%C3%9F/dp/B00TALGDMO/ref=as_li_ss_tl?ie=UTF8&qid=1514491813&sr=8-1-fkmr0&keywords=aukey+usb+kabel+wei%C3%9F+5+st%C3%BCck&linkCode=ll1&tag=yammade-21&linkId=9101b8f12129b7290ece34d35a4f27db". But at least one in four worked, so in case you're desperate, you might give them a try...
Btw, Apple Carplay works too. I used a third party cable and it connected instantly without any problems.
PS: I'm not allowed to post real links, because I'm new in the forums.

Hi everyone,
I'm on the same problem than you, I got a 2016 208 with SMEG+IV2 and sadly just like you, android auto is not supported.
Since i'm French I may have found more infos about why and how in French forums.
So basically since february 2017, 208, and most likely all the new Peugeot cars, have a different head unit NAC (Navigation Audio Connectée; Connected Audio Navigation). Which has a better touch screen quality, firmware, buttons and so on. There is no more useless mirrorlink but Android Auto just like Apple Car.
That was my bad when (2 months ago when I recieved my car) I found out that the car I bought was 6 months too old.
I tried to contact Peugeot's staff, they told me they had no idea about if we could replace the head unit to the newest (physically), but they will "keep an eye on the situation and come back to me" ... still no feedback, and even if it was possible, I think it would be hard to find a dealer that would know how to do it.
Anyway that's what I know. (Tried my best to explain).

Hi,
I have the same situation and my local service doesn't know it either. Does anyone have any news?
Thanks.

NeO_ReVoLuTiOn89 said:
Hi,
I have the same situation and my local service doesn't know it either. Does anyone have any news?
Thanks.
Click to expand...
Click to collapse
In Brazil only Peugeot cars from 2017/2018 have this new Head Unit. I have a 2017/2017 and I can only work with Mirror Link which is fine at the moment. I can work with all apps I want, the only thing is the microphone. I can't seem to make it work on specific applications suck as the search for google maps, or the microphone on the Android Auto App from the phone.
Though if I make a phone call it will work just fine. Strangely enough.

I have 208 2013mod and a oneplus 5t. can my smartphone mirror with my cars display? whick way can I do this? pleaee for your help

Pangadaywalker said:
In Brazil only Peugeot cars from 2017/2018 have this new Head Unit. I have a 2017/2017 and I can only work with Mirror Link which is fine at the moment. I can work with all apps I want, the only thing is the microphone. I can't seem to make it work on specific applications suck as the search for google maps, or the microphone on the Android Auto App from the phone.
Though if I make a phone call it will work just fine. Strangely enough.
Click to expand...
Click to collapse
Hey man, sou do brasil tbm, e tenho um 17/17 208 gt, como vc fez pra usar o mirrorlink? tenho um samsung A7 2017 mas não funcionou irmão, pode me dar uma dica? segue meu whats 47-988394884

I have a 2016 208 and I'm using a carlinkit 4 to get android auto before this my car wouldn't run android auto as far as I can tell it pushes it through the carplay software

Mirrorlink with A3 2017

Hi all,
just a simple question - had anybody succeeded with MirrorLink? And with full phone mirroring (not just with the limited number of apps allowed)? If so, how? My A320FL is updated to the latest available Android 6.0.1, then rooted.
I tried several apps and guides together with two cars (Toyota & Skoda) with no success:
1) Samsung CarMode - the latest available from the market is not the latest, as I found somewhere here, but anyway: it doesn't do anything with Skoda and does show "Your phone is connected through MirrorLink" when connected with Toyota Touch 2, but shows nothing on the display. No option to start it is displayed on Toyota display, Skoda Amundsen says "no compatible app found".
2) LG MirrorDrive - does not even start, but it's shown as compatible app in Skoda. And once, I got the display in portrait mode shown on Skoda display for few seconds.
3) Android Auto - even though it's not accessible in my country (don't know why), I installed the latest version, but it is possible to start this app only on the phone, no car sees it.

check this
https://www.youtube.com/watch?v=F-TNAXxFqDw&t

shaggyxda said:
check this
https://www.youtube.com/watch?v=F-TNAXxFqDw&t
Click to expand...
Click to collapse
Thanks for idea, but it's unfortunately not the right thing - this deals with app flickering when the phone is already connected via MirrorLink. In my case, I don't see anything related to phone display on the car's display. In the meantime, I found out, that the possible problem could be system incompatibility - Samsung supports only MirrorLink 1.1 and Toyota is MirrorLink 1.0 (that's why all the videos online with Toyota are shown with the old S3). I also found out, that Samsung dropped the backward compatibility on Bluetooth, so i.e. old integrated handsfree in 2007 Yaris is now unusable. Shame on Samsung, did those people ever see a car?

Finally, got it working. But not thanks only to myself
The first is thanks to Toyota - there has to be at least HE3934 firmware version loaded (that I found out only when trying to make the mirrorlink running in a new Yaris).
The second is, that in phone, only one mirrorlink app is allowed and it shall be LG MirrorDrive for make it running in Toyota (Samsung CarMode app supports only VW group vehicles - possibly because they provide VW with the whole infotainment and related electronics).
The third and most important is the cable - it has to be a cable that "somehow" supports mirrorlink - Samsung original cable is ok, but I firstly tested it with another "noname" cable, which works only sometimes. Only during longer continuous driving period I found out, that the "impossible to connect" periods happen when the phone and cable shake - maybe some contact is doubled in the original cable.
As last I need to say, that LG MirrorDrive mirrors any running app, but after you run an app, mirroring quits with message, that the function is not available during driving. But it starts the app in background anyway, so when you run LG MirrorDrive on the infotainment again (without disconnecting or anyhow touching the phone), the system opens directly in the app you started before. It's also good to turn off the notifications for LG MirrorDrive, as it shows a message about incompatibility every time it's started.
So I hope that the lines above help also somebody else.

Can a samsung a3 2017 screen mirror? If yes then how please??

... but only working with nougat. Android 8 not working any more. ?

Please send me