TuneECU be a fickle *****!!

[gadget_ho]

I am the same as Atomsplitter: Galaxy Tab A8 (SM-X200) running Android 14, latest OBDLink firmware on the reader. I have TuneECU v6.2.05 (which I am not sure is the latest) with the perpetual license. There are apparently a number of compatibility issues introduced with the latest version(s)...

 

[Bedifferent]

I am the same as Atomsplitter: Galaxy Tab A8 (SM-X200) running Android 14, latest OBDLink firmware on the reader. I have TuneECU v6.2.05 (which I am not sure is the latest) with the perpetual license. There are apparently a number of compatibility issues introduced with the latest version(s)...

So are you able to link your TuneECU to your Link and bike.
Here is a partial comment that I read about certain issues and maybe a work around with higher versions. He wrote...

To prove this, I ran a test on one of my Android 14 devices that has never had TuneECU installed on it. I downloaded the latest version from tuneecu.fr & installed it. When I went into Device Settings->Apps->TuneECU the Nearby Devices permission was already set - which makes sense because it's not classed as a "Dangerous Permission" by Android, but on some devices the customised version of Android may automatically disable it as an extra security measure. Anyway, for the purposes of the test I disabled the Nearby Devices permission & then tried to connect to my OBDLink LX Bluetooth device, but TuneECU couldn't see any devices at all. Then I went back & re-enabled the Nearby Devices permission & TuneECU was able to scan for & connect to my OBDLink LX. I tried to attach screenshots & also provide shared links to them from my Google Photos account, but the forum wouldn't play the game...

This could be the solution to many problems installing and using TuneECU on current Android devices. Please try it out.

 

[gadget_ho]

So are you able to link your TuneECU to your Link and bike.
Here is a partial comment that I read about certain issues and maybe a work around with higher versions. He wrote...

To prove this, I ran a test on one of my Android 14 devices that has never had TuneECU installed on it. I downloaded the latest version from tuneecu.fr & installed it. When I went into Device Settings->Apps->TuneECU the Nearby Devices permission was already set - which makes sense because it's not classed as a "Dangerous Permission" by Android, but on some devices the customised version of Android may automatically disable it as an extra security measure. Anyway, for the purposes of the test I disabled the Nearby Devices permission & then tried to connect to my OBDLink LX Bluetooth device, but TuneECU couldn't see any devices at all. Then I went back & re-enabled the Nearby Devices permission & TuneECU was able to scan for & connect to my OBDLink LX. I tried to attach screenshots & also provide shared links to them from my Google Photos account, but the forum wouldn't play the game...

This could be the solution to many problems installing and using TuneECU on current Android devices. Please try it out.

Yes, my setup works fine. Note that I did originally set it up a couple of years ago using an earlier version still.

For sure your OS could be blocking your connection to the OBDLink, so I'd check the settings you're quoting. Have you installed the OBDLink software as well to test? My tablet has TuneECU, OBDLink and VAG DPF for checking the diesel particulate filter on my car. Everything works. I regularly use the OBDLink software it to check error codes on cars as the MX+ gives you the manufacturer-specific databases for free.

One thing that did stuff me around early on was that I had also paired the MX+ to my iPhone and I had the OBDLink software there as well. Problem was, the iPhone would connect almost immediately to the MX+ when it fired up, blocking the Android from connecting. So if I forgot about it and had my iPhone in my pocket when I went to connect to the bike, I'd be dicking around trying to work out why it wouldn't connect...

 

[Bedifferent]

Yes, my setup works fine. Note that I did originally set it up a couple of years ago using an earlier version still.

For sure your OS could be blocking your connection to the OBDLink, so I'd check the settings you're quoting. Have you installed the OBDLink software as well to test? My tablet has TuneECU, OBDLink and VAG DPF for checking the diesel particulate filter on my car. Everything works. I regularly use the OBDLink software it to check error codes on cars as the MX+ gives you the manufacturer-specific databases for free.

One thing that did stuff me around early on was that I had also paired the MX+ to my iPhone and I had the OBDLink software there as well. Problem was, the iPhone would connect almost immediately to the MX+ when it fired up, blocking the Android from connecting. So if I forgot about it and had my iPhone in my pocket when I went to connect to the bike, I'd be dicking around trying to work out why it wouldn't connect...

I would say I covered all those bases. The OBDLink MX+ pairs with my phone and is fully functional with its app. I registered it and also did a firmware update on it as well. I made sure I didn't have any other Bluetooth devices nearby interfering with the connection as well. I double checked all my permissions and rebooted my phone after my updates. I uninstalled and reinstalled TuneECU and reregistered it as well. Everything is up to date. When I clicked connect it just would never find or connect with my OBDLink. I know everything is working because I have no issue with my older phone. I may give it a try again some other time, but for now and not needing to do any other mods I'm good. As long as I was able to reset the service interval and save some time and $$ going to the dealership for just that I'm good. You may find it doesn't work with version 15.