Android 6 Master Control Panel Bonded DFU + Android 6 gets stuck in a loop

RE: Android 6 Master Control Panel Bonded DFU + Android 6 gets stuck in a loop

Clem Taylor — Thu, 19 Nov 2015 07:50:32 GMT

That apk fixes the problem in the nRF Toolbox. I was able to upload firmware from a non-bonded device without a crash.

While on the topic of crashing :-) I get a number of different nRF Master Control panel crashes as well:

Something that looks like the bug above:

11-10 19:06:56.707 18218 21775 E AndroidRuntime: FATAL EXCEPTION: IntentService[DfuBaseService]
11-10 19:06:56.707 18218 21775 E AndroidRuntime: Process: no.nordicsemi.android.mcp, PID: 18218
11-10 19:06:56.707 18218 21775 E AndroidRuntime: java.lang.NullPointerException: Attempt to get length of null array
11-10 19:06:56.707 18218 21775 E AndroidRuntime:        at android.bluetooth.BluetoothGattCharacteristic.getIntValue(BluetoothGattCharacteristic.java:445)
11-10 19:06:56.707 18218 21775 E AndroidRuntime:        at no.nordicsemi.android.dfu.DfuBaseService.readVersion(DfuBaseService.java:2187)
11-10 19:06:56.707 18218 21775 E AndroidRuntime:        at no.nordicsemi.android.dfu.DfuBaseService.onHandleIntent(DfuBaseService.java:1339)
11-10 19:06:56.707 18218 21775 E AndroidRuntime:        at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:66)
11-10 19:06:56.707 18218 21775 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:102)
11-10 19:06:56.707 18218 21775 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:148)
11-10 19:06:56.707 18218 21775 E AndroidRuntime:        at android.os.HandlerThread.run(HandlerThread.java:61)

Along with:

11-13 16:59:20.338  6283  6283 E AndroidRuntime: FATAL EXCEPTION: main
11-13 16:59:20.338  6283  6283 E AndroidRuntime: Process: no.nordicsemi.android.mcp, PID: 6283
11-13 16:59:20.338  6283  6283 E AndroidRuntime: java.lang.IllegalStateException: Can not perform this action after onSaveInstanceState
11-13 16:59:20.338  6283  6283 E AndroidRuntime:        at android.support.v4.app.FragmentManagerImpl.checkStateLoss(FragmentManager.java:1377)
11-13 16:59:20.338  6283  6283 E AndroidRuntime:        at android.support.v4.app.FragmentManagerImpl.enqueueAction(FragmentManager.java:1395)
11-13 16:59:20.338  6283  6283 E AndroidRuntime:        at android.support.v4.app.BackStackRecord.commitInternal(BackStackRecord.java:637)
11-13 16:59:20.338  6283  6283 E AndroidRuntime:        at android.support.v4.app.BackStackRecord.commit(BackStackRecord.java:616)
11-13 16:59:20.338  6283  6283 E AndroidRuntime:        at no.nordicsemi.android.mcp.scanner.connection.ConnectedDevicesActivity.onItemSelected(ConnectedDevicesActivity.java:161)
11-13 16:59:20.338  6283  6283 E AndroidRuntime:        at android.widget.AdapterView.fireOnSelected(AdapterView.java:931)
11-13 16:59:20.338  6283  6283 E AndroidRuntime:        at android.widget.AdapterView.dispatchOnItemSelected(AdapterView.java:920)
11-13 16:59:20.338  6283  6283 E AndroidRuntime:        at android.widget.AdapterView.-wrap1(AdapterView.java)
11-13 16:59:20.338  6283  6283 E AndroidRuntime:        at android.widget.AdapterView$SelectionNotifier.run(AdapterView.java:890)
11-13 16:59:20.338  6283  6283 E AndroidRuntime:        at android.os.Handler.handleCallback(Handler.java:739)
11-13 16:59:20.338  6283  6283 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:95)
11-13 16:59:20.338  6283  6283 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:148)
11-13 16:59:20.338  6283  6283 E AndroidRuntime:        at android.app.ActivityThread.main(ActivityThread.java:5417)
11-13 16:59:20.338  6283  6283 E AndroidRuntime:        at java.lang.reflect.Method.invoke(Native Method)
11-13 16:59:20.338  6283  6283 E AndroidRuntime:        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
11-13 16:59:20.338  6283  6283 E AndroidRuntime:        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)

No clue what I was doing when that crash occurred.

