Extended advertising (nRF52833 + S140) - Samsung S20+ can't connect, Huawei P30 can

RE: Extended advertising (nRF52833 + S140) - Samsung S20+ can't connect, Huawei P30 can

Simonr — Wed, 25 Mar 2020 09:08:45 GMT

[quote user="Simonr"]Do you see this error on both devices or just one end?[/quote]

By both devices, I meant both the Samsung as well as the debugging on the nRF side. Do you see this error when logging on the nRF device as well?

Please try adding adv_params.properties.scannable = 1; and adv_coded = false; when advertising with the 1MBPS PHY. Take a look at this case where a customer has implemented switching between 1MBPS and CODED PHY advertising.

Best regards,

Simon

RE: Extended advertising (nRF52833 + S140) - Samsung S20+ can't connect, Huawei P30 can

MatevzB — Tue, 24 Mar 2020 16:58:07 GMT

We see the error only on the Samsung device after 'Connecting' status. The other phone connects immediately.

The ble_evt handler (nrf_sdh_soc_evt_observer_t) is not called during the unsuccessful connection establishment.

void advertising_init(void)
{
	ret_code_t             err_code;
	ble_advertising_init_t init;

	memset(&init, 0, sizeof(init));

	init.advdata.name_type               = BLE_ADVDATA_FULL_NAME;
	init.advdata.include_appearance      = true;
	init.advdata.flags                   = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE;
	init.advdata.uuids_complete.uuid_cnt = 0;	
	init.advdata.p_manuf_specific_data   = &manufData;	
	
	init.config.ble_adv_fast_enabled  = false;
	init.config.ble_adv_fast_interval = APP_ADV_INTERVAL;
	init.config.ble_adv_fast_timeout  = APP_ADV_DURATION;
	
	init.config.ble_adv_slow_enabled = true;
	init.config.ble_adv_slow_interval = APP_ADV_INTERVAL;
	init.config.ble_adv_slow_timeout = 0; // Never timeout

	init.evt_handler = on_adv_evt;
	
	init.config.ble_adv_extended_enabled = true;
	init.config.ble_adv_secondary_phy = BLE_GAP_PHY_1MBPS;
	//init.config.ble_adv_primary_phy = BLE_GAP_PHY_1MBPS;
	init.config.ble_adv_primary_phy = BLE_GAP_PHY_CODED;

	err_code = ble_advertising_init(&m_advertising, &init);
	APP_ERROR_CHECK(err_code);

	ble_advertising_conn_cfg_tag_set(&m_advertising, APP_BLE_CONN_CFG_TAG);
}

void advertising_start()
{
	ret_code_t err_code;
		
	err_code = ble_advertising_start(&m_advertising, BLE_ADV_MODE_FAST);
	APP_ERROR_CHECK(err_code);
}

Anyway, we have now found an alternative way in order to avoid the use of extended advertisements.

RE: Extended advertising (nRF52833 + S140) - Samsung S20+ can't connect, Huawei P30 can

Simonr — Tue, 24 Mar 2020 11:51:54 GMT

Okay, the GATT ERROR (0x85) is unfortunately very general and can be a bunch of things. Do you see this error on both devices or just one end? In that case, where do you see it? I also recommend making a support ticket with Samsung's support channels as well, as you're only seeing this on a Samsung device. You can also test on more mobile devices to see if the error propagates elsewhere if you have the opportunity.

Can you upload a snippet of your code (advertising init) where you include extended advertising, etc., so I can have a look to see that everything seems correct?

Best regards,

Simon

RE: Extended advertising (nRF52833 + S140) - Samsung S20+ can't connect, Huawei P30 can

MatevzB — Tue, 24 Mar 2020 08:16:29 GMT

We missed the log entry there - it is Error 133 (0x85): GATT ERROR

The devices are being tested one at a time (no concurrent operation of both phones).

RE: Extended advertising (nRF52833 + S140) - Samsung S20+ can't connect, Huawei P30 can

Simonr — Tue, 24 Mar 2020 06:57:10 GMT

Have you tried debugging on the nRF side of things? I think you should be able to get an error code when the connection times out. Could it be that the nRF is bonded to the Huawei device already, which is why it isn't able to connect to the Samsung device?

Also, if you swipe left in the nRFConnect app, you should be able to see a log on the phone side as well, maybe you can see some error code there?

Best regards,

Simon

RE: Extended advertising (nRF52833 + S140) - Samsung S20+ can't connect, Huawei P30 can

MatevzB — Mon, 23 Mar 2020 08:36:23 GMT

Indeed, the Samsung device is unable to connect even if both are set to PHY_1MBPS, while Huawei has no issue.

No, there is no error displayed in the app - it simply times out.

RE: Extended advertising (nRF52833 + S140) - Samsung S20+ can't connect, Huawei P30 can

Simonr — Mon, 23 Mar 2020 08:23:47 GMT

This seems very strange indeed. Do you get any error code in the nRFConnect app? Do you see this error when the PHY_1MBPS is set to both primary and secondary PHY? Does it work if Coded PHY is set as both primary and secondary PHY?

I also think you should contact Samsung support, but we don't have any "ties" with their engineers for additional support, and we suggest using their regular support channels.

Best regards,

Simon

RE: Extended advertising (nRF52833 + S140) - Samsung S20+ can't connect, Huawei P30 can

MatevzB — Sat, 21 Mar 2020 11:18:05 GMT

Update, it somehow works if primary interface is configured as PHY_CODED and secondary as PHY_1MBPS.