Open manio opened 8 months ago
latest version is https://github.com/cedricp/ecutweaker/releases/tag/v2.0
Fine ??? If ok Close this issue. Thanks.
I have it on my radar. Please leave it open for a few days, I'll give it a try with newest version ASAP...
Hi,
Unfortunately i cannot test the bluetooth because the version 2.0 which you've mentioned is not working for me - it is constantly crashing at startup (Ecu Tweaker keeps stopping: App info/Close app
) on my Samsung Galaxy A10 phone. Then I've got notification:
Ecu Tweaker is crashing frequently. Put it in deep sleep to keep your phone running smoothly.
So for me the version which is working great is still: EcuTweaker-release-v1.85.apk
you uses a good DB ecu-zip ?? try this https://github.com/cedricp/ddt4all/discussions/845
place zip in InternalStorage root
can't not unzip place as zip
and not uses Release apk uses the EcuTweaker-debug.apk apk release apk is bugued
Yes, this is the database I am using. It's md5 is exactly:
57d9856cf2959b387c408867cb32dfdf ecu.zip
I know how to use it because the earlier version is working fine (with the same ecu.zip)
I will now try the debug version...
Ok ... the debug version started fine!
... but the bluetooth bug is still there. I am clicking on SELECT DEVICE
and nothing happen.
When I change eg for USB, then button is doing action (eg EcuTweaker USB scan
).
i think issue in release mode is because obfucation mode https://github.com/cedricp/ecutweaker/blob/master/EcuTweaker/build.gradle#L46
for bluethoo maybe you need associate device before in android settings>conexions->bluethoot
I had the device paired before app start (and it is working without any problems on older versions). The bug probably started between version 1.85 and 1.9.
@manio try new release https://github.com/cedricp/ecutweaker/releases/tag/v2.1
release or debug normally, both are ok, I tested and the bluethood devices already appear.
Thanks, I've installed this 2.1 release version and unfortunately no change - clicking on "Select device" -> no action.
odd!!
I have the same problem. There was no problem with using the 1.85 version All 1.9, 2.0, 2.1v are not working. I also downloaded a new ECU.ZIP file and tested it, Unfortunately, it doesn't work.
Hello, versions 2.0 also do not work for me (it turns off because it detects an error), 2.1 release and 2.1 debug, both of them start up, but do not detect the bluetoth device. Versions 1.85 and 1.9 work correctly, the others do not detect bluetoth on the phone: Galaxy a53 5g android 14 oneui 6.0 I will add Bluetooth devices, both versions, i.e. 2.1 debug and 2.1 release, are detected but cannot connect
Could you try to launch the app in dbg mode and read logcat (with android studio). Maybe there are some interesting warnings/errors inside it to fix that issue.
I already installed 1.9
If you can, try to make it so that BT connection works in version 2.1 release or debug version
when can we expect the bT problem to be fixed?
As soon as we get more information. A logcat reading could help us localize the bug. We can't buy every android devices and check against it.
HOW to read this logcat? what would I have to do?download the release or debug version?
@cedricp Never done this before, so few questions:
Android Studio
? (I have adb).adb logcat
or adb shell logcat
?I'm used to use logcat inside Android studio, but adb liogcat should work as well. Capture the log while using the app and search for debug/error message.
@cedricp As this log may contain sensitive data I've sent you this via e-mail. It is from application start to clicking on the "Select device" button.
Does BT work for you yet or not?it's about version 2.1 release or debug
@cedricp As this log may contain sensitive data I've sent you this via e-mail. It is from application start to clicking on the "Select device" button.
Did not receive it, sorry
Did not receive it, sorry
Look into the spam folder. Google doesn't like foreign SMTP servers. Besides the attachment may seems like a virus for its anti-spam AI :)
@dwazero Dzięki za info że CI też nie działa - zawsze to jest dodatkowa istotna informacja. Skupiamy sie aktualnie na rozwiązaniu tego problemu. Wiemy od której wersji przestało to działać i autorzy nad tym pracują a ja im próbuję pomóc... więc luzik :)
To czekam na jakieś info :) 1.9 działa poprawnie mimo,że pisze,ze aplikacja jest na starszą wersje androida.Natomiast 2.0 wyłącza się od razu podczas rozruchu jakiś błąd jest a 2.1 zaś nie znajduje BT
Nope :(
Unfortunately either debug or release doesn't allow selecting bluetooth. I was also trying to disable bluetooth and when I press that Select device
button Android is asking me whether to turn it on ... so it is some kind working but no window at all.
Maybe git bisect what happens between last good working and first "bad" one?
This is very strange, the permissions are good etc... I have to note one thing. or add fine location permissions. I have been reading some Android documentation and they apparently use this for wi-fi/bluetooth
does it already know whether version 2.1 release or debug works correctly and finds BT?
does it already know whether version 2.1 release or debug works correctly and finds BT?
Not yet, and I don't know why it doesn't work if all permissions are ok. I don't know where this error comes from
let's see if @cedricp has a solution
Maybe this will help: | Version 1.85 | recent "test" version from 8th march |
---|---|---|
working | not working | |
Maybe this will help:
Version 1.85 recent "test" version from 8th march working not working
yep maybe is a permissions stufs missed need look
I understood from what you wrote that you edited it, but I just wanted to ask a question, do you have a chance to do this?
I understood from what you wrote that you edited it, but I just wanted to ask a question, do you have a chance to do this?
there will certainly be, waiting for it to be resolved, you will be able to use 1.85 https://github.com/cedricp/ddt4all/wiki/Android-port
I don't think version 1.85 is on this list!!!
1.85 manages BT connections well, any newer version not connects to bluetooth device at all.
I had the same problem with version 2.1 on Pixel 7A and Android 14. When I click on select and see paired devices, click on the Konnwei KW902 or OBDLink LX and there is a very quick message "no devices found" and the status window shows bluetooth connection failed.
But now, 1.85 is working. But I am not sure how to enable writing parameters with it. Yes, I have made a donation.....
Hi Cedric, According to the wiki here: https://github.com/cedricp/ddt4all/wiki/Android-port I downloaded and installed the latest version there
(DOWNLOAD LINK V1.9) -> EcuTweaker-1.9.apk
And it seems this particular version has a bug which leads to problem with connecting to bluetooth devices: when clicking onSelect device
button (in bluetooth mode/icon) nothing happens (bluetooth persmission has been granted).When I downgraded to previous version:
EcuTweaker-release-v1.85.apk
then all is working just fine.Maybe this bug was fixed in the mean time (sorry for reporting then), I only want to report this, so you are aware of this problem.
Tested on: Galaxy A10 / Android 11