RE: Android 6 Master Control Panel Bonded DFU + Android 6 gets stuck in a loop

Aleksander Nowakowski — Wed, 18 Nov 2015 13:05:47 GMT

One more thing. Since some time the DFU lib waits 1 second before it start connecting to the target. Also it waits after switching from app to bootloader mode. Maybe that's why it does not end up in a loop, like MCP does (the current version of MCP was release some time ago and may not have this delay implemented, I don't remember).

RE: Android 6 Master Control Panel Bonded DFU + Android 6 gets stuck in a loop

Aleksander Nowakowski — Wed, 18 Nov 2015 13:02:41 GMT

Hi, I've managed to fix the bug now. The app should be on Google Play soon, it's already available on github github.com/.../releases. I've published new version of the DFU library on both GitHub: github.com/.../Android-DFU-Library and jcenter. New version is 0.6.1. Could you please test it? The new version of nRF Master Control Panel will also have the newest version of this lib when released (couple of weeks, I'm doing my best).

RE: Android 6 Master Control Panel Bonded DFU + Android 6 gets stuck in a loop

Aleksander Nowakowski — Wed, 18 Nov 2015 10:46:43 GMT

Hi, I managed to crashed the nRF Toolbox the way you described. I'll fix the app asap.

RE: Android 6 Master Control Panel Bonded DFU + Android 6 gets stuck in a loop

Clem Taylor — Wed, 18 Nov 2015 07:21:16 GMT

Yeah my DFU stuff requires bonding. It dies after entering the pin. The bond is created, so it tends to work the second time I try or if the bond was already present.

Yes, my device is in developer mode and no I do not get anything other then a "Ok" in the crash dialog. There is absolutely no way I would submit a full android bug report form my personal device, those bug reports leak way to much personal data. Sadly, I don't have any Android test only devices.

RE: Android 6 Master Control Panel Bonded DFU + Android 6 gets stuck in a loop

Aleksander Nowakowski — Wed, 18 Nov 2015 07:16:49 GMT

BTW, if you tap Build Version in Android settings 7 times you'll enable the Developer Settings (also in Android settings). There is a chance that you'll then have a Report button next to OK. But the log you posted is enough, I'd get the same from Google play console.

RE: Android 6 Master Control Panel Bonded DFU + Android 6 gets stuck in a loop

Aleksander Nowakowski — Wed, 18 Nov 2015 07:13:15 GMT

Thanks! You're saying this happen when your device needs bonding with pin. And also I understand it triggers bonding when the service wants to read the DFU Version characteristic.

RE: Android 6 Master Control Panel Bonded DFU + Android 6 gets stuck in a loop

Clem Taylor — Tue, 17 Nov 2015 23:15:29 GMT

FYI, the dialog box just say "Ok", there is no option to report the bug. The above was pulled from an Android bug report.

RE: Android 6 Master Control Panel Bonded DFU + Android 6 gets stuck in a loop

Clem Taylor — Tue, 17 Nov 2015 23:10:12 GMT

This should be the most recent crash:

