|
0.28.0
Sept 22, 2020 8:55:23 GMT
Post by Thirsty on Sept 22, 2020 8:55:23 GMT
Use the following format to report bugsDescription of bug: your bug descriptionAndroid software version: your android version Phone: your android phone modelDongle variant: Firstgen or Nextgen Car: your vehicle brand, model and year App profile: your app user email or username Changelog
v0.28.0
- Added dialog showing whether hood needs to be opened for write operation - Fixed missing long coding descriptions in history - Fixed output test not showing values on some vehicles - Fixed live data showing incorrect values on some cases - Fixed incorrect fault indicator in control unit list when connected to vehicle - Fixed language selection issue where selecting different language would have no effect - Fixed missing live data in engine ECU
|
|
Deleted
Deleted Member
Posts: 0
|
0.28.0
Sept 22, 2020 9:24:25 GMT
Post by Deleted on Sept 22, 2020 9:24:25 GMT
Description of Bug: Android Application crashes after updating photo on IOS Phone. I was playing around with settings in IOS and changed the picture on my car profile. Worked fine on IOS, When I opened up Android I noticed the picture was much larger than any I was able to do with Android (size is limited) but then when I went back to android the picture of a Rose I had taken was replaced with the Red Audi, Then I went back again after stopping the app (as it was just hanging) and the Red Audi was replaced by a stock car picture.
Whilst this was all going on I was not able to use the Android app as it locked up and kept crashing
On the IOS App there are 30 different language options, on Android there are 29 can we match them together please, the missing one appears to be Greece but the description of the languages are different so its not always obvious what is what.
Full backup live data count differences. Did a full backup and checked control unit 03 backup shows 51 rows but when you look at live data there are 54 missing 3 were Analysis 104, 105 and Prevented stop processes (ring memory)
Firmware update today and on Android worked fine (Failed on IOS) and then I ran full scan. Old issue on Control unit 09 that it shows 101% complete Today new feature Control unit A9 now shows complete at 96%
Still showing Control Unit 56 when looking offline - please remove it.
Another difference between Android and IOS, On IOS the Reset function is shown when offline but on Android it is only shown when connected to the car.
Did a back to back full backup on Android and IOS And was pleased that all the numbers are the same (which was not the case last time). However I have one issue which I saw the last time i did a comparison. Under Control Unit 17 (but saw it yesterday on 03) Under Advanced ID the Android extract shows Diagnostic mode as OBD-diagnostic mode but under IOS it shows VW - diagnostic mode, doing a check of the Advanced ID on screen and both show VW - diagnostic mode and no changes were made just straight backup.
Android software version: 9 Phone: Sony Xperia Dongle variant: Nextgen Car: your vehicle Seat Leon Cupra 280 App profile: username - cupra280.co.uk
|
|
ViĆ
Full Member
Posts: 185
|
0.28.0
Sept 28, 2020 14:44:46 GMT
Post by ViĆ on Sept 28, 2020 14:44:46 GMT
Description of bug: Cant connect to Firstgen after dongle update in 0.27.0 Android software version: 10 Phone: Oneplus 7 Pro Dongle variant: Firstgen Car: your vehicle brand, model and year App profile: Z'
Already in contact with support about this matter since 0.27.0. Support thought 0.28.0 would solve it but it didnt, just figured if there is more people with same issue or just me.
Few days after updating to 0.27.0 I got a dongle update for my firstgen and it updated without a fuss. However I could no longer connect to the dongle. Dongle is visible in Bluetooth list and flashes green when trying to connect but timesout after 10-15 seconds of trying to connect.
Done all the basic troubleshooting which consists of cache removal, Uninstall/Reinstall, Remove saved device, Different Phone/tablet, WiFi/Mobile data etc....... But no luck, waiting on an answer from support currently.
**UPDATE** 2020-10-06 **UPDATE** Support sent me a "new" dongle update on Monday 5th October. Dont know exactly what the update did. At first the dongle update kept looping the update for 3 times, after that I could finally connect to my First Gen dongle again. Been using it 10 hours roughly after the dongle update, disconnecting and reconnecting several times aswell to check if it would malfunction again., but it has been working reliable so far. Sure it took them a while to find a solution that would work, but overall I am happy.
|
|
Deleted
Deleted Member
Posts: 0
|
0.28.0
Sept 28, 2020 15:02:31 GMT
Post by Deleted on Sept 28, 2020 15:02:31 GMT
Just to add to the above I have Android 9 and so far no issues but I have seen two other users with Android 7.1.1 not being able to connect and one user then used another phone with Android 6 and it worked fine. Have you tried using an older version of OBD11 (26.1) to see if its the same issue.
Update - Just had confirmation from Support via in app help function that they are aware of this issue and are looking into it.
Something i have been seeing a lot over the last few days when you are offline and go look at various items (Live Data, Adaptations, Long coding) either gives me not availiable offline or blank screen. Other times it works fine. I am also having to force stop the app to be able to see control units as the car details are lost and you have to force stop to get it to work again.
|
|
ViĆ
Full Member
Posts: 185
|
0.28.0
Oct 3, 2020 19:32:48 GMT
Post by ViĆ on Oct 3, 2020 19:32:48 GMT
^^ I hadn't tried your suggestion before. I gave it a go an hour ago, and there was no difference. my devices are OnePlus 7Pro with Android 10 and my Xiaomi Mi Pad 4 with Android 8.1.0 OBDeleven app tries to connect to the dongle, the led on the dongle shines red and flashes green but 10-15 seconds later I get "Something went wrong", "Unable to connect" or lately it spins with the connecting thing and goes back to "home page" with no error displayed.
|
|
Deleted
Deleted Member
Posts: 0
|
0.28.0
Oct 3, 2020 21:46:56 GMT
via mobile
Post by Deleted on Oct 3, 2020 21:46:56 GMT
i will give my white donglrs a go in the morni ng
|
|
Deleted
Deleted Member
Posts: 0
|
0.28.0
Oct 4, 2020 16:36:21 GMT
Post by Deleted on Oct 4, 2020 16:36:21 GMT
Well just tried it again, With the Next Gen once again I had to do an update on my Android phone and the same for the Original White dongle.
Works fine, if I log off and back on no update still all works ok but based on the weekend if I log on again on Monday it will require and update but it will again still work for the day.
Same applies to IOS.
|
|
ViĆ
Full Member
Posts: 185
|
0.28.0
Oct 6, 2020 19:59:31 GMT
Post by ViĆ on Oct 6, 2020 19:59:31 GMT
Description of bug: Cant connect to Firstgen after dongle update in 0.27.0 Android software version: 10 Phone: Oneplus 7 Pro Dongle variant: Firstgen Car: your vehicle brand, model and year App profile: Z' Already in contact with support about this matter since 0.27.0. Support thought 0.28.0 would solve it but it didnt, just figured if there is more people with same issue or just me.
Few days after updating to 0.27.0 I got a dongle update for my firstgen and it updated without a fuss. However I could no longer connect to the dongle. Dongle is visible in Bluetooth list and flashes green when trying to connect but timesout after 10-15 seconds of trying to connect.
Done all the basic troubleshooting which consists of cache removal, Uninstall/Reinstall, Remove saved device, Different Phone/tablet, WiFi/Mobile data etc....... But no luck, waiting on an answer from support currently.**UPDATE** 2020-10-06 **UPDATE** Support sent me a "new" dongle update on Monday 5th October. Dont know exactly what the update did. At first the dongle update kept looping the update for 3 times, after that I could finally connect to my First Gen dongle again. Been using it 10 hours roughly after the dongle update, disconnecting and reconnecting several times aswell to check if it would malfunction again., but it has been working reliable so far. Sure it took them a while to find a solution that would work, but overall I am happy. Just a new update for thoose who are curious
|
|
Deleted
Deleted Member
Posts: 0
|
0.28.0
Oct 7, 2020 15:59:08 GMT
Post by Deleted on Oct 7, 2020 15:59:08 GMT
Description of bug: Logged on to Old Dongle and no update, Logged on to New Dongle and no Update Logged on with IOS Phone and got an update Logged on with Android and New dongle and got an update
Today got an extra free credit - thank you
Android software version: 9 Phone: Sony Xperia Dongle variant: Nextgen Car: your vehicle Seat Leon Cupra 280 App profile: username - cupra280.co.uk
|
|
|
Post by octo|opto|koppler on Oct 11, 2020 14:59:00 GMT
Description of bug: no long coding in control unit 09 Android software version: 10 Phone: Huawei Mate 20 Dongle variant: Firstgen Car: Skoda Fabia Estate, 1.0 l, 55 kW, MY2019 App profile: octo|opto|koppler
|
|
Deleted
Deleted Member
Posts: 0
|
0.28.0
Oct 24, 2020 8:44:47 GMT
Post by Deleted on Oct 24, 2020 8:44:47 GMT
Description of bug: how many different Languages does the app support. In Android under Language Application there are a total of 29 In Android under Language Database there are a total of 22 On the IOS App you only have one Language available (which is a bug) but they have 30 Languages. Could we please make sure all apps and settings support the same number, Description
The IOS App has different naming convention for example in IOS its Dansk in Android its Danish, IOS has Cpnckn but Android Serbian Within Android not only are database and app numbers different but the names of countries are also different for example we have Dansk in Application and Danish in database Android software version: 9 Phone: Sony Xperia Dongle variant: Nextgen Car: your vehicle Seat Leon Cupra 280 App profile: username - cupra280.co.uk
|
|
arnau
New Member
Posts: 15
|
0.28.0
Oct 26, 2020 10:18:29 GMT
Post by arnau on Oct 26, 2020 10:18:29 GMT
Description of bug: Some control units appear duplicated (Engine 01 , Driver Asistance A5, Dashboard 17) Android software version: MIUI 12.05 (Android 10) Phone: Xiaomi Mi9t Dongle variant: Nextgen Car: Audi A4 Avant Quattro 2016 (B9) App profile: (I only have email as username, I can send by private)
|
|
Deleted
Deleted Member
Posts: 0
|
0.28.0
Oct 26, 2020 10:24:27 GMT
Post by Deleted on Oct 26, 2020 10:24:27 GMT
just to add i have seen the same issue but its not on all cars and i have checked on IOS and dont get duplicates so its an Android only bug Please note in this case the car was a 2011 model.
|
|
|
0.28.0
Oct 27, 2020 19:10:02 GMT
Post by jay808 on Oct 27, 2020 19:10:02 GMT
Description of bug: Cannot install App anymore after factory reset of my tablet "Fehler beim Installieren"...
Log: I/PackageManager( 534): Dexopt done on: com.voltasit.obdeleven W/PackageManager( 534): Package couldn't be installed in /data/app/com.voltasit.obdeleven-1 W/PackageManager( 534): com.android.server.pm.PackageManagerException: scanPackageLI W/PackageManager( 534): at com.android.server.pm.PackageManagerService.scanPackageDirtyLI(PackageManagerService.java:6309) W/PackageManager( 534): at com.android.server.pm.PackageManagerService.scanPackageLI(PackageManagerService.java:5615) W/PackageManager( 534): at com.android.server.pm.PackageManagerService.installNewPackageLI(PackageManagerService.java:10744) W/PackageManager( 534): at com.android.server.pm.PackageManagerService.installPackageLI(PackageManagerService.java:11299) W/PackageManager( 534): at com.android.server.pm.PackageManagerService.access$2800(PackageManagerService.java:243) W/PackageManager( 534): at com.android.server.pm.PackageManagerService$6.run(PackageManagerService.java:9193) W/PackageManager( 534): at android.os.Handler.handleCallback(Handler.java:815) W/PackageManager( 534): at android.os.Handler.dispatchMessage(Handler.java:104) W/PackageManager( 534): at android.os.Looper.loop(Looper.java:194) W/PackageManager( 534): at android.os.HandlerThread.run(HandlerThread.java:61) W/PackageManager( 534): at com.android.server.ServiceThread.run(ServiceThread.java:46) I/PackageManager( 534): Installation done for package: com.android.vending I/PackageManager( 534): mcs_unbind I/PackageManager( 534): calling disconnectService() I/PackageManager( 534): mcs_check I/PackageManager( 534): mcs_check(false, 1) V/ActivityManager( 534): Broadcast: Intent { act=com.android.vending.INTENT_PACKAGE_INSTALL_COMMIT.2089917755 flg=0x10 (has extras) } ordered=false userid=0 callerApp=null E/Finsky (16436): [1] xpd.onReceive(16): Error -504 while installing com.voltasit.obdeleven: INSTALL_FAILED_DEXOPT: Package couldn't be installed in /data/app/com.voltasit.obdeleven-1: scanPackageLI W/System.err( 534): java.lang.SecurityException: Caller has no access to session 2089917755 W/System.err( 534): at com.android.server.pm.PackageInstallerService.abandonSession(PackageInstallerService.java:636) W/System.err( 534): at android.content.pm.IPackageInstaller$Stub.onTransact(IPackageInstaller.java:97) W/System.err( 534): at android.os.Binder.execTransact(Binder.java:451) W/Finsky (16436): [9675] xph.C(5): Unexpected error abandoning session=2089917755. exception=java.lang.SecurityException: Caller has no access to session 2089917755 W/Finsky (16436): [1] qiz.d(4): IT: Install failure of com.voltasit.obdeleven (isid: EYXgXim0Qr-c_nQqgzzvEg): -504, Exception: n/a D/SQLiteDatabase(16436): beginTransaction() D/SQLiteDatabase(16436): endTransaction() W/Finsky (16436): [1] qjc.k(1): IT: Cleanup running installation of com.voltasit.obdeleven (..split.config.armeabi_v7a) I/Finsky (16436): [9620] mmb.d(1): getDownloads() I/Finsky (16436): [9620] qgu.run(-1): IT: Running resource fetching of ..split.config.armeabi_v7a canceled. I/Finsky (16436): [1] qgg.S(1): Installer: stopping tracking of task: com.voltasit.obdeleven W/Finsky (16436): [9864] mcc.run(5): Exception while deleting file:///data/data/com.android.vending/files/phonesky-download-service/103/ec06092c-ff40-4012-bfc6-11bbce0e756c: java.lang.IllegalArgumentException: Unknown URL file:///data/data/com.android.vending/files/phonesky-download-service/103/ec06092c-ff40-4012-bfc6-11bbce0e756c I/Finsky (16436): [1] qgg.I(12): Installer: Notifying status update. package=com.voltasit.obdeleven, status=INSTALL_ERROR
Android software version: 5.0.1 Phone: Tablet Telekom Puls (Alcatel /TCT 8072) Dongle variant: white / original Car: VW Tiguan App profile: (my email-adress)
After several E-Mails to support with all the Log-Files and Screenshots, they wrote, i should buy a new phone (not funny). They denied to simply send me the old app Version which worked fine. Any tips?
|
|
tomas
New Member
Posts: 33
|
0.28.0
Oct 28, 2020 18:36:01 GMT
Post by tomas on Oct 28, 2020 18:36:01 GMT
I have already written to obdeleven asking for help. I am waiting for an update with a corrected error. I have identical problem. I have duplicate control unit -> central electric 09 and dashboard 17. I have not control unit airbag, radio, steering wheel. I have already written to obdeleven asking for help. I am waiting for an update with a corrected error
I have Skoda fabia m.y. 2011 phone: samsung j6 software: Android One OBD eleven pro nextGen (black)
|
|
Deleted
Deleted Member
Posts: 0
|
0.28.0
Oct 28, 2020 22:01:57 GMT
Post by Deleted on Oct 28, 2020 22:01:57 GMT
description of bug tomas this is a bug they keep releasing into production and then over time they fix it. This version of the bug only seems to impact older cars, my 2014 model is fine and I have a few 2012 cars with no issue. However with the exception of one car all cars that are 2011 show this feature oddly older cars don't in my garage anyway.
OBDeleven can you please add the Polo and Passat to the Audi Bonnet open feature for my2021 cars Android software version: 9 Phone: Sony Xperia Dongle variant: Nextgen Car: your vehicle Seat Leon Cupra 280 App profile: username - cupra280.co.uk
|
|
tomas
New Member
Posts: 33
|
0.28.0
Nov 3, 2020 19:54:41 GMT
Post by tomas on Nov 3, 2020 19:54:41 GMT
Thank U to answer. Now is upgrate to version 0.30.0 and I must connect with my car.
|
|