Torque

Forums

Forums

Guest  

Show or hide header
Welcome Guest, posting in this forum require registration.

Torque » Torque OBD ECU Scanner » Torque Discussion / Ideas » Strange timeout after upgrade to 7.0 (Nougat)

Pages: [1]
Author Topic: Strange timeout after upgrade to 7.0 (Nougat)
CecoM71
Member
Posts: 7
Post Strange timeout after upgrade to 7.0 (Nougat)
on: September 14, 2017 (GMT)

Hi Ian,

In short my configuration is: two Torques Pro: for “Proxy” and “Dashboard”, one external GPS. All was working fine with few exceptions: More details on https://torque-bhp.com/forums/?wpforumaction=viewtopic&t=8657.0

The proxy device was tablet at Android 6.0, and after upgrade to 7.0 there is strange issue occured AFTER ignition OFF.

Before upgrade (proxy at Android 6.0):
– Proxy marked OBDLink MX BT as disconnected (blinking icon) 5 sec after ignition off
– Dashboard marked Proxy as disconnected (blinking icon) 5 sec after ignition off

After Proxy upgraded to Android 7.0:
– Proxy marked OBDLink MX BT as connected for exactly 30 sec and next as disconnected (blinking icon). During 30 second false connection sometimes very big number appeared on the screen and/or in the log files
– Dashboard marked Proxy as disconnected (blinking icon) 5 sec after ignition off

Also tried to power off external GPS:
– blinked as disconnected after 5 sec

I have reproduced the issue with 30 sec false connected status at least 20 times. Everything else is fine, but till now dont have long trips tested.

So, my questions are:
1. Should I worry about these false connected 30 seconds?
2. If yes, what to do about it

Thank you in advance!
piemmm
Administrator
Posts: 6634
Post Re: Strange timeout after upgrade to 7.0 (Nougat)
on: September 14, 2017 (GMT)

Hi!

It’s likely a bug in the bluetooth implementation on that device – what manufacturer is it out of interest?

Unfortunately, it does mean that if it’s a new driver bug, then the manufacturer may require to fix it (it’s nothing Torque can fix as the app simply uses the android bluetooth API itself)

Ultimately though it shouldn’t have much of an effect on the app in terms of connectivity – it will eventually time-out and then a fresh connection will be attempted

(I’ll have a look at the other post hopefully tonight/tomorrow – I’m in the process updating the app to use some of the newer Android APIs which is taking a little bit of time)
CecoM71
Member
Posts: 7
Post Re: Strange timeout after upgrade to 7.0 (Nougat)
on: September 14, 2017 (GMT)

Thank you for the fast response, Ian!

The device is tablet Huawei MediaPad M3 (exact model/build BTV-DL09C100 B303). It was the first 7.0 official (not beta/test) update.

Yes, it seems like a bug in the BT driver, but for me is very strange that the dashboard device (Android 5.1.1) dont have this issue. So the issue is client related, but not server (proxy plugin on the same Android 7.0)
Also, the external GPS device disconnects after same 5 sec, not 30.

Anyway, after that false 30s connection, the device disconnects and then at ignition on connects fine, so seems like there are no another problems, but till now dont have long (50+ km) trips.

I will expect the new (BT API) TorquePro version and will give my feedback. Thank You in advance!
2011_Subaru_Outback
Member
Posts: 1
Post Re: Strange timeout after upgrade to 7.0 (Nougat)
on: September 14, 2018 (GMT)

I’m also having the exact same issue. It always goes from connected/disconnected over and over and so on…it’s also just getting extremely old. I have a Galaxy S8+ with the OS Andriod 8.0.0 “Oreo”. It has to be a bug. IDK it’s the APP.
Pages: [1]
WP-Forum by: Fredrik Fahlstad, Version: 2.4
Page loaded in: 0.018 seconds.

  Follow me on twitter