<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Headset: Could not create BIG sync -5 After a period of losting Sync from Gateway</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/101025/headset-could-not-create-big-sync--5-after-a-period-of-losting-sync-from-gateway</link><description>I am developing app in BIS mode and have encountered this problem. 
 When the signal from the Gateway is too weak that make the Headset must re-sync multiple time. The headset cannot create BIG group after call 
 
 bt_hci_cmd_send_sync with the return</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 20 Jun 2023 14:58:04 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/101025/headset-could-not-create-big-sync--5-after-a-period-of-losting-sync-from-gateway" /><item><title>RE: Headset: Could not create BIG sync -5 After a period of losting Sync from Gateway</title><link>https://devzone.nordicsemi.com/thread/432088?ContentTypeID=1</link><pubDate>Tue, 20 Jun 2023 14:58:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1ccef6ed-b0ff-4615-885e-e6780970d576</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;This is a known issue, we can replicate the issue by toggling the power of the BIS gateway frequently or putting the headset in the middle of in/out of the radio range from the gateway. The team is working on it, but no promised schedule. Sorry for the inconvenience.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Amanda H.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>