Torque

Forums

Forums

Guest  

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




Torque » Torque OBD ECU Scanner » Torque Discussion / Ideas » New beta update (android 10 & S10 support)

Pages: [1] 2 3 4
Author Topic: New beta update (android 10 & S10 support)
piemmm
Administrator
Posts: 6073
Post New beta update (android 10 & S10 support)
on: November 9, 2019 (GMT)

Hi!

There’s a new beta update out which adds android 9, 10+ support as well as an update trip view screen, S10 support, and other updates to the app (some fixes to plugins, etc)

There are some big changes that have gone in due to the changes in android 9/10 – feedback is appreciated on this to catch anything i might have missed!

cintakc
Member
Posts: 1366
Post Re: New beta update (android 10 & S10 support)
on: November 9, 2019 (GMT)

nothing has changed on the USB connection in beta, it also doesn’t connect

santa2003007
Member
Posts: 20
Post Re: New beta update (android 10 & S10 support)
on: November 9, 2019 (GMT)

Hi.
Many people ask how you added in the program?
https://torque-bhp.com/forums/?wpforumaction=viewtopic&t=633.32

1. A text label. (To be able to establish the names of the entire screen, when the screens)
2. Allow user to change the color of each indicator (round and deletion of the square), a separate indicator name, a separate indicator. (from transparent to colored)
3. To add a horizontal progress bar and vertical progress bar program.
4. Additional formulas for solving user problems. (For example, the formula of comparison: if; then)
5. You can add a horizontal display, with the ability to change size. (Example:
Speed km/h…………………………………..86
Voltage, V……………………………………13.89
Oil temperature, °C……………………………98
6. To do this, you can memorize the settings. (drove 10 miles, turned off the car went to the store, started the car and started again reference the path to continue, not zero as it is now)
7. To make a normal USB adapter connection to the program.
(The USB adapter in my PIC18F25K80 chip from FTDI RS232 Converter.
I can’t connect.
USB adapter tablet sees torque program tries to connect, but I can’t)

piemmm
Administrator
Posts: 6073
Post Re: New beta update (android 10 & S10 support)
on: November 9, 2019 (GMT)

USB should be already working (tested on S10 & Note this evening)

You must start Torque after plugging in the adapter however, so if you start the app, then plugin the adapter, you won’t be able to select it in the USB device list (*edit, I said before by mistake, I meant start Torque after plugging in the adapter and ignoring any popup that asks if you want to start it – start by tapping the icon)

After you start the app after plugging in the adapter (ignoring the popup to start it automatically!), then you should be able to select the USB device to use from the “what USB device should I use” part of the OBD2 adapter settings (because some pepole use more than 1 serial device, this option must be selected)

Then the app should simply use the USB adapter – at this point as well you should simply be able to plugin the adapter at any point and the app should start using it (you must tell Torque what USB device to use first in the settings before it will use the plugged in device – not just set the connection type to USB)

If you’ve done the above and it’s still not working, then I’ll need to know:
– The adapter type (manufacturer, or a link would help)
– The type of phone you’re using
– The type of USB OTG connector device you’re using to connect the adapter (not all OTG devices are the same, or work for all phone manufacturers)
– If a prompt for Torque appears when you plug the adapter in (to know if android recognises the USB device, and (for those that can get this info) the USB PID/VID information)
– If you’ve enabled OTG on your device in the settings (some devices like the OnePlus 5 needs this enabling in the settings first before OTG will work for USB devices)

That’ll help me figure out where any issues with USB support are, though from the tests here it seems to be working ok

cintakc
Member
Posts: 1366
Post Re: New beta update (android 10 & S10 support)
on: November 9, 2019 (GMT)

piemmm, piemmm, I will send you logs in debug mode

P.S. I send you logs in debug mode

cintakc
Member
Posts: 1366
Post Re: New beta update (android 10 & S10 support)
on: November 9, 2019 (GMT)

piemmm, VID_PID

usb-device vendor-id="4292" product-id="60000" -- CP2102 UART Bridge
usb-device vendor-id="4292" product-id="60016" -- CP2105 UART Bridge
usb-device vendor-id="4292" product-id="60017" -- CP2108 UART Bridge
usb-device vendor-id="4292" product-id="60032" -- CP2110 UART Bridge
usb-device vendor-id="1659" product-id="8963" -- Prolific PL2303
usb-device vendor-id="6790" product-id="29987" -- WCH CH340
usb-device vendor-id="6790" product-id="21795" -- WCH CH341A
usb-device vendor-id="17224" product-id="21795" -- WCH CH341     
piemmm
Administrator
Posts: 6073
Post Re: New beta update (android 10 & S10 support)
on: November 9, 2019 (GMT)

Hi! Thanks!

Looking at it, 60033 and 60048 pids also appear to be in use for the cp21x chipset – I’ll need to locate a suitable USB serial library now for this as the current one I use is no longer maintained…. I also need to check to see if the extra PIDs are simple to support or there’s funny stuff like multiple endpoints to consider. Fortunately the library should be drop-in as I abstracted all the comms stuff a long time ago to allow for this kind of thing

I need to get a release out before/on the 11th Nov though, so this might not make it into that release (but it will be in the beta immediately after though, assuming the release goes well)

Adamantos
Member
Posts: 2
Post Re: New beta update (android 10 & S10 support)
on: November 10, 2019 (GMT)

where i can find the BETA version to download/test?

piemmm
Administrator
Posts: 6073
Post Re: New beta update (android 10 & S10 support)
on: November 10, 2019 (GMT)

There should be a new beta available in an hour or so (when google approve it) 1.10.106 that should hopefully fix a couple of issues reported. I’ve added the VID/PIDs as well, though they will (probably) not work until I’ve updated the usb library (existing devices should continue to work though)

You can join the beta by going to: https://play.google.com/apps/testing/org.prowl.torque

(there may also be a method via google play directly as the beta is set to ‘open’)

piemmm
Administrator
Posts: 6073
Post Re: New beta update (android 10 & S10 support)
on: November 10, 2019 (GMT)

I’ll need to add a function to add a ‘total’ data (like total engine runtime) – the groundwork for this is already done with the . TOT() function, so I will try to do this after the current release cycle at the same time as the USB drivers

Capp777
Member
Posts: 2744
Post Re: New beta update (android 10 & S10 support)
on: November 10, 2019 (GMT)

Quote from admin on November 10, 2019
I’ll need to add a function to add a ‘total’ data (like total engine runtime) – the groundwork for this is already done with the . TOT() function, so I will try to do this after the current release cycle at the same time as the USB drivers

End Quote.

Isn’t this possible already with a Torque
based timer?

Mode/Pid: Leave blank.

Equation: tot(1:lookup([1F]::0=0:1~65535=1))

With result stored and number of decimal
places set to zero.

Capp777
Member
Posts: 2744
Post Re: New beta update (android 10 & S10 support)
on: November 10, 2019 (GMT)

If it works as I expect, the totalizer value
will be saved in either the global or
vehicle profile. When you restart Torque
the “timer” should continue where it left
off. You will have to long press the dashboard
gauge to Reset to zero.

This equation simply looks at [1F] and if it is
counting the totalizer will count the value of
“1” in seconds thus becoming a second timer.

Hope this works as expected. Sorry I can’t test
with my OBDI vehicle.

Please remember to set the storage option
while in the pid editor for the custom pid.

cintakc
Member
Posts: 1366
Post Re: New beta update (android 10 & S10 support)
on: November 10, 2019 (GMT)

piemmm,
in v1.10.106 an adapter with converters on CP12xx CH34x is not specified are not defined
FTDI 6001 are detected but also not connected

Pages: [1] 2 3 4
WP-Forum by: Fredrik Fahlstad, Version: 2.4
Page loaded in: 0.269 seconds.

  Follow me on twitter