System crash investigation. Vivoactive 4

Hello!

So a situation is.

I have an application that are already approved and downloaded several times. It uses BLE. Yesterday I got a report from a user with Vivoactive 4. The application causes a system crash while trying to use BLE. And it doesn't show (IQ!) as I can see sometime, but it causes system restart.

Actually it looks like this

I tried to remove my functions one-by-one but I'm stuck on removing BleDelegate. So. If I remove the delegate or all internal logic, it stops crashing.

My Forerunner945, another Fenix5+, vivoactive3m are working without this problem. Sim works as well.

And another moment. We tried to create a file with the application name under /garmin/apps/logs, but it's always empty. ERA is empty.

And the question is: How to investigate these situations? Are there crash dumps somewhere?

Thanks.

0 jim_m_58 over 5 years ago in reply to Aleks

Yes, I've used more than 7 characteristics with no problem. I forget the exact reason (it may have to do with hashing) and I think it's mentioned in the ble video from the 2019 summit, but how you define UUIDs can impact things.

If you look at the thingy code you'll see

TEMPERATURE_CHARACTERISTIC   = Ble.longToUuid(0xEF6802019B354933L, 0x9B1052FFA9740042L);
PRESSURE_CHARACTERISTIC      = Ble.longToUuid(0xEF6802029B354933L, 0x9B1052FFA9740042L);
HUMIDITY_CHARACTERISTIC      = Ble.longToUuid(0xEF6802039B354933L, 0x9B1052FFA9740042L);
AIR_QUALITY_CHARACTERISTIC   = Ble.longToUuid(0xEF6802049B354933L, 0x9B1052FFA9740042L);

notice the format - most is constant starting with 0xEF68

but then there are 4 digits that are/can be unique

then the rest is constant. This is the most efficient format.

While I didn't do this is the blog post I did for the raspberry pi, my current does use this method.