Unfortunately, Shadow Dash MS has stopped.

[LT401Vette]

KPH should be working. Are you using the GPS for speedometer or an MS3 speedometer?

[arjay]

The 10Hz GPS is what I'm using.

On another note, I just went for a quick ride up to the store so I figured, now that ShadowDash appears to be working, I'll take it with me and do some more testing. Unfortunately, Shadow Dash MS has stopped. I tried to start it 4 times and each time got the same thing I'm trying to find the debug file so that I can attach it as it may help.

[arjay]

Here it is....

[arjay]

Not to bug ya but I installed Shadow Dash on my phone as well a little while back and I tried it today and got the same crash during startup. Just an FYI

[arjay]

Good to see all the post are being abandoned as opposed to getting down and fixing the problem.

[LT401Vette]

Don't worry, the fixes are in the works.
Remember I generally help 20-50 people a day before a line of code is written, that takes time in itself. At times I am deeply involved in other projects and an simply can't drop that to respond to an issue effecting 1 person. There are only so many hours in a day

[LT401Vette]

Are you using shadow dash just for GPS, not using an MS with it?

[Zaphod]

Hi Phil,

I try to get my MS3pro to work (pre1.3.1 Beta 2) over my bluetooth dongle. (JY-MCU cheapo one)
It works fine with my Win7 PC and Tuner Studio - but when I try to open Shadowdash it crashes at connecting with the nice "Shadow Dash has stopped"
Latest Shadow dash.

[LT401Vette]

Zaphod,
Is it during connect, or does it crash just opening it?
Your appDebug.txt might help.

Also, a new Shadow Dash just went out yesterday (1.25), is that the one you are on?

Can you try to connect with Shadow Logger? It is much more basic to rule out some things and has an option to capture a comm debug log in preferences.
http://tunerstudio.com/index.php/downloads

[Zaphod]

Shadow logger also crashes with the same message

Here is the appdebug.txt

appDebug.txt

[LT401Vette]

This is a strange set of lines:

Code: Select all

20.05.14 18:47:57 :Debug: Got BT Socket
20.05.14 18:47:57 :Debug: About to connect Socket
20.05.14 18:48:02 :Debug: Socket connected
INFO 10.365,75488(s): Connected to :null

The null after it connected. It looks like it lost it. I could probably put in protection against the null device right after connecting. However, that shouldn't be.

What kind of device is it?
Are you able to connect to any other BT Devices?

How about Blue Term, can you connect to it from that and get a response to an S

[Zaphod]

The device is this little bluetooth board:



The device is called MS3pro in my bluetooth setting - it is called null under paired devices when I try to connect Shadow dash...
I can connect to it just fine on my Windows 7 PC.

It's called correctly in Blueterm and when I type S - I get the "MS3 pre 1.4 alpha 1...etc."

Sven

[LT401Vette]

By device I meant the type of tablet or phone.

[Zaphod]

Oh sorry, it's a Galaxy Tab2 with a custom ROM [4.4.2][P31XX]AOKP - (which might be the issue...?)

But as I said - it connects just fine in the BT settings of the Tab2 and works in Blueterm

Edit: WTF. I just tried again and it acknowledges the BT as MS3pro and connects - I removed the pairing in Shadowdash before and re-connected... Very strange...!

[LT401Vette]

Did you originally pair and type the pairing code in SD?

I have seen some devices where if you pair from in SD, the connection doesn't work until you swipe close SD and start it fresh. I'm not sure why this happens on some devices and not on others.