[navnerd]

Today I installed 3.00039 on my device: The foreground service message on exit is really gone :-(. When switching to the device home screen (and not exiting DMD2!), the trip is not incremented and straight lines are drawn… 🙁 🙁 . Also, switching the screen off during DMD trip recording leads to the same problem.
So, that forces us to use DMD2 as start app and NEVER use another app over it that may switch the screen off (like during a phone call…). The only workaround currently is to record the trip with a third party app (like GPX logger recommended by Severian – it works really great! :-)).
John, can’t you explain the Google reviewer / approver that this will cost Google license fees (American companies are usually very sensitive to this…)? This is a huge limitation of functionality of a navigation / trip logging app!! Google has allowed the wished behavior already in DMD1 (which I sometimes still use :-). Why don’t they allow it in DMD2? –> Explain and ask him. May be the forum participants should send him a protest petition…
😉

Probably the best solution really is providing an apk-download outside the google play store, if that discussion still does not help…

[navnerd]

…may be the tip will result in a new button in [App Section] OBD view “Reset bluetooth OBD connection” or so, that does this automatically…

John, an option?

[navnerd]

Just an Information: The error is gone (3.00032), the problem seems to be fixed! 🙂

Thanks, John!

[navnerd]

Hi Severian,

thanks a lot for the tip with using GPS logger. I have tried it since some weeks now and it is really a great and stable workaround as long as we have the trouble with DMD2 and Google not allowing it to run as a foreground service… 🙁

[navnerd]

Hi RH,

at least to my knowledge there is no other reliable solution except of unplugging in replugging the OBD dongle. But what I found out that often seems to work instead of this, is selecting any arbitrary different bluetooth device for connection in the list of known bluetooth devices in the phone/the OBD settings menue. This will force DMD2 to try to connect to something it does not understand. If you select after this unsuccessful connection attempt the OBD dongle in the list again, it often connects without the need to un- and replug the dongle. Just give it a try.

Hopefully in some time John will find a solution for the DMD code that this becomes unnecessary.

Hope it helps!

[navnerd]

I have tested a BMW R1200 GS ADV model year 2007 (so the old air/oil cooled model). The used OBD2-dongle is OBDLink LX (the green one). The  following data is provided over the BMW’s OBD2 interface of that model year (I have tested that with their own software called “OBDlink”- note other BMW models or model years may not provide any data via the OBD2 interface!):

Vehicle speed, engine speed (RPM), coolant (=oil) temperature, intake air temperature, throttle position, ignition timing advance, battery voltage (just read out from the OBD dongle!). No fuel level is provided by the BMW OBD2 interface, even though the motorcycle’s cockpit itself provides this value.

In DMD2, I have configured and tested the OBD dashboard with the following quantities:

motorcycle speed, coolant temperature, intake air temperature, engine RPM, voltage or throttle position (both works), and fuel level – but this just with the DMD2 functionality of entering an estimated average range and counting that down by the GPS milage you drive. Note the motorcycle’s OBD2 interface does not support a direct read out from the fuel sensor in the fuel tank.

When connecting the OBD dongle via bluetooth to DMD2 at the start of te trip, all works fine and stable. The problem comes if you stop the engine by switching off the ignition. Then, the communication between DMD2 (3.00032, but similar in much older versions, e.g. 2.xy) and the dongle breaks down and cannot be reliably reestablished after restarting the engine. The only thing that helps is pulling the dongle off the plug and reconnect it :-(. I’ll file a bug report for this, since this problem only appears in combination with the OBDlink LX dongle connected to DMD2. If connected with the native OBDlink Android App, the connection is immediately reestablished when the ignition is on and the engine starts again.

• This reply was modified 2 months, 4 weeks ago by navnerd.
• This reply was modified 2 months, 4 weeks ago by navnerd.

[navnerd]

Hi John,

just tried to simulate the route that made the problems with the error message “null description for : n_10000525_52602937” on your simulator. There it works fine…

[navnerd]

Great news regarding background operation; thanks John!

Just found out that 3.00022 still does not allow the setting to access location in the background. When does Google play store allow background location access? Is that a formal approval process there? No idea about it. Let us know…

[navnerd]

Hi John,

just a short partial answer, first readings done still in 3.00021, not todays 22:

– Device: SAMSUNG Galaxy Note 20 Ultra 5G, 12 GB RAM, Android 13, OneUI 5.1

– Free memory reporting in the DMD2 status bar is typically 60-80 %/512 MB

– Today moring I surprisingly had first time the reporting 0%/512 MB. When a long trip was calculated then, I got a very long error message “java.long.OutOfMemoryError: Failed to allocate a 72 byte allocation with 4968736 free bytes and 4852KB until OOM, target footprint 536870912, growth limit 536870912; giving up an allocation because <1% of heap free after GC.” That never happened bevor or after. I was very surprised since I do not run any memory intensive applications in the backround, at least I am not aware of it. The biggest memory usage I ever got reported by OneUI was < 8 GB from the 12 GB installed RAM

– Average location precision is typically 4-6 m, in rare cases 8 m

I’ll do some more testing in version 3.00022 (just installed) and let you know, but it may need some time.

 

[navnerd]

After more refined tests during a trip on a German Autobahn, some additional findings:

1) Unfortunately, also with profile “street fun” the error message “null description for : n_10000525_52602937” may appear: This was the case if, during driving on the Autobahn, DMD2 3.00020 does a recalculation of a longer route to a distant target. I initially startet the trip routing when parking may be 500 m off the Autobahn on a fuel station: From there, using “street fast” didn’t work (distance approx. 185 km), but “street fun” did. When driving the Autobahn even though, the error message starts after some recalculations (in mode street fun)

2) During the automatic recalculations in mode “street fun”, I recognized that DMD often does not guide you away from your current location on the Autobahn, but just picks starting points on other streets that are just close to the Autobahn, but not connected to it. That of course is not very useful unless you prefer to drive over the motorway embankment… 😉

3) When I came closer to the target (during driving on the Autobahn), suddenly “street fast” started to work correct while “street fun” did not (I think that was around 90 km remaining to the target or so).

John, if you can simulate the trip with the different settings anyhow, use these points (all in Germany):

Starting point: MAXI Autohof Rhüden, Am Zainer Berg 2, 38723 Seesen

Target Village: 28879 Grasberg

The setting “street fast” should guide you via the Autobahn A7 and A27, distance is around 185 km. Hope it helps to debug. I guess the problem must really somehow be linked to using motorways (which usually “street fun” does not use). By the way: I always allowed “Maut” and “Autobahnen”, so no prevention settings active.

[Author]

Posts