<?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>Questions regarding using scan response to advertise full device name</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/115986/questions-regarding-using-scan-response-to-advertise-full-device-name</link><description>Hi, I&amp;#39;m working on a BLE peripheral project using nRF52840 with nRF5SDK version 17.0.2 and softdevice S140 version 7.2.0 
 We are considering to increase our full device name from 10 bytes to 14 bytes. However, this cannot fit into our current adverting</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 08 Nov 2024 08:33:41 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/115986/questions-regarding-using-scan-response-to-advertise-full-device-name" /><item><title>RE: Questions regarding using scan response to advertise full device name</title><link>https://devzone.nordicsemi.com/thread/509615?ContentTypeID=1</link><pubDate>Fri, 08 Nov 2024 08:33:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b75ae9cb-5f4b-4213-9a36-cedd4c0e9f16</guid><dc:creator>Menon</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;You are always welcome.&lt;/p&gt;
&lt;p&gt;Kind Regards,&lt;/p&gt;
&lt;p&gt;Abhijith&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Questions regarding using scan response to advertise full device name</title><link>https://devzone.nordicsemi.com/thread/509596?ContentTypeID=1</link><pubDate>Fri, 08 Nov 2024 07:36:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8979cb52-a1a2-4ac2-814b-a2c4b265bac3</guid><dc:creator>yoyuasa</dc:creator><description>&lt;p&gt;Thank you for the detailed response! That really helps clear things up for us.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Questions regarding using scan response to advertise full device name</title><link>https://devzone.nordicsemi.com/thread/508704?ContentTypeID=1</link><pubDate>Thu, 31 Oct 2024 16:01:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7b6eaf90-0445-4a21-861f-c8999394445d</guid><dc:creator>Menon</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
[quote user=""]Will there be any impact to our already existing BLE service and characteristics ID from this change alone? We have some concerns that if this changes affects the existing service and characteristics ID then it will be a big change on both firmware and our application side.[/quote]
&lt;p&gt;No, there won&amp;#39;t be any impact on the existing BLE service or characteristic IDs. As long as these services and characteristics stay the same in your firmware, you don’t need to change the IDs or adjust any application logic connected to them.&lt;/p&gt;
[quote user=""]If we implement this way, do we need to update any RAM configuration for softdevice?[/quote]
&lt;p&gt;Moving the device name from the advertising packet to the scan response packet doesn’t require a change in SoftDevice RAM configuration. If RAM or Flash size changes were needed, the build log would indicate this.&lt;/p&gt;
[quote user=""]We will use our device with mostly PC and mobile phone (both iOS &amp;amp; Androids) so are there any known compatibility issues of using scan response packet for sending device full name? We have tested with a couple of iOS and android devices on our hands and they seems to work fine however we&amp;#39;d also like to know if there are such cases where compatibility issues might arises.[/quote]
&lt;p&gt;Using the scan response packet to broadcast the full device name is generally compatible with most BLE-capable devices, including PCs, iOS, and Android devices. So, the answer to this question is No; there are no known compatibility issues that might arise&lt;/p&gt;
&lt;p&gt;&lt;span dir="ltr"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span dir="ltr"&gt;&lt;span dir="ltr"&gt;Kind Regards,&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span dir="ltr"&gt;&lt;span dir="ltr"&gt;&lt;span dir="ltr"&gt;Abhijith&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>