11-17 17:41:52.737 28845 28862 I BluetoothBondStateMachine: bondStateChangeCallback: Status: 0 Address: E0:4B:75:64:34:DE newState: 2
11-17 17:41:52.737 28845 28878 I bt_bta_dm: bta_dm_gatt_disc_result service_id_uuid_len=2   
11-17 17:41:52.738 28845 28878 I bt_bta_dm: bta_dm_gatt_disc_result service_id_uuid_len=2
11-17 17:41:52.738 28845 28878 I bt_bta_dm: bta_dm_gatt_disc_result service_id_uuid_len=16
11-17 17:41:52.738 28845 28878 I bt_bta_dm: bta_dm_gatt_disc_result service_id_uuid_len=2
11-17 17:41:52.738 28845 28869 D BluetoothAdapterProperties: Adding bonded device:E0:4B:75:64:34:DE
11-17 17:41:52.738 28845 28878 I bt_bta_dm: bta_dm_gatt_disc_result service_id_uuid_len=2
11-17 17:41:52.738 28845 28878 I bt_bta_dm: bta_dm_gatt_disc_result service_id_uuid_len=16
11-17 17:41:52.739 28845 28869 I BluetoothBondStateMachine: Bond State Change Intent:E0:4B:75:64:34:DE OldState: 11 NewState: 12
11-17 17:41:52.739 28845 28869 I BluetoothBondStateMachine: StableState(): Entering Off State
11-17 17:41:52.740 24976 29192 E AndroidRuntime: FATAL EXCEPTION: IntentService[DfuBaseService]
11-17 17:41:52.740 24976 29192 E AndroidRuntime: Process: no.nordicsemi.android.nrftoolbox, PID: 24976
11-17 17:41:52.740 24976 29192 E AndroidRuntime: java.lang.NullPointerException: Attempt to get length of null array
11-17 17:41:52.740 24976 29192 E AndroidRuntime:        at android.bluetooth.BluetoothGattCharacteristic.getIntValue(BluetoothGattCharacteristic.java:445)
11-17 17:41:52.740 24976 29192 E AndroidRuntime:        at no.nordicsemi.android.dfu.DfuBaseService.readVersion(DfuBaseService.java:2218)
11-17 17:41:52.740 24976 29192 E AndroidRuntime:        at no.nordicsemi.android.dfu.DfuBaseService.onHandleIntent(DfuBaseService.java:1370)
11-17 17:41:52.740 24976 29192 E AndroidRuntime:        at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:66)
11-17 17:41:52.740 24976 29192 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:102)
11-17 17:41:52.740 24976 29192 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:148)
11-17 17:41:52.740 24976 29192 E AndroidRuntime:        at android.os.HandlerThread.run(HandlerThread.java:61)
11-17 17:41:52.741  6178  6444 W BluetoothEventManager: CachedBluetoothDevice for device E0:4B:75:64:34:DE not found, calling readPairedDevices().
11-17 17:41:52.743 24220 24220 W BluetoothEventManager: CachedBluetoothDevice for device E0:4B:75:64:34:DE not found, calling readPairedDevices().
11-17 17:41:52.743  4556  6650 W ActivityManager:   Force finishing activity no.nordicsemi.android.nrftoolbox/.dfu.DfuActivity
11-17 17:41:52.774 28845 28862 I bt_btif_gatt: set_read_value unformat.len = 2

RE: Android 6 Master Control Panel Bonded DFU + Android 6 gets stuck in a loop

Aleksander Nowakowski — Tue, 17 Nov 2015 22:28:36 GMT

Hi, yes, we've tested it with Nexus 9 and 6, both with Android 6. Could you report the crash using the Unfortunately, ... dialog box? I'll have a look at it tomorrow.

RE: Android 6 Master Control Panel Bonded DFU + Android 6 gets stuck in a loop

Clem Taylor — Tue, 17 Nov 2015 22:10:57 GMT

MCP is never attempting to issue the start command, it is just disconnecting and reconnecting. The device side is happily accepting connections. When I manually do the write to DFU control point it is properly switching to bootloader mode (passing bond data and cleanly disconnecting). I'm not sure what you mean by giving more time to the device to setup, it can't reconnect until the device starts advertising and it doesn't start advertising until is is ready to go.

The 6p just happens to be the only device I have with Android 6, I'd imagine that the same issue would happen with other devices with Android 6. The BLE hardware on the Nexus 6P is fairly standard for current android devices. Has Nordic tested MCP DFU with Android 6 on any recent device?

I did manage to get the nRF toolbox to work, but it really likes to die with 'Unfortunately, nRF Toolbox has stopped'. nRF toolbox does not start out connected, it connects, does the CCCD write and then writes the 'start' DFU command. The device switches to bootloader mode, starts advertising, and the toolbox reconnects. From sending the 'start command' to reconnecting is ~1.5s.

The nRF toolbox crash seems to be related to having to bond to trigger the switch to DFU mode. It likes to die after I enter the pin. If I try a second time, Android remembers the bond and it the DFU upload works.

RE: Android 6 Master Control Panel Bonded DFU + Android 6 gets stuck in a loop

Aleksander Nowakowski — Tue, 17 Nov 2015 13:11:02 GMT

Hi, the reason thy it gets in a loop is that the DFU Version is always read as 0.1, which means that that's the application mode, not the bootloader mode. If it works when you manually write the start command, it means that the chip restarts after it disconnects, and does not start the DFU mode at all (or does, but immediately resets afterwards). The question is why..? I'm not quite sure. Nexus 4 sends just 1 packet each connection interval so it's very slow. Maybe it gives more time to the device to set itself up. We don't have the 6P yet, so it's hard to test, but it's a metter of time only.

Did you try the DFU with nRF Toolbox? It has a slightly newer version of the DFU library... There is a small chance it would work.