MK1 can't connect to android app

Post by **brentp** » Fri Mar 04, 2016 8:59 pm

The BT LED is tied right into the BT module itself. the BT module controls the flashing pattern - flashing when not paired, solid when paired.

Also - having the ability to select / lock-in and override the BT name is on the list as well, but auto-detection is the way it'll work initially to have a "just works" experience that minimizes user intervention and steps.

Thanks!

murph1379 · Post by **murph1379** » Tue Apr 05, 2016 2:07 am

murph1379 wrote:
brentp wrote:Hi - let's figure this out more.

Are you running the 1.3.7 app or did you sign up for the 1.4.3 beta ?

What tablet make / model are you using?

Do you see this problem on another android device, just as a comparison?
The Racecapture app is version 1.3.13, according to Android.

It's a Samsung Galaxy Tab 3 7", 2013 model running Android 4.4.2.

I don't own another Android device, so I haven't been able to test that.

Hey guys, I don't think I ever got a response... Solostorm connects to the RCP just fine, but the RCP app just won't, regardless of how long it sits and spins at "connecting".

Any ideas? Can I pull some more data for you somehow?

Post by **brentp** » Tue Apr 05, 2016 2:21 am

Hi,

Thanks for following up.

Looks like you're on the 1.3.13 app - could you by chance try the 1.4.4 we have in beta? That would be a good comparison.

https://groups.google.com/forum/#!topic ... rFwAW08CZM

If you're not in the beta already you can opt in here:
https://play.google.com/apps/testing/co ... acecapture

-Brent

murph1379 · Post by **murph1379** » Tue Apr 05, 2016 2:33 am

brentp wrote:Hi,

Thanks for following up.

Looks like you're on the 1.3.13 app - could you by chance try the 1.4.4 we have in beta? That would be a good comparison.

https://groups.google.com/forum/#!topic ... rFwAW08CZM

If you're not in the beta already you can opt in here:
https://play.google.com/apps/testing/co ... acecapture

-Brent

Thanks for the quick response, I'll see how that goes once I get approved for the group.

murph1379 · Post by **murph1379** » Tue Apr 05, 2016 12:02 pm

brentp wrote:Hi,

Thanks for following up.

Looks like you're on the 1.3.13 app - could you by chance try the 1.4.4 we have in beta? That would be a good comparison.

https://groups.google.com/forum/#!topic ... rFwAW08CZM

If you're not in the beta already you can opt in here:
https://play.google.com/apps/testing/co ... acecapture

-Brent

ok, tried the beta, interesting results... I can see it search linvor, which is the RCP, and the RCP bluetooth light turns solid green indicating it's paired, and the little icon that indicates the app is reading data lights up, but the app still keeps moving and eventually gives me an error dialog box "Could not read configuration:"

Post by **brentp** » Tue Apr 05, 2016 2:59 pm

Interesting on the Linvor. The firmware should be renaming the bluetooth module to RaceCapturePro.

What firmware version are you running on MK1?

Could you run from the desktop, do a fresh power up and then view the app log file under the scripting window? This will have some information about it trying to manage the BT module.

Also, can you email your current configuration to us? racecapture@autosportlabs.com.

murph1379 · Post by **murph1379** » Wed Apr 06, 2016 3:56 am

The Racecapture 1.4.2 software on my PC says RaceCapture/Pro v2.8.7 when it connects to the RCP.

The log file only has the following related to bluetooth:

BT: Probing using baud 115200
BT: Provision win
BT: Init complete

I'll send the config file via email.

Thanks for your help!

Post by **brentp** » Wed Apr 06, 2016 6:27 am

Hi Matt,

Thanks. I looked at your config and it seems sane.

A couple of things to try.

* can you test with the 1.4.5 app we just released in google play beta? We have some changes in there that might improve communications with MK1
* as an experiment, can you try a different android device? I understand you're able to communicate with Solostorm, but this is just a diagnostic measure.

Thanks - will watch for an update.

murph1379 · Post by **murph1379** » Fri Apr 08, 2016 12:54 am

Hmm, the app in the app store seems to be stuck on 1.4.4, any idea when 1.4.5 will get there?

murph1379 · Post by **murph1379** » Tue Apr 12, 2016 12:55 pm

BINGO!

1.4.5 finally updated, and now I can connect!

The app is pretty slow, especially in the accelerometer options screen, but it works, it reads, and it writes!

I also love that the back button now goes back to the previous screen.

Post by **brentp** » Tue Apr 12, 2016 4:39 pm

Thanks for the update, and glad it's working for you.

Are you talking about the configuration screen? what device are you using?

The configuration screens will receive updating as we blend in the work from the Kickstarter, and in the process we'll see some performance improvements.

murph1379 · Post by **murph1379** » Wed Apr 13, 2016 2:19 pm

brentp wrote:Thanks for the update, and glad it's working for you.

Are you talking about the configuration screen? what device are you using?

The configuration screens will receive updating as we blend in the work from the Kickstarter, and in the process we'll see some performance improvements.

Yes, most of the configuration screens are very slow.

Im using a samsung galaxy 7" tablet running Android 4.4